Most Business Analysts have a reasonable idea about how to develop a Business Process. We don’t all do it the same way (far from it), however the general approach is usually much the same, it goes something like this…
- Gather requirements from the business
- Design and validate a process model
- Implement the new process with the business
- Move on ..
What will this look like in the world of Process 2.0?
I recently asked the BPM Collaboration community about Process and Google Wave (check out the forum thread to follow the discussion). Bernie Clark provided me with a link to a great YouTube video prepared by the SAP Research centre, it is titled “Gravity, the best example of Google Wave”. This is well worth 7 minutes. Well done to the research team for a quality presentation.
Using this kind of collaborative process development, the Business Analyst becomes more of a facilitator and educator about the way to build processes, without needing to get too involved in the business. With this kind of approach, an organisation would be capable of developing and deploying Business Processes in record time!
Add to this, adhoc process modelling. This concept, introduced to me as a new feature in the webMethods 8 product suite, provides the ability for knowledge workers to model processes as they are being executed. Generally there is marginal value in mapping a complex process that is not executed regularly, especially where human judgment is involved!
However, if you can capture the process as it is completed, then you can measure what has been done and learn from the experience in the future.
My first reaction to adhoc processes was, “It is hard enough to get people to map processes and execute them, what incentives would be needed to encourage adhoc mapping?”.
What if we mixed both collaborative and adhoc process modelling?