Short answer: Follow one real case from its start to its finish. Record the trigger, person or system responsible at every step, information used, decision rule, handoff, exception, and definition of completion. Map what actually happens before designing what should happen.
A lightweight process map
Use a table with one row per step:
| Step | Trigger/input | Owner/system | Rule or decision | Output/handoff | Failure or exception |
|---|---|---|---|---|---|
| Receive a request | Form, email, or other agreed source | Intake owner | Required details present? | Create or route a case | Incomplete or duplicate request |
Add the real system names only after confirming the team uses them and can provide access. Do not assume a connector exists just because a vendor name is familiar.
Walk through edge cases
Ask the people doing the work to describe a normal case, then a late case, missing information, duplicate, rejected approval, and system outage. A diagram that shows only the happy path is an incomplete specification. Write down who owns exceptions and how work resumes after a failure.
Fictional example: a quotation request
Suppose a fictional sales team receives quote requests through a web form. Today one person checks the fields, another looks up availability, and a manager approves unusual discounts. A sensible first version might validate required fields and route each request to a named owner. AI could later classify free-text product descriptions, but it should not approve a discount unless a clear, tested rule and authorisation are defined. This scenario illustrates mapping, not a real client project.
Turn the map into a baseline
For each step, measure volume, active minutes, waiting time, rework, and error consequences. These figures help identify the bottleneck and estimate whether a change is worthwhile. They also let the team compare the pilot with the original process.
Do not automate a confusing process simply to make it faster. Clarify ownership and policy first. See the workflow automation guide, automation ROI formula, and workflow automation services.
Written by
Formula Works
Published
Thu Oct 29 2026