How to run a process mapping workshop that ends with a map
Most process mapping workshops end with a wall of sticky notes and a promise that someone will type it up. The typing-up takes two weeks, and by then nobody remembers what the arrow from the yellow note meant. Here is how to run one that ends with a finished, shareable process map, in about ninety minutes.
Who to invite
Five to eight people. More than that and the conversation splits; fewer and you are missing a lane.
- One person who does the work for each lane of the process: the people who actually raise the order, approve it, receive it and pay it.
- The process owner, who can settle disagreements about how the process should run.
- A facilitator who is not one of the above, so the person drawing the map is not also defending their part of it.
- On an ERP project, the functional consultant for the module, so differences from the standard system are noted as they come up.
Prepare a draft, not a blank page
The single biggest time-saver is arriving with a draft. Take a template for a similar process, or spend an hour with the process owner filling in a spreadsheet: one row per step, with the owner, the next step and any decision. Turn it into a map before the session.
A draft changes the conversation. Instead of 'what happens first?', which produces silence, you ask 'is this right?', which produces corrections immediately. People are much better at fixing a wrong map than at drawing a right one from nothing.
A 90-minute agenda
This fits one end-to-end process at a level of twenty to thirty steps:
- 10 minutes: agree the boundaries. What event starts the process, what result ends it, and what is out of scope.
- 10 minutes: agree the lanes. One per role or team that does work in the process.
- 40 minutes: walk the draft step by step. At every step ask who does it, what they need to start, and what they hand on. At every decision ask what the real rule is.
- 15 minutes: the exceptions. Ask what goes wrong every week, and add those branches.
- 10 minutes: open questions and owners. List anything unresolved with a name and a date.
- 5 minutes: confirm who reviews and approves the finished map.
Build the map live
Edit the map on screen during the session rather than on a whiteboard. If the map is generated from a spreadsheet, the facilitator edits rows (renames a step, changes its owner, points its next step somewhere else) and the diagram redraws as people watch. That keeps the focus on content: nobody waits while boxes are dragged into line.
Write the decision labels as the actual rule, not 'yes' and 'no'. 'Over 10,000' and 'up to 10,000' is a business rule people can check; 'yes' is an invitation to interpret.
Handling disagreement
Two people will describe the same step differently. Usually both are right: the process really does run two ways, depending on the region, the customer or who is on shift. Draw both as branches and record what decides between them. If the process owner wants one way only, that is a to-be decision; note it and keep mapping what happens today.
After the workshop
Share the map the same day, while people still remember the discussion, and give reviewers a short deadline. Two rounds of review is usually enough. Then the map can be used: for training, as input to an ERP fit-gap analysis, or as the baseline for an improvement project.
Frequently asked questions
How long should a process mapping workshop be?
Ninety minutes for one end-to-end process at twenty to thirty steps, if you arrive with a draft. Without a draft, plan two sessions. Sessions longer than two hours lose people; split large processes by phase instead.
Should we map the current process or the ideal one?
Map the current process first, honestly, including the workarounds. Designing the ideal process before agreeing on the current one means arguing about two things at once. Record improvement ideas as notes and come back to them once the current map is agreed.
Do we need a professional facilitator?
No, but the facilitator should not own any step of the process. Their job is to keep the session moving, ask what the real rule is at each decision, and capture what is said, not to argue for how their part of the process works.
Try it on your own process
The editor is free and opens with a starter template. One row per step — the swimlane diagram renders as you type. No signup required.
Start Process Mapping Free