What is Process Mapping?
Also called process map, workflow mapping.
Process mapping is the practice of drawing a process as an ordered sequence of steps, decisions, inputs, and handoffs, usually as a diagram. It makes explicit what a procedure actually involves, including the branches that experienced staff handle without thinking. Maps are a prerequisite for delegating a process to an AI agent reliably.
The technique long predates AI and comes from quality management and industrial engineering. Standard notations distinguish activities, decision points, waits, and handoffs between roles. The specific notation matters less than the discipline of forcing every branch onto paper, since undrawn branches are precisely where an unattended agent will behave unexpectedly.
Maps usually reveal three things. There is a difference between the documented process and the performed one. There are more decision points than anyone estimated. And there are waits, often the largest component of elapsed time, where work sits idle pending someone's attention rather than being actively worked on.
For delegation purposes, decision points are the critical feature. Each one has to be answerable from information the agent can access, or it becomes an escalation. Mapping therefore doubles as a design exercise for the escalation path: the branches that cannot be resolved from available data define exactly where a person must be brought in.
Over-mapping is a real failure mode. A map detailed enough to cover every conceivable variation takes longer to produce than the automation saves and is obsolete when the process changes. Most practitioners recommend mapping the path that covers the large majority of cases and treating the remainder as explicit exceptions rather than trying to diagram them.
Key points
- Draws a process as steps, decisions, inputs, and handoffs
- Comes from quality management, not AI
- Reveals gaps between documented and performed process
- Decision points define where escalation is needed
- Over-detailed maps go stale before they pay off
In practice
A recruiter maps candidate screening and finds nine steps but fourteen decision points, eleven of which depend only on the CV and the role brief. The remaining three depend on knowing which hiring managers tolerate career gaps, which is written nowhere. Those three become the escalation boundary: the agent screens against the eleven and routes anything touching the other three to a person.