A practical field guide from Automation Ace.
The short answer
Before you automate anything, map how the process actually works today: who does each step, where work is handed off between people and systems, where it waits, and what goes wrong. A 60–90 minute discovery workshop with the people who do the work, captured as a swimlane map plus a one-page scoping worksheet, prevents the most expensive automation mistake: building the wrong thing quickly.
This is part of the automation planning playbook. Prepare with 50+ discovery questions.
Why map before you build
- The documented process is rarely the real one. People have workarounds nobody wrote down.
- Handoffs are where time and errors hide. Each one is a wait and a chance to drop the ball.
- Exceptions drive complexity. Finding them now is cheap; finding them after launch is not. See the exception inventory.
- A shared picture creates agreement on scope before anyone builds.
Who to invite
- The process owner accountable for the outcome.
- One or two people who do the work daily; they know the real steps.
- Someone from each downstream team that receives the output.
- The builder: automation engineer, consultant, or FDE.
Keep it under eight people. Ask for screen shares of the real tools.
The workshop agenda
DISCOVERY WORKSHOP AGENDA (90 minutes)
0:00 Goals and ground rules (5 min)
0:05 Name the process: trigger, end state, owner (10 min)
0:15 Walk the happy path step by step (25 min)
0:40 Mark handoffs, waits, and systems touched (15 min)
0:55 Exceptions: "what if...?" round (20 min)
1:15 Volumes, timings, pain points, and metrics (10 min)
1:25 Agree next steps and owners (5 min)How to draw the swimlane map
| Element | How to draw it | Example |
|---|---|---|
| Lane | One row per role, team, or system | Sales rep, Ops, Finance, CRM, Billing app |
| Step | A box for each action | “Create invoice” |
| Handoff | An arrow crossing lanes | Sales → Ops: “deal won” email |
| Decision | A diamond with labeled branches | “Over $5,000?” yes/no |
| Wait | A clock or note with typical delay | “Waits 1–3 days for signature” |
| Exception | A red flag with what goes wrong | “PO number missing” |
- Start at the trigger and end at the agreed “done” state. Do not map the whole company.
- Walk the happy path first, one step at a time, asking “then what happens?”
- Add a lane for each system, not just each person; copy-paste between systems is a prime automation target.
- Mark every handoff and wait with typical delays.
- Then do the exceptions round: “What if the data is missing? The customer replies late? The approver is out?”
- Note volumes and timings on the steps that matter.
Tools do not matter much: a whiteboard, sticky notes, Miro, Lucidchart, or a shared slide all work. Photograph or export the result the same day.
The scoping worksheet
Send this to the process owner before or after the workshop. It captures what the map does not:
PROCESS SCOPING WORKSHEET
Process name: ______________________ Process owner: ________________
What starts it (trigger)? ______________________________________________
What does "done" look like? ____________________________________________
Volume: ____ per day/week/month Peak times: __________________________
Average time per item (manual): ____ minutes People involved: ________
Systems used (in order): _______________________________________________
Handoffs between people/teams: _________________________________________
Approvals required (who, when): ________________________________________
Known exceptions / "what ifs": _________________________________________
Data that often arrives missing or messy: ______________________________
Rules that are written down vs "in someone's head": ____________________
Compliance or privacy constraints: _____________________________________
Biggest pain point today: ______________________________________________
How will we measure success? ___________________________________________After the workshop
- Score readiness with the readiness assessment and readiness calculator.
- Inventory the tools involved: systems and data inventory.
- Draw the future state: current vs future state.
- Capture a baseline: success metrics.
- Write the spec: requirements doc template.
Common mapping mistakes
- Mapping how it should work instead of how it does work.
- Interviewing managers only, not the people doing the work.
- Skipping systems as lanes, which hides data re-entry.
- Ignoring exceptions because “they are rare.”
- Jumping to tool choices in the workshop. Map first, design later.
Frequently asked questions
Why should I map a process before automating it?
Because the real process often differs from the documented one. Mapping reveals hidden steps, handoffs, waits, and exceptions, so you automate the right thing and agree on scope before building.
What is a swimlane process map?
A diagram with one horizontal lane per person, team, or system, showing each step in its lane and arrows where work is handed off, plus decisions, waits, and exceptions.
Who should attend an automation discovery workshop?
The process owner, one or two people who do the work daily, representatives of downstream teams, and the person who will build the automation. Keep it under eight people.
How long should a process mapping workshop take?
Sixty to ninety minutes is usually enough for one process, covering the happy path, handoffs, exceptions, volumes, and success metrics.
What goes in an automation scoping worksheet?
Process name and owner, trigger, definition of done, volume, time per item, systems, handoffs, approvals, known exceptions, data quality issues, compliance constraints, pain points, and success measures.
Disclaimer: Templates and checklists are starting points; adapt them to your process, policies, and tools. Product features, limits, and pricing mentioned here change over time, so confirm current details in each vendor's documentation. This article may include links to apps, products, or services; some links may be affiliate links, which means Automation Ace may earn a commission at no extra cost to you.