Caspar Jans's picture

I don't know how, but somehow I managed to get through this week, not because it was overly busy (it’s almost Christmas) but because I ran into a situation in which I almost did not know what to say anymore and for people that know me a little bit, this is quite rare.

Every once in a while you end up in a conversation where you are thoroughly confronted with the fact that you (and I mean everybody individually) assumes a lot things, you take a lot of things for granted while you have your conversations. You find yourself having a discussion with somebody (a client or a prospect or a friend) and based on one remark you suddenly realize that your assumptions going into the discussion where out of sync with reality.

The topic with which I had exactly this experience was #processmining and in and by itself this not amazing because I spend more than 50% of time talking about process mining. The way I normally build up this conversation is by explaining what I call the big picture (blog #5) where an organization’s strategy and operating model form the basis on which a process and system landscape is being defined and build. Then, once you have translated your processes into work instructions (or SOP’s) you arrive at the EXECUTION level (where it all has to happen).

Only then you can start to think about implementing more tools to either improve your execution capabilities (think about RPA or workflow automation) or to improve your understanding of the level of execution (task mining, IoT or process mining). And yes, all of these mentioned tools can be implemented in a stand-alone fashion, but to my opinion, this will leave you with stand-alone results. When looking for more structural or sustainable results (and thus also ROI), one would do good to consider embedding these tools into a wider process management practice.

So, there I was discussing this topic and all of sudden (I don’t even remember what triggered it) the bomb is dropped: “we don’t document our processes and don’t see the need to do it either”. Fortunately, the addition “but we could be wrong about that” was added rather quickly. My jaw just missed the edge of my desk and by the time I gathered my thoughts again, I decided that I would need to tackle that discussion in a different way. It started asking questions about how they dealt with improvement projects and more specifically the starting point for these projects and the efforts they deployed to make the improvement sustainable.

Soon, it became clear that one the main benefits of working according to process management principles is to reduce the number of time you have to re-invent the wheel!

Without process management (BPM) you often reinvent the wheel on…

  • value stream mapping when starting a LSS DMAIC process
  • finding out who needs to approve this change to our way of working
  • what do we need to train/teach our new employees on?
  • what activities are going to be audited because of ISO27K?
  • how did we do on our first time right KPI this month?
  • why are our business lines all executing this standard process differently?
  • why did our RPA bot stop working (it worked last week….before we implemented this new feature on our ERP)?

And the list of course can go on and on. 

I am a true believer of the BPM approach, and even if you would be skeptical I still believe there is so much published evidence why a process centric way of working is beneficial for your organization.

So, if you want to implement process mining without doing process management, please go ahead, but don’t be surprised if your results are not sustainable in the long run because you are lacking the foundation on which to embed your mined results. 

Having said that… no more blogs for the next 2 weeks…I’ll be enjoying my Christmas holidays and will try not to open up my company laptop ;-)

Happy Holidays and see you in 2021!

Ciao, Caspar

Tags: Business Process Management