Definition
Workflow mapping is documenting how work actually moves, including actors, inputs, decisions, exceptions and handoffs, before deciding what to change or automate.
A useful map is one the people doing the work recognise as true. It is the foundation for deciding whether a step should be removed, integrated, automated or given to an AI agent.
Why it matters
Automating a process nobody fully understands makes the confusion faster. Most workflows contain steps that exist only in someone's head, workarounds for broken systems, and approvals that no longer serve a purpose.
A map makes those visible. It shows where time is lost, where errors start and which steps could be removed entirely, which is often more valuable than automating them. It also gives everyone a shared picture to agree on before money is spent.
An example
A clinic maps patient onboarding and discovers that reception enters the same details into three systems, and that insurance checks wait a day because they are batched each evening. The fix is one integration and a real-time check, not an AI agent. AI is then applied to the step that is left: reading referral letters.
Illustrative example, not a client project.
Common questions about Workflow mapping
How long does workflow mapping take?
For one workflow, usually days rather than weeks: interviews with the people doing the work, observation of the real process, then a map they review and correct.
What tools are used to map a workflow?
The tool matters less than the accuracy. Sticky notes, a whiteboard or diagram software all work, as long as actors, inputs, decisions, exceptions and handoffs are captured.
Related terms