We at Gartner talk about BPM’s focus on “continuous improvement.” We really like to talk about agility and rapid process change. So, what happens when your process change time is measured in years… or decades?
I heard a presentation today where the speaker was describing the complexities of interstate resource negotiation. He said in this particular case it has taken 18 years – so far – and they still haven’t been able to agree on a comprehensive update to the operations manual that governs the use of the resource. “Operations Manual” – an archaic word for “Hey! Where do I find all the processes?” – used when paper was king. 18 years…
The next time one of your process gurus tells you that it will be 24 hours before he can load your process changes on the server, don’t scream at him. Just imagine adopting a newborn, raising him, and then sending him off to college. See what process change cycles could be like.
Processes, unlike Single Malt Scotches, should not require 18 years in the barrel.