Collaborate to evolve your business process

Business process mapping would be simpler if it wasn't for exceptions. Mapping  exception handling workflows can grow the task of process mapping by one or two orders of magnitude.
In most organisations, processes represent the result of evolution: Exceptions generated by a changing world have shaped the way business gets done. But the end result does not necessarily allow for the unknown exceptions of the future.
A neat approach to exception handling in business process management is to launch a collaborative space to resolve issues and feed the response back into the workflow. The space can be pre-populated with content depending on where in the workflow the exception occurred and rule-based invitations can go out to the appropriate facilitators and decision makers.
Mature corporations will want to measure the frequency of exceptions and concentrate efforts to define efficient responses and thereby embrace the most likely exceptions into the process. A BPM engine can provide the frequency data; collaborative spaces with full audit trails can be analysed to produce the optimal response. If you are really advanced, you only change the process once the response proves to have a statistically significant impact.
And what to do if there is an exception to the defined way of dealing with an exception? Kick off a collaborative space and watch process evolution in practice.