I, BPM: when the quest for automation loses the most important element. You.

Companies love BPM. It’s a chance to address burning issues with a cohesive strategy, to turn a flagging and tired business model into a lean, mean operating machine. It’s a chance to engage everyone in the enterprise and teach them the values of process thinking.

And it’s also a chance to go horribly wrong when the attention is focused on a shiny new piece of software at the expense of that strategy.

What invariably happens is that the newly acquired BPMS becomes the focal point of all effort and automating everything or as much as possible is the overriding quest and definition for success. While some companies see the opportunity to improve process, operating model and strategy then align and use the BPMS to support that goal, others simply fall into the old trap of garbage in/ garbage out, lets chuck it all into the system and automate for quick gains and improvements. Automating process for the sake of it because you now can is never a winning strategy, nor will it show off the value of your BPM strategy.

We know that doesn’t work. They don’t know it doesn’t work. But are you prepared to tell them ?

What ?! You mean this expensive piece of kit doesn’t fix our problems ?! What do you mean it’s not a panacea ?!!

I’ve seen low level management and C-level execs over the years all clap excitedly at the mention and thought of automating the simplest of processes and integrating clunky systems for the sake of it to the point of obsession. It primarily falls down because there’s a lack of fundamental understanding of what good BPM can really achieve, or what BPM means for that organisation. I’ll go further and suggest that those kind of leaders have lost touch with how their business actually operates from the inside, not from how they think it does from the comfort of the boardroom.

It boils down to education again (yes, yes, that drum I’ll continue to beat for a while still)

We have BPMS, decisioning engines, Adaptive Case, each piece of the overall expanding BPM landscape is turning enterprise into mere automatons, removing the human elements and judgements that add the core value to the business itself. There is a law of diminishing returns in BPMS that most won’t tell you, at some point the effort to automate and design increasingly complex decisions to capture and process all possible scenarios becomes greater than the efficiency and resultant savings you first aimed for. Furthermore, removing the human from the process and boiling everything down to just sets of values to return on a screen or automatically process removes judgement, removes the personalisation, removes the connection to your ultimate strategy: the customer.

BPMS is like any enterprise technology, it’s an enabler, a support for your overarching BPM strategy. It’s not the goal to aim for.

To paraphrase Shakespeare: To automate or not to automate ?: that is the question.

3 responses to “I, BPM: when the quest for automation loses the most important element. You.

  1. Pingback: BPM Quotes of the week « Adam Deane·

  2. You’re right on on the point. Thing is education is the logical step but I’ve heard in my short time in BPM that people hate learning on the job so to speak. Esp higher up. A Generalisation but it’s a chance to get out of the office (sure), they’ll go for the training heck they’ll even have a few meetings on the thing and hire some people. Then something else comes along and this gets put to the side. BPM is strategy and till that happens, sad to say we’re stuck with software peddlers and never ending “discussions” about “how to measure BPM success”.

  3. Pingback: Google gets workflow wings with KiSSFLOW. Can they democratize BPM? « The Eclectic Zone·

Leave a comment