Swimlane diagrams explained: what, when and how to draw one

A swimlane diagram is a flowchart divided into horizontal or vertical bands, one band per person, team or system. Each step sits in the lane of whoever does it. The result shows two things at once: the order of the work and who is responsible for each part.

That second dimension is the whole point. A plain flowchart tells you what happens. A swimlane diagram tells you what happens and who does it, and, by extension, where work changes hands.

What a swimlane diagram is made of

The building blocks are the same as a flowchart, with one addition.

• Lanes: labelled bands, each representing one actor. An actor can be a role (“Customer”), a team (“Finance”) or a system (“Billing software”).
• Steps: rectangles placed in the lane of whoever performs them.
• Decisions: diamonds, also placed in the lane of whoever decides.
• Arrows: the flow from one step to the next. An arrow that crosses a lane boundary is a handoff.
• Start and end: rounded shapes, placed in the lane where the process begins and finishes.

If you need a refresher on the shapes themselves, flowchart symbols and what they mean covers each one.

When to use one

Choose a swimlane diagram over a basic flowchart when responsibility matters as much as sequence. Typical situations:

• Cross-team processes. Purchase approvals, customer onboarding and month-end close all involve several teams. The diagram shows each team its part.
• Diagnosing delays. Work often waits at handoffs. Seeing every lane crossing in one view makes those waiting points easy to find.
• Clarifying ownership. When two teams each assume the other handles a step, placing that step in one lane forces the decision.
• Explaining a process to an outside party. A client or auditor can see what they do, what you do and when they’ll hear back.

A swimlane diagram is less useful when one person does almost everything. If nearly every box sits in the same lane, a simple flowchart will be cleaner. And if a slide only needs to show the stages in order, without the question of ownership, process slide templates are a lighter option than lanes.

How to draw one in five steps

The example throughout is a purchase request at a mid-sized company in Bengaluru: an employee asks to buy a laptop, and the request moves through their manager, finance and the IT team.

1. Name the process and its boundaries

Write one sentence: “How a purchase request moves from the employee’s request to the item being delivered.” That fixes the start (request raised) and the end (item delivered).

2. List the actors

Write down everyone who touches the process. Keep it to the roles that actually do steps.

1. Employee
2. Manager
3. Finance
4. IT

Four lanes is comfortable. Six is workable. Beyond about seven, consider grouping minor actors or splitting the diagram.

3. List the steps and assign each to a lane

Step	Lane
Raise purchase request	Employee
Review request	Manager
Approved?	Manager
Check budget	Finance
Within budget?	Finance
Place order	Finance
Configure laptop	IT
Hand over laptop	IT
Receive laptop	Employee

If you can’t decide which lane a step belongs to, that is a finding in itself. Settle it with the people involved before you draw.

4. Lay out the lanes and place the steps

Draw the lanes as horizontal bands, labelled on the left. Order them so the flow mostly moves in one direction; here, top to bottom follows the request from employee to IT, then back up to the employee at the end.

Place steps left to right in time order. A step that happens later should sit further right, even if it’s in a different lane.

5. Draw the arrows and label the branches

Connect the steps. Label every exit from a diamond. In this example:

• Approved? → No returns to the employee lane with “Request declined”.
• Within budget? → No goes back to the manager lane for a decision on an exception.

Every path should finish at an end shape.

Reading the finished diagram

Once drawn, look at the diagram for three things:

Count the handoffs. Each arrow crossing a lane line is a point where work waits for someone else to pick it up. A process with many handoffs between the same two lanes may benefit from moving a step.

Look for back-and-forth. Arrows that bounce between two lanes several times often point to missing information at the first handoff. In the example, if finance regularly sends requests back to ask for a quote, the employee lane could add “Attach quote” at the start.

Check each lane’s load. A lane crowded with steps, especially decisions, may be a bottleneck.

If the aim is to redesign the process rather than document it, draw a current-state and a future-state version side by side; how to create a process map covers that method.

Layout choices that help

• Horizontal or vertical lanes? Horizontal lanes suit wide documents and slides. Vertical lanes suit tall pages and wikis. Choose based on where the diagram will be read.
• Keep lane labels visible. If the diagram is long, repeat the labels or freeze them on screen.
• Use one colour per lane, lightly. Pale fills separate the lanes without competing with the steps.
• Don’t shrink to fit. If the diagram won’t fit a slide, split it into phases rather than reducing the text size.

A starting outline

Before drawing, write down:

1. The process question in one sentence
2. The actors, one per line
3. The steps, each tagged with its actor
4. The decisions, as yes/no questions
5. Where each “no” branch goes

With that list, the drawing is mostly mechanical. It’s also the kind of plain description DiagramsPro can turn into lanes and steps directly.