Why map the process before automation?
Automation copies a process. If the process has gaps, duplicate checks or steps that only one person understands, automation will reproduce them faster and make them harder to see. A map makes the current way of working visible, so the team can agree on what should change before any tool is chosen.
The map also settles a practical question: which part to automate first. Most processes have one or two places where work waits, gets re-typed or goes missing between people. Those are usually better candidates than the step everyone complains about loudest. Business process automation services start from exactly this picture, because without it any quote is a guess.
Keep the map to one page. A large diagram with every possible branch looks thorough but is rarely read. One page forces you to show the main route and the exceptions that really happen.
Choose one process per map, with a clear start and end. “Sales” is too broad to draw; “from a new enquiry to a sent quote” fits on a page and can be checked against what actually happened with recent enquiries. If the map keeps spilling over, split it into two processes and pick the one that matters more right now. Broad maps of the whole company are useful later, once a few individual processes are understood and the team has seen what a map can show.
What goes on the one-page map?
Trigger and result. Where does the process start, for example a new enquiry or an incoming invoice, and what does “done” look like?
Steps. List the steps in order, each as a short verb phrase: check the request, create the client record, send the quote. Map what happens today, not what the procedure says should happen.
Owners. Next to each step, write the role responsible. If the honest answer is “whoever is free”, write that too; it is often where things go missing.
Systems. Name the tools used at each step: email, a spreadsheet, the CRM, the accounting system, a messaging app. Mark every place where data is copied by hand from one system to another.
Handovers. Mark every point where work passes from one person or team to another. Handovers are where work waits, and waiting stays invisible until someone draws it.
Exceptions. Add the cases that leave the main route: missing information, a request that needs approval, a customer who changes their mind. Note who handles each one and roughly how often it comes up.
How do you choose what to automate first?
Walk through the map with the people who do the work, not only with managers. Ask where they wait, what they re-type and what they check twice, and mark those points on the map. A business process consulting session can help when the team is too close to the process to see it, but often one honest walkthrough is enough.
Then compare the candidates. A good first automation happens often, follows clear rules, has a visible owner and connects systems that already hold the data. Steps that depend on judgement, and exceptions that come up rarely, are better left to people for now. Write down what the result should be after automation and how you will know it works.
Sometimes the map shows that the right answer is not a connector between existing tools but a system built around the process. In that case custom software development is worth comparing, and the map becomes the starting point of its specification. Either way, keep the map current: when the process changes, update the map before changing the automation.
How do you draw it without special tools?
A whiteboard, sticky notes or a simple table are enough. Draw one row per role, place the steps in order along it and draw an arrow wherever work passes to another row. Standard notations such as BPMN are useful for large projects, but for a first map clarity matters more than the correct symbol.
Photograph or copy the result into a shared document, add the date and ask everyone involved to correct it within a few days. A map that the people doing the work recognise as true is worth more than a neat diagram that only its author believes. Keep the first version rough on purpose: people correct a sketch far more readily than a diagram that already looks approved.
Common mistakes
- Mapping the official procedure. The documented process and the real one often differ. Map what people actually do today, including the workarounds.
- Leaving out the exceptions. A map that shows only the main route hides the cases that cause most of the manual work.
- Mapping without the people who do the work. Managers see the outline of a process; the details of where work waits are known by the people at each step.
- Automating the loudest complaint. The step people complain about is not always the one that slows the work most. Let the map, not the noise, choose the first candidate.
- Treating the map as finished. Once the automation is live, the process changes. Update the map, or the next improvement will start from an outdated picture.
One-page process map template
A template to adapt to your own project.
| Field | What to write |
|---|---|
| Trigger | What starts the process. |
| Result | What “done” means and who confirms it. |
| Steps | Short verb phrases in today’s order. |
| Owner | The role responsible for each step. |
| Systems | The tools used and where data is copied by hand. |
| Handovers | Where work passes between people or teams. |
| Exceptions | Cases that leave the main route and who handles them. |
| Candidates | Steps that happen often, follow clear rules and have an owner. |
Checklist: process map
- Name the trigger and what “done” means.
- List today’s steps in order, with an owner for each.
- Mark the systems used and every manual copy between them.
- Mark the handovers and the exceptions that really happen.
- Walk through the map with the people who do the work.
- Choose a first automation that is frequent, rule-based and owned.
Example: from enquiry to quote
A small service company maps how an enquiry becomes a quote. Enquiries arrive by email and through the website form, a manager copies each one into a spreadsheet, a specialist prepares the quote in a document template and the manager then re-types the details into the accounting system.
The loudest complaint was about the document template, but the map shows that the real delays happen at the copying steps and at the handover between manager and specialist. The first automation creates the record from both sources and notifies the specialist. The quote template stays as it is until the team has seen how the new flow works.
