Swimlane diagram best practices
Swimlane diagrams fail in predictable ways: too many lanes, vague step names, handoffs hidden inside a single lane, one map trying to show three processes. These eight rules keep a swimlane map readable months after you drew it.
1. One lane per role, not per person
Lanes should name roles or departments — "Finance", "Warehouse", "Account Manager" — not individuals. People change jobs; roles persist. A map with "Sarah" as a lane is stale the day Sarah moves teams.
2. Keep it under six lanes
Past five or six lanes, the eye can no longer track a connector across the map. If the process genuinely involves eight roles, that's a signal to split the map at a natural boundary (e.g. "intake" and "fulfilment") or to consolidate minor roles into one "supporting functions" lane.
3. Make handoffs the loudest thing on the map
Connectors that cross lane boundaries are the most important ink on a swimlane diagram — handoffs are where queues form, context gets lost, and SLAs break. Don't bury them: route them cleanly, label them when the trigger isn't obvious, and review them first when analyzing the process.
4. Name steps as verb phrases
"Approve invoice" beats "Invoice approval" and destroys "Invoice". A step is something someone does — the name should survive being read aloud as "then the role does X".
5. Label every decision branch
An unlabelled branch out of a decision diamond forces the reader to guess. Label both branches with the actual criterion: Yes/No at minimum, the business rule ("Over $10k / Under $10k") when it matters.
6. One start, explicit ends
Every map needs exactly one Start shape and at least one explicit End. Multiple unmarked endpoints make it impossible to tell whether a path is finished or just undocumented.
7. Map the as-is before the to-be
Document how the process actually runs today — including the workarounds — before drawing the improved version. A to-be map without an honest as-is is a wish, not a plan, and the delta between the two maps is where the improvement case lives.
8. Keep the source data editable
A swimlane map drawn as static shapes rots the first time the process changes — re-aligning lanes by hand is enough friction that nobody does it. Keeping the map as structured data (one spreadsheet row per step, lane as a column) means updating the map is editing a cell, so the map actually stays current.
Frequently asked questions
How many lanes is too many for a swimlane diagram?
More than six is usually too many. Split the process at a natural boundary or consolidate minor roles into a single supporting lane.
Should swimlanes be horizontal or vertical?
Horizontal lanes (roles stacked top to bottom, time flowing left to right) are the most common and read naturally on wide screens. Vertical lanes work better for processes presented on portrait documents. Pick one orientation per organization and stay consistent.
What's the most common swimlane mistake?
Hiding handoffs — drawing the process so most steps sit in one lane with the other lanes barely used. If 80% of steps are in one lane, either the lanes are wrong or the process didn't need a swimlane map.
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