I think this is a challenge for lots of people. Process improvement should be iterative. It won't be perfect the first time, and as people wait for perfection, they miss opportunities for feedback. One of the benefits of BPM is that it allows people the flexibility both from an modeling perspective and an automation perspective.
This can be good and bad. The ease of use in changing a model and modifying the resulting application or automation of the process makes it tempting to tweak it real-time. This both creates some change management and application stability risk, but it also makes it difficult to manage user expectations. As they better understand flexibility, they want to make real-time changes. Compare this with years past when the user realized that if they missed their requirements window, they had to wait for a future release.
There is something in between that allows for agility while preserving stability. But, the key is making everyone understand this. I will stick with my golf analogy from blogs past. If I waited to play golf until I perfected my swing, I wouldn't have a lot of fun. But, in playing the game as I learn, I continue to find things to work on, situations I didn't consider, and identify questions to ask. When I go back to my pro for more lessons, I know things to work on and areas to develop on the practice green. BUT, modifying your swing during the round is typically a mistake. I think this is a good framework for thinking about your BPM efforts.
Comments