Swimlane Diagrams: Who Does What, Without the Mess

By Kirill Stolbushkin

A swimlane diagram shows who does what. Each band is a role or system; each box sits in one band. In BPMN, a pool is a participant and a lane is a role inside that pool. Without lanes you have a to-do list with arrows. With them you can see the handoff — where work usually stalls.

That is the job. Not decoration. Not a rainbow of departments. Ownership.

What is a swimlane?

A swimlane is a horizontal or vertical band on a process diagram that groups steps by who performs them. “Who” can be a person, a role, a team, or a system. Every activity lives in one lane. Arrows that leave a lane are handoffs.

People sketch swimlanes in Lucidchart, Visio, Miro, and on whiteboards because unlabeled flowcharts hide the argument. “We approve invoices” is not a process. AP matches, the buyer explains the miss, the controller signs above a threshold. Put them in different lanes or you will keep having the same meeting.

A swimlane diagram is still just a diagram until the bands mean something in a standard. In BPMN 2.0 they do.

What is a swimlane in BPMN? Pool vs lane?

BPMN splits the metaphor into two levels, and mixing them is the most common mess.

A pool is a participant. Your company is a pool. The vendor is a pool. A new hire filling Section 1 of an I-9 is a participant, not an internal role. Work inside a pool is your process. Work in another pool is someone else’s. You do not sequence-flow into another company’s AP department. You send a message and you wait.

A lane is a role or system inside a pool. AP clerk. Controller. HR coordinator. The ERP. Lanes partition the work you control. They are not other companies.

Pool

Lane

What it is

A participant

A role or system inside a participant

Example

Your company; the vendor; the employee

AP clerk; controller; HR coordinator; the ERP

Connectors

Message flow (dashed) between pools

Sequence flow (solid) across lanes inside one pool

Common mistake

One giant pool named “Process”

A lane named “Finance” that hides three jobs

Read an invoice-approval flowchart without lanes and you will not know whether the three-way match is a person or a batch job. In BPMN the match sits in a system lane, the exception in the buyer’s lane, sign-off with the controller when the amount requires it. The handoff is the process.

If you cannot name the lane, you cannot name the owner. You have a drawing, not a process.

Horizontal or vertical process swimlanes?

Horizontal lanes (work flows left to right, roles stacked) are what most people mean by a swimlane diagram. Vertical lanes (work flows top to bottom, roles in columns) show up in some ITIL and manufacturing maps.

Pick one and stay there. Mixing orientations on one page is how you get the mess. For operational processes — invoice approval, vendor onboarding, employee onboarding — horizontal BPMN lanes are the default. Readers already know left is earlier.

Do not add a lane because a stakeholder wanted their logo on the page. Empty lanes are clutter. If a role never performs a task, they are a recipient of a message, not a swimmer.

How do I draw process swimlanes without the mess?

The mess is usually too many lanes, lanes that are departments instead of jobs, and arrows that cross because nobody wanted a gateway.

  1. List the work before you list the bands. Happy path only. Invoice received → match → approve → post. Vendor request → tax forms → contract → PO.

  2. Name roles, not org-chart continents. “Finance” is not a lane. AP clerk, AP lead, controller. “HR” is not a lane. Coordinator, hiring manager. If two titles always do the same task, they are one lane.

  3. Add a system lane when a system does the work. Three-way match, E-Verify lookup, account provisioning. If you put those in a person’s lane, you will staff a batch job.

  4. Put external parties in their own pool. The vendor sends a W-9. That is a message flow into your pool, not a lane labeled “Vendor” sitting under your logo.

  5. Keep the happy path in order. Then add exclusive gateways for the rules and parallel gateways for work that is actually simultaneous. Finance collecting tax forms while legal reads the MSA is a parallel split, then a join.

  6. One box, one lane. If a step “sort of” belongs to two roles, it is two steps or a badly named task. Split it.

  7. Label the handoff, not just the box. The arrow from AP to controller is “Amount > $5,000.” The arrow back to the vendor is “W-9 missing.”

  8. Stop adding color. Ownership is the lane name. If you need a legend to know who works, the lanes failed.

What are the usual ways process swimlanes go wrong?

The department dump. One lane per VP. Everything Finance does sits in a band the length of the page. You have shown who will be blamed, not who does the work.

The people dump. One lane per named human. When Jordan leaves, the diagram dies. Roles survive. Names belong in the org chart.

The happy-path lie. Vendor onboarding that never shows a missing W-9. I-9 that never shows day three. Swimlanes without exception paths are a poster.

Sequence flow between companies. A solid arrow from your buyer to the vendor’s lawyer. In BPMN that is a message, and the vendor’s lawyer is not in your pool.

Parallel work with no gateway. A stack of boxes in different lanes looks concurrent. It is not specified. Use a parallel gateway, then a join. The join is where people forget, and where work waits.

A lane named Approver with no rule. Whose approval? Over what amount? After how many days? That lane is a flowchart diamond in disguise.

Swimlane flowchart vs BPMN swimlanes

A swimlane flowchart is a flowchart with bands. Useful. Informal. No official meaning for task type, gateway type, or message vs sequence. Lucidchart and Visio will let you draw it in an afternoon.

BPMN swimlanes are pools and lanes in a model that can export XML. The band is not a styling choice. It is part of the language. Engines and other modelers can read who owns the task because the file says so, not because the PNG was labeled.

You need BPMN when the swimlane diagram has to be the spec: more than one team, real rules, a chance you will run it later. Invoice approval, vendor onboarding, and I-9 cross that line. Packing a sample kit does not.

How do I make a swimlane diagram of a process I already know?

Write it as a briefing, not as notation.

When an invoice arrives, AP matches it to the PO. If the match fails, the buyer resolves it. If the amount is $5,000 or less, the AP lead approves and AP posts. If it is over $5,000, the controller approves. If anyone rejects, AP sends it back to the vendor.

That paragraph already has lanes (AP, buyer, controller, vendor as a separate participant) and an exclusive gateway on amount. You can drag those bands in a diagramming tool. You can also paste the paragraph into a BPMN generator and get pools, lanes, and gateways without hunting for the pool icon.

Vevos generates BPMN 2.0 with swimlanes from a description, a photo of a whiteboard, or a SOP. The free mapper at vevos.ai/free needs no account. Intro is $0, three models. If the first draft dumps everything into one lane, say so: “Split Finance into AP clerk and controller.” Live deploy of a signed-off model is Conductor, from Tempo at $199/month. You do not need that to get the lanes right.

Who does what — on purpose

A swimlane diagram earns its keep when a stranger can see the handoff. If they cannot, you drew a flowchart and shaded it.

Try it at vevos.ai/free

Free to model · No credit card required

FAQ

What is a swimlane? A swimlane is a band on a process diagram that groups steps by who performs them — a role, a team, or a system. Each activity sits in one lane. Arrows that leave a lane are handoffs.

What is a swimlane diagram? A process map organized by those bands so ownership is visible. In informal tools it is a flowchart with rows. In BPMN 2.0 the bands are pools (participants) and lanes (roles inside a participant).

What is the difference between a pool and a lane? A pool is a participant: your company, a vendor, a new hire. A lane is a role or system inside that pool: AP clerk, controller, the ERP. Sequence flow stays inside a pool. Message flow crosses pools.

Should swimlanes be horizontal or vertical? Horizontal is the usual choice for operational processes: time left to right, roles stacked. Vertical appears in some IT and plant maps. Pick one. Do not mix. Do not add empty lanes for politics.

How many swimlanes should a process have? As many roles as actually perform work, and no more. Merge titles that share every task. Split “Finance” and “HR” until a new hire could be assigned the lane. External parties belong in another pool, not another lane.

Are swimlane diagrams the same as BPMN? No. Swimlanes exist in informal flowcharts and in BPMN. BPMN adds typed tasks, gateways, events, and XML. A swimlane flowchart is a sketch with owners. A BPMN model with pools and lanes is a spec.

Can AI generate a swimlane diagram? Yes. Describe who does each step. A BPMN generator should return pools and lanes, not a single undifferentiated canvas. Vevos does this from text, images, or documents; modeling starts free.

Try Vevos

Related