Swimlane Diagrams
Part of the Business Analyst Roadmap
In short
A plain flowchart shows what happens. A swimlane diagram also shows who does it, and that's exactly where you spot the ping-pong between teams that makes customers wait.
A process diagram organized into horizontal or vertical lanes representing different roles or departments — making clear exactly who is responsible for each step, and where handoffs happen.
Think of it like this
A relay race
In a relay, every runner has their own lane, and the baton passes between them. Races are often lost at the handoff, not in the running. Swimlanes show each team's lane and every baton pass, so you can see where it gets dropped.
Watch it happen
A refund passing between lanes
Return request
1/6The customer's lane starts the process. Each actor here is one swimlane.
The big ideas
What you need to know
One lane per role
Each lane is a person, team, department or system. Steps sit in the lane of whoever does them.
Handoffs are visible
Any arrow crossing a lane line is a handoff. Count them. Fewer handoffs usually means less waiting.
Spot ping-pong
Work bouncing between two lanes repeatedly signals unclear ownership or missing information.
Systems get lanes too
Give the CRM or payment system its own lane to show what's automated and what's manual.
Save yourself the pain
Common mistakes
Oops
Giving lanes to individual people's names.
Do this instead
Use roles like 'Support agent' or 'Finance team', so the diagram stays true when people change.
Oops
Drawing every lane even if it only has one step.
Do this instead
Merge or drop lanes that add nothing. Five or six lanes is usually the limit for readability.
Your mission
Swimlane a food order
Quick check
What does an arrow crossing from one swimlane into another represent?
Go deeper
- 1Build a swimlane diagram for a cross-departmental process (e.g. order fulfillment).
- 2Learn why handoff points between lanes are often where processes break down.
- 3Practice identifying an unnecessary handoff that could be eliminated to simplify the process.
More topics at this stop
Business Process Modeling Basics
BPMN (Business Process Model & Notation)
Process Flowcharts
As-Is vs To-Be Process Mapping
Gap Analysis
Process Improvement Techniques (Lean, Six Sigma Overview)
Root Cause Analysis (5 Whys, Fishbone)
Value Stream Mapping
Stuck on this topic? Ask an Insider
Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.
