To map a business process, pick one job and follow it from trigger to finish: interview the team leads for the outline, then the people who do the work for the detail, draw one swimlane per role, and mark every system, hand-off and wait. Then check the map by walking one real, recent case through it. The process mapping template below gives you the fields to capture for each step.
Before you start: choose one job
Map one job end to end, not a department. “Finance” is not a process. “A supplier invoice from arrival to payment” is. A good first choice has a clear start and finish, happens often (daily or weekly), crosses at least two teams and causes complaints.
We will use one example through this lesson: say a wholesaler with 40 staff wants to map a customer order, from the customer’s email to the invoice. It starts when an order lands in a shared Outlook inbox and ends when the invoice is sent from Xero.
Write the boundaries down first: the trigger (order email arrives), the end (invoice sent) and what is out of scope (payment collection, returns). Without boundaries, the map grows until nobody finishes it.
Step 1: Interview the team leads for breadth
Start with a short conversation with the head of each team the job touches: sales, warehouse, logistics, finance. You want the outline, not the detail: what the team does with the order, who it gets work from, who it hands work to and which systems it uses. Twenty minutes each is plenty.
Ask: “When an order reaches your team, what happens first? Who does it go to next? What usually holds it up?” Sketch the steps as you go, and note the names of the people who actually do each part.
Step 2: Interview the people doing the work for depth
Leads describe how the work is supposed to run. The people doing it know how it runs. Go back to the sales coordinator, the picker and the person who raises invoices, and follow up on what their lead said.
Short interviews work better than workshops. In a workshop, people describe the official version in front of their manager, and the workaround stays quiet. Fifteen minutes one to one, or a voice note answered between tasks, gets you the real version. Ask for specifics:
- Walk me through the last order you handled. What did you do first?
- How often does this happen? How long does it take?
- What do you do when the stock figure is wrong, the customer has no account or the price is different?
- Where do you write that down?
Keep their exact words in your notes. You will need them when two people disagree.
Step 3: Draw swimlanes by role
A swimlane map gives each role a horizontal lane and puts every step in the lane of whoever does it. Each time the work crosses from one lane to another, that is a hand-off. Use roles, not names: “sales coordinator”, not a person. People change jobs; roles stay.
Keep the symbols basic: a rounded box for start and end, a rectangle for an action, a diamond for a decision (stock available? yes or no) and a page shape for a document such as a delivery note. Any tool works: a whiteboard, Excel, Visio, Miro, Lucidchart. The tool matters far less than the fields you capture.
Step 4: Mark systems, hand-offs and waits
Under each step, note the system it happens in. In the order example it might be Outlook, then HubSpot, then a stock spreadsheet, then NetSuite, then a printed picking list, then Xero. Every change of system is a place where data is retyped, and retyping is where errors come from.
Mark each hand-off and how it happens: system notification, email, chat message, phone call, a sheet of paper on a desk. Then mark the waits: how long the work typically sits before someone picks it up. Ask for the usual wait and the bad-day wait; the gap between them tells you where the process is fragile.
Step 5: Count hand-offs and waits
Now count. How many times does the order change hands? How many systems does it touch? Add up the usual waits. For the wholesaler, the tally might read: six hand-offs, five systems, about half an hour of actual work and a day and a half of waiting. Those figures are only an example, but the pattern is common: the work itself is quick, and the time goes on waiting between people.
These counts are your baseline. When you change something, whether a new rule, a new system or an automated step, you count again and compare.
Step 6: Walk one real case through the map
Pick an order from last week, ideally one that went slightly wrong, and trace it through the map with the people involved. Open the actual email, the actual order in NetSuite, the actual invoice in Xero. Does every step on the map appear? Did anything happen that is not on the map?
This is where missing steps show up: the credit check someone does informally, the call to confirm a delivery slot, the spreadsheet the warehouse keeps to track backorders. Add them, with who told you.
Step 7: List the open questions
Finish with a short list of what is still unclear: steps with no owner, contradictions you have not resolved, exceptions nobody could explain. That list is a to-do, not a failure. It is also where the lesson on documenting exceptions picks up.
Process: [one job, e.g. Customer order, email to invoice]
Trigger: [what starts it] · End: [what finishes it] · Out of scope: [what you are not mapping]
Map owner: [role] · Last checked against a real case: [date and case reference]
One row per step. The example rows are illustrative; replace them with yours.
| # | Step (verb + object) | Role (stand-in) | System | Hand-off to (how) | Usual wait (bad day) | Exceptions | Source (who said it) | Confirmed? |
|---|---|---|---|---|---|---|---|---|
| 1 | Read order email and find the customer | Sales coordinator (sales manager) | Outlook, HubSpot | — | 2 hours (1 day) | No account: ask finance for a credit check | Sales coordinator | Yes |
| 2 | Check stock for each line | Sales coordinator | Stock spreadsheet | — | 30 min (half a day) | Spreadsheet out of date: phone the warehouse | Sales coordinator; warehouse lead disagrees | No: contradiction |
| 3 | Enter the sales order | Sales coordinator (sales manager) | NetSuite | Warehouse (forwarded email) | 4 hours (1 day) | No PO number: hold and email the customer | Sales coordinator | Yes |
| 4 | Pick and pack | Picker | Printed picking list | Logistics (paper on desk) | [ ] | [ ] | [ ] | [ ] |
Totals: hand-offs [ ] · systems [ ] · work time [ ] · usual waiting time [ ]
Open questions: [steps with no owner, unresolved contradictions, unexplained exceptions]
Once the map holds up against a real case, the next step is to turn each team’s part into a procedure people can follow: how to write an SOP. If you are new to the terms, start with what business process mapping is.
Not sure which job to map first? The free Bonofici grader reads your company’s public pages and shows where to start.