What is workflow management (and where does automation fit)?

What workflow management covers

Workflow management makes a repeating process explicit and then keeps it accountable: the sequence of activities, the owner of each one, the rules that route work between them, and the measurement of where it stalls. The Workflow Management Coalition, founded in May 1993, wrote the definition most vendors still borrow, and it draws the line clearly. An activity in its model "may be a manual activity, which does not support computer automation, or a workflow (automated) activity." Manual steps sit inside the scope, not outside it.

How it is structured

Four parts, in order:

• A process definition. The steps, roles, and routing rules. WfMC's XPDL and OMG's BPMN 2.0 are the two formats that survived; roughly 60 tools still read XPDL.
• Assignment. Each activity instance becomes a work item on somebody's list, human or agent.
• Enactment. Something runs the routing, either software or a person forwarding email.
• Monitoring. The 1995 WfMC Reference Model made this a first-class interface, one of five, because a process nobody can audit cannot be improved.

Where it bites

The cost is almost never the steps. It is the gaps: work sitting in an inbox, two people doing the same review, nobody able to say what stage a deal is at. Automating a process that nobody has mapped just makes the wrong sequence run faster. Map first, then automate the steps that are genuinely repetitive, and leave judgment calls as approvals a named owner signs off. If a process runs fewer than a handful of times a month, write it down and skip the tooling.