Swimlane diagram: Example and Use Cases

1 swimlane diagram example

Deal to invoice handoffs

How a closed deal crosses Sales, Legal and Finance before an invoice goes out.

Each lane is an owner, each arrow crossing a lane is a handoff, and handoffs are where deals stall. The accent marks the one that matters most: the signed contract reaching Finance.

Open in the editor

What is a swimlane diagram?

A swimlane diagram is a flowchart divided into horizontal or vertical lanes, one per person, team or system. Each step sits in the lane of whoever does it, so ownership and handoffs are visible at a glance. It is also called a cross-functional flowchart, and BPMN formalizes it as pools and lanes.

Read it along the flow of arrows. Every time an arrow crosses from one lane to another, work changes hands, which is where delays and errors usually happen.

When to use a swimlane diagram

Use it to map a process that crosses departments, such as the path from a signed deal to a sent invoice.
Use it to find bottlenecks and unclear ownership before automating or reorganizing a process.
If only one person or system is involved, a plain flowchart is simpler and lanes add nothing.

How to make a good swimlane diagram

Name lanes by role or team, not by individual, so the diagram survives staff changes.
Order lanes so the most frequent handoffs are between neighbors, which keeps arrows short.
Label each handoff with what is being passed, such as "signed contract" or "PO number".
Mark waits and manual rework explicitly; they are usually the reason the diagram was drawn.