While interacting with our clients around the world two questions generally top the frequently asked questions list. One of those questions I will save for the topic of my post next week. Yes...a teaser I know. But hopefully your inquiring mind will bring you back for the installment next week. The question I wish to ponder today is "How do you know when it is time to change a process that is already running in production?"
In short, my answer is always the same. There is no one size fits all answer. The key consideration driving the change should be one of value and/or optimization. Have you constructed a process that is as efficient and streamlined as possible? Will there be any recognizable or appreciable gains from changing the process? Has your business environment changed in any way? If the answer to any of these questions is YES, it's time to change the process. Just a hint - the answer is always likely to be YES to at least one.
Modern state-of-the-art BPM platforms, like BizFlow, make changing and implementing a process simple, effective, and quick. There is no reason not to change if gains can be realized. Some organizations have a mindset that changing their processes somehow demonstrate original design weaknesses. Studies conducted by the University of Applied Sciences in Koblenz, Germany refute this thinking. Their study results reveal that nearly two thirds of enterprises who change their processes annually, or more frequently, demonstrate higher levels of business success than their competitors who don't. As these results are summarized by industry it aids in refuting the naysayers who might use differing economic environments and/or markets as oppositional fodder.
The bottom line in my mind is this: continuous process improvement and optimization should be the goal of any enterprise that wishes a long and prosperous future. For those who have made the investment in a BPM platform this should prove to be no challenge as the capabilities to do so are presently at hand. To those enterprises still slugging it out the "old school" app dev way, the mantra of "evolve or die" should bear careful consideration.