A swimlane diagram is a process map divided into horizontal lanes, one per role or department, so that every step sits in the lane of whoever performs it. Its purpose is to make handoffs visible — because in most broken processes the failure is not inside any one lane, it is in the gaps between them.
What it produces
A cross-functional process map you build on screen: lanes by role, steps in sequence, and the handoff points where work crosses from one lane to another.
Who it is for
Teams diagnosing a process that spans departments — intake, billing, approvals, onboarding — where nobody owns the whole flow and delays accumulate at the boundaries.
How to read the result
Count the lane crossings. Every crossing is a queue, a potential delay, and a place accountability can be dropped. A process with more than five or six crossings almost always has rework hiding in it.
What the tool asks for
- Roles or departments involved
- Process steps in sequence
- Which role performs each step
- Handoff points between lanes
- Decision points and rework loops
Common questions
What is a swimlane diagram?
A process map organized into lanes by role or department, so each step is visibly owned. It is used to expose handoffs, queues, and gaps in accountability across a cross-functional process.
When should you use swimlanes instead of a flowchart?
Use swimlanes when a process crosses two or more roles or departments. A plain flowchart shows sequence; swimlanes show sequence plus ownership, which is what matters when the problem is a handoff.
What do handoffs tell you about a process?
Each handoff is a place where work waits, context is lost, and ownership becomes ambiguous. Handoff count is often a better predictor of cycle time than the number of steps.
How detailed should a swimlane map be?
Detailed enough that every handoff appears, no more. If a step never crosses a lane and never fails, it rarely needs decomposing.
Should I map the process as documented or as it actually runs?
As it actually runs. The gap between the two is usually the finding.
What do I do with the finished map?
Circle every handoff, then ask of each: does the receiving lane add value, or just approval? The approvals that add nothing are your first improvement candidates.
How many lanes is too many?
More than seven or eight and your process probably isn't one process. Split it.
Is it free, and can I export my diagram?
Free, no signup, no email required. Export as PDF, PNG, SVG, a standalone HTML viewer, or Visio (.vsdx); if your Visio version is picky about third-party files, use the SVG.
Related tools
SIPOC Explorer · Flow Bottleneck Calculator — or see the full Windy Hill Toolkit.
Built by Windy Hill Partners, a process improvement consultancy applying Lean Six Sigma and DMAIC. Every tool here is free and ungated at the point of use.