How Business Process Management Works [As-Is, To-Be, and Business Process Improvement]

Most IT Managers don't understand the importance of Business process mapping!

Great insights as usual Eric ! Thank you !

Excellent content as always! Thank you!

Dear Eric - I believe that indeed there is a whole "trenches-war" happening within businesses when the "write down the AS IS status" part comes up. Other members of the company deep dive and drown into details of "we click that button and then Julia receives this .....and does that and ....." and some other members are thinking that this whole BPM(ining) has no meaning and so on - boredom etc. But both cases are wrong and they cost the business seriously. This whole thing is not happening with your videos, you are Concise, Simple, Accurate, Explanatory, and "democratizing" in your speaking and presenting the main concepts and outcomes of the Digital Transformation universe. Thank you again.

You are going too fast…

Thank you a lot, i took a note some of your words to my notebook about what did you said.

Hi Eric, very informative videos have subscribed :). Needed some tips i am about to conduct future state process workshop for some raising PO process along with the process managers for which all AS IS maps are ready with identified VA, wastes, business VA. Want to have interactive workshop with all process owners buy in...Planned for brown paper exercise with sticky notes any tips can help

This was a very useful video, thank you.

Hi Eric, thanks a lot for the content you're putting, very useful and helpful! Quick question on the future state and the requirements of TO BE. You've mentioned that first we should define our AS IS, to understand the current situation and opportunities. From there we should then define TO BE processes, which would be the backbone of the requirements. The part that I find difficulty is how the TO BE processes translates into formal requirements and how detailed those requirements should be? As by the time we are mapping the TO BE state we are not yet aware of the technological solution that the ERP brings, thus we don't know exactly how the process can work. And then if we don't describe the details, how can we use it as a formal requirement? Won't it be too general to use as a requirement document? Really tricky! Would appreciate any tip on this one. Thanks!