How to create a swimlane diagram
How to create a swimlane diagram: choose lanes by who owns the work, put each step in the lane that does it, and make every lane change a visible handoff. Includes a live example you can step through.
A swimlane diagram is a process flowchart split by owner: each lane belongs to a role or team, every step sits in the lane that performs it, and each crossing between lanes is a handoff.
The short version
- One lane per accountable role, not per person and not per department.
- Four or five lanes is the readable ceiling; more than that, split the process.
- A step goes in the lane that performs it, not the lane that gets blamed for it.
- Every line crossing a lane boundary is a handoff: that is where the delay lives.
- In QueryChart, lanes are two spreadsheet columns: owner and phase.
What the lanes are actually for
A swimlane diagram answers a question a plain flowchart cannot: who is holding this right now. That matters because operational processes rarely fail inside a step. They fail between steps, in the gap where one team has finished and the next has not started, and nobody has noticed because each team's own checklist looks complete. Splitting the flow into lanes makes those gaps the most visible thing on the page.
The lanes are the design decision. Pick them by accountability, not by org chart: one lane per group that can be held responsible for finishing a step, which is usually a role or a function rather than a person or a department. Four or five lanes is the practical ceiling: past that the crossings turn into a tangle and the diagram stops being readable, which is a signal to split the process rather than to shrink the font.
QueryChart's swimlanes run on two axes at once. The vertical lanes are the owners; the horizontal lanes are the phases of the process, so a step is placed by naming both. The example below is a real employee onboarding flow across four owners and six phases, the process most likely to be four separate checklists that all have to finish on the same morning.
Watch a swimlane diagram get built
A cross-functional onboarding process across four owner lanes and six phases. Each stage below adds one lane's worth of work, and one handoff.
Start in one lane
HR alone, in the offer-and-contract phase. A lane only appears once a step is assigned to it, so at this point the diagram looks like an ordinary flowchart, which is exactly what it is until work changes hands.
Put the decision in the lane that owns it
The background check is HR's, but the exception call is not: an exception belongs to the hiring manager, so the diamond sits in the hiring manager's lane. Decisions are the easiest thing to put in the wrong lane, and it is the mistake that makes people argue about who was supposed to act.
The handoff is the point
Provisioning drops into IT and then Facilities, and you can now see the two crossings that decide whether day one works. Note the fallback: equipment that will not arrive in time routes to a loaner kit rather than leaving the new hire without a laptop.
Work comes back across the lanes
Day one runs HR to IT and back, then the first week sits with the hiring manager. Handoffs go both ways in a real process; a diagram where work only ever flows downward is usually a diagram of a wish.
Every lane ends its own branches
Probation closes in the hiring manager's lane with two outcomes: confirmed, or extended with a support plan. Each lane should finish its own work rather than leaving a line trailing into someone else's.
How it works
List the roles before you list the steps
Write down every group that has to do something, then merge until you have four or five. Merge by accountability: if two names always act together and would be chased as one, they are one lane. A lane per individual person guarantees the chart is wrong the next time somebody changes job.
Name the phases across the top
Phases are the horizontal lanes: the stages of the process, like Screening, Provisioning, Day one. They give the reader a sense of time without pretending to be a schedule, and they make it obvious when one phase is carrying twice the work of the others.
Type the steps as rows and set both lane columns
In QueryChart each row carries a Horizontal lane (the phase) and a Vertical lane (the owner). Open the spreadsheet view under the example above to see it: a swimlane diagram is a plain table with two extra columns, and the layout is derived from them rather than dragged into place.
Put each step in the lane that does the work
The test is who would be chased if the step were late. Not who cares about it, not who reports on it, but who does it. Steps parked in the lane of whoever complains loudest are the reason lane diagrams get quietly abandoned.
Look hard at every crossing
Each line that crosses a lane boundary is a handoff, and handoffs are where processes stall. For each one, ask how the receiving lane finds out it has work: a ticket, an email, a shared queue, or nothing at all. "Nothing at all" is a finding, and it is usually the finding worth having.
Check the lane balance, then circulate it
A lane with one box may not need to exist; a lane with fifteen is probably three roles wearing one hat. Adjust, then share the chart with every lane owner and capture their sign-off, so the diagram is something the teams agreed to rather than something one person drew about them.
Mistakes to avoid
Lanes copied from the org chart
Departments are not owners. "Operations" as a lane hides the three teams inside it that actually hand work to each other, and the diagram ends up with no visible handoffs at all, which is precisely the information a swimlane diagram exists to show.
A lane per person
Name roles, not people. People move; the process is supposed to outlive them. It also stops the diagram from becoming a document about individuals, which is what makes reviewing it uncomfortable.
Nine lanes
Past about five, the crossings dominate and nobody can trace a path. Either the scope is too wide (split it into two processes with a defined handoff) or several lanes are really one.
Decisions in the wrong lane
A decision belongs to whoever makes the call, which is often not whoever prepared the information. Getting this wrong is how a chart ends up implying that an analyst approves their own work.
Create your own swimlane diagram
Open the onboarding example as your own chart, rename the lanes to your teams, and replace the steps.
Related guides
Frequently asked questions
What is the difference between a swimlane diagram and a flowchart?
A flowchart shows sequence and logic. A swimlane diagram shows the same sequence split by who performs each step, so responsibility and handoffs become visible. Every swimlane diagram is a flowchart; the lanes are what turn it into a picture of an organisation rather than just a picture of a procedure. If a process stays inside one team, lanes add nothing; use them the moment it crosses a boundary.
Should swimlanes be horizontal or vertical?
Convention is horizontal lanes with the flow reading left to right, which is what most people find easiest to scan. QueryChart uses both axes at once: vertical lanes for owners and horizontal lanes for the phases of the process. That combination means you can see both who is acting and how far through the process they are, without either dimension being implied by position alone.
How many swimlanes should a diagram have?
Four or five. Two or three is common and perfectly good for a process that crosses one boundary. Beyond about five the crossings overlap enough that tracing a single path takes effort, and the usual fix is not a bigger canvas but a smaller scope: split the process at a natural handoff and give each half its own chart, with the handoff itself as the end of one and the start of the other.
Where do external parties like suppliers or customers go?
In their own lane, whenever their action is part of the flow. A supplier submitting an invoice, a customer confirming a complaint is resolved, a candidate accepting an offer: these are steps the process waits on, and hiding them inside an internal lane makes the wait invisible. Putting them in a lane also makes it obvious how much of your cycle time is not actually yours.
