If a process exists only in one person’s memory, an automation diagram drawn from assumptions is a risk register in disguise. This guide gives you a practical mapping method that captures the real path, exceptions, and ownership before anyone opens a workflow builder.
Map what happens, not what the procedure says
Ask a person who performs the work to walk through a recent case. Capture the trigger, each action, system used, decision, wait, handoff, and final outcome. Note where people copy data, ask for clarification, or make judgment calls. The official procedure is still useful, but compare it with actual work. Power Automate approvals.
Use swimlanes for roles or systems and name decisions as questions with explicit branches. A box labelled “process request” conceals more than it explains.
Include the paths the happy path omits
Map missing information, duplicate requests, out-of-hours arrivals, rejected approvals, retries, and cancelled work. Record what people do today when a system is unavailable. For each exception, identify whether it is rare, expensive, risky, or simply part of normal operations.
A process map is also a troubleshooting aid: each transition should have an observable result so the team can locate where a run stopped.
Add facts that support a decision
For a representative period, estimate arrival volume, processing time, wait time, correction rate, and exception frequency. Mark which numbers are measured and which are estimates. This avoids treating a few memorable delays as a reliable baseline. See also OpenAI evaluation best practices.
Note the data touched, permissions needed, retention expectations, and any customer-impacting decision. If a step needs judgment, specify criteria and who is accountable for the final call.
Turn the map into a safe pilot
Select one bounded segment and state what success and failure look like. Keep manual approval around irreversible actions. Define alerts, a process owner, recovery steps, and a manual route before launch. Then compare the pilot to the baseline and update the map as the real workflow teaches you something.
The map is not a contract to automate every box. It may reveal that the best improvement is to remove an unnecessary approval or clarify ownership before connecting software.
What would you do?
What “invisible” step in your team’s process would surprise someone mapping it for the first time? Share your experience in the comments.
Have a related project in mind? Talk with Acorn.
Share your perspective