At the core of every BPM implementation there is always a workflow, a sequence of connected steps with process routing.
Process Routing should be the most boring subject in the world.
Should be… but not.
Everyone sees process from a different perspective.
You’ve got the Six-Sigmas that see the process from orbit.
Enterprise Architects that see the process from 10,000 feet.
The Business / Process and other analysts that see the process from 1,000 feet,
and let us not forget researchers, consultants, marketing guys, project managers and business philosophers and BPM theologians that see process from the office window.
At the bottom of the pile, you’ve got the guys in the trenches looking up and asking “Eh.. Hello…What the heck are you all talking about”
The recent discussions on dynamic vs structured processes provide a simplistic alternative to process routing problems. Dynamic vs Structured…
Its like explaining that sending a task to a group is an alternative to sending the task to a single recipient.
People sometimes tend to forget the range of options you can use in workflow routing:
• Send a task to a group in the organization
• Send a task to a queued group
• Send a task to a calculated user in a group
• Send a task to an employee role in the organization
• Send a task to a process role in the workflow
• Send a task to an email defined in one of the forms
• Send a task to calculated external users
• Send a task to internal calculated users
• Send a task to multiple users/multiple groups
• Send to a named user (ok… not the best practice)
• Let the system decide whom in the group to send the task to
Process routing is a bit more complex than “let the user decide who to send it to”