Mapping a Manual Workflow Before Automation
A workflow map makes hidden decisions visible. The purpose is to describe what people actually do, including workarounds, rather than draw an ideal process that does not exist.

Follow one item through the process
Choose a real example and record each hand-off, decision and waiting point. Note where staff copy data, look up information or ask someone for approval. Mark the systems involved and any information that changes format along the way.
Practical checklist
- Identify the starting event.
- Record decisions and exceptions.
- Name each hand-off owner.
- Define the evidence of completion.
How to review the result
Ask another team member to follow the map with a different example. Differences between their actions and the map reveal rules that need clarification before development.