Quick answer: Swimlane process mapping draws a process in horizontal rows, one row per role or system, so you can see who does each step. Its real value is the hand-offs: every arrow that crosses from one lane to another is a point where work can sit in someone’s queue, and those crossings are where most of the waiting time hides.
A swimlane diagram gives every role its own row, so ownership is never ambiguous
A plain flowchart shows the order of steps. A swimlane diagram adds who owns each one. You draw a horizontal band for each participant, such as credit control or the ERP itself, and place every step inside the band of whoever performs it.
The layout answers a question a flowchart leaves open. When a purchase order stalls, the diagram shows straight away whether it is sitting with the approving manager or the finance system. Lanes can be people or systems; the rule is that each lane has one owner who can be asked about the work in it.
The arrows that cross between lanes are where work usually waits
Inside one lane, work tends to move quickly: the same person finishes one step and starts the next. Between lanes it stops. The order lands in another team’s queue, behind their own priorities, and nobody on either side is measured on the gap.
Count the lane crossings on your diagram. A purchase-to-pay process that crosses between approver and accounts payable eight times has eight queues, and each one adds days that no single team sees as its own. Reducing crossings, by moving an approval into the lane that already holds the work, often saves more time than speeding up any individual step.
This blind spot is one reason improvement programmes stall: about 88% of business transformations fall short of their original ambitions (Bain & Company press release, 15 Apr 2024).
Drawing a swimlane in BPMN takes four decisions, made in order
Business Process Model and Notation (BPMN) calls the whole diagram a pool and each row a lane. Most mapping tools follow it, which keeps your diagram readable by anyone trained in the standard.
- Choose the lanes: list every role or system that touches the work, and merge any two that never act independently.
- Place the start and end events: put the trigger in the lane where the work begins and the end event where it finishes.
- Draw the steps: add each task in its owner’s lane, with diamond gateways for decisions such as “approved or rejected”.
- Mark the waits: label each lane crossing with how long work typically sits there, measured from your system records.
Keep to six or seven lanes. Beyond that, split the process into two diagrams joined at a clear hand-off point.
Use a swimlane when several teams share the work, and a flowchart when one team owns it
If a single team runs the whole process, lanes add nothing but width, and a flowchart is quicker to draw. Swimlanes earn their place once two or more teams pass the work between them.
Once the diagram is drawn, record it where the team works. Our guide to business process documentation covers how to keep it current. The diagram also becomes the baseline for wider business process management work.
Check the swimlane against system timestamps before you trust it
Swimlanes drawn in a workshop show the hand-offs people remember. Event logs from your ERP record every one, with the time each order entered and left a lane. Process mining reads those logs and draws the real crossings, including the loops back to an earlier lane that rarely make it onto a whiteboard. Our process mining FAQ explains what data you need.
Zenotris maps processes from system event logs for mid-market operations teams, with over 100 engagements completed and the first measurable result targeted by week 8. An engagement on one process costs between $10,000 and $50,000.
The takeaway: take your current swimlane, find the lane crossing where work waits longest according to your ERP timestamps, and ask whether that step could move into the lane before it.
| If you need… | Use | Because | But |
|---|---|---|---|
| To show the order of steps in one team | Flowchart | Quick to draw and read | Hides who owns each step |
| To show ownership across teams | Swimlane diagram | Every hand-off is visible as a lane crossing | Grows unwieldy past six or seven lanes |
| The real crossings and their waiting times | Process mining | Reads each hand-off from event logs | Needs clean, timestamped data |
Find the hand-offs where your work waits.
First measurable result by week 8. $10,000–$50,000 per process.
Frequently asked questions
What is a swimlane diagram?
A process map drawn in horizontal rows, one per role, team or system, with each step placed in the row of whoever performs it.
When should I use a swimlane instead of a flowchart?
When two or more teams, or a team and a system, pass the work between them. For a process one team runs alone, a flowchart is enough.
How many lanes should a swimlane diagram have?
Six or seven at most. Beyond that, split the process into two diagrams joined at a clear hand-off.
What do pools and lanes mean in BPMN?
The pool is the whole process diagram; each lane is one participant inside it, such as a department or a system.