Why this matters
Automation projects fail quietly. A tool is installed on top of a process nobody has written down, exceptions pile up, and within a quarter the team has routed around it. The cheapest insurance is unglamorous: one afternoon, one workflow, one wall of sticky notes.
This playbook is the exact mapping exercise we run before any engagement. It requires no software and produces a document your whole team can argue with.
The method
Choose one workflow that is frequent, painful and bounded — lead follow-up, invoice chasing, client onboarding. Bounded means you can say where it starts and where it ends. Gather the two or three people who actually do it, not only the people who manage it.
- Step 1 (20 min): List every step from trigger to done, one sticky note per step, in the order it really happens.
- Step 2 (20 min): Mark the exceptions — the five percent of cases that take fifty percent of the time.
- Step 3 (20 min): Mark every handoff between people or systems. Handoffs are where work silently waits.
- Step 4 (20 min): Mark the judgement calls — steps where a human decides something that depends on context.
- Step 5 (20 min): Agree as a group what 'good' looks like: speed, quality, cost, or the thing your customer actually feels.
Reading the map
Automate candidates are steps that are frequent, rules-based and low-judgement. Steps heavy with judgement are assistant candidates — technology that prepares, a person that decides. The exceptions list tells you what will break a naive automation, and it becomes your test plan.
If the group cannot agree on what 'good' looks like, stop. That disagreement is the finding; automate nothing until success has a definition.
Actions you can take
- Block one afternoon this month and map a single workflow using the five steps.
- Circle exactly one automation candidate and one assistant candidate on the map.
- Write the success measure for a pilot before you speak to any vendor — including us.
Limits — what stays uncertain
- A map shows one workflow, not the whole organization; resist generalising from a single afternoon.
- Workflows change after automation; plan to re-map after the first pilot, not before it.

