Swimlane: who does what in a process

A swimlane is a lane in a process diagram that assigns the steps a role, department or person is responsible for. It makes clear at a glance who does what and when — and where the workflow hands off from one party to the next. The name comes from a swimming pool: each lane belongs to exactly one swimmer.

What swimlanes are good for

A plain flowchart shows you the steps. A swimlane adds the responsibility — and that’s exactly where friction lives in practice. Most processes don’t stall inside a department; they stall at the handovers in between.

• Clear ownership. Each step sits in exactly one lane. No more “is that my job or yours?”
• Handovers become visible. Every time an arrow jumps from one lane to the next, that’s an interface — and interfaces are where things get stuck.
• Bottlenecks stand out. If everything piles up in one lane, that’s often the bottleneck nobody could name before.

Horizontal or vertical

You can lay lanes out across or down — the logic stays the same.

Horizontal lanes

The lanes stack on top of each other and the process runs left to right. This is the most common variant and reads like a timeline: trigger up front, result at the end.

Vertical lanes

The lanes sit side by side and the process runs top to bottom. Handy when you have many roles but few steps — or the diagram needs to fit a tall format.

Rule of thumb: one lane per role, not per person. Pin the process to names and you’ll redraw it with every staffing change. Roles stay stable; people move on.

What really matters: the handovers

The real value of a swimlane isn’t in the boxes — it’s in the arrows that cross lanes. Ask at each handover: is it clear what’s being handed over? Is the recipient maybe waiting for something that never arrives? This is exactly where the days hide — the ones a task spent “sitting somewhere” without anyone being able to say where.

Common mistakes

• Too many lanes. Eight roles in one picture and nobody follows it anymore. Cut more coarsely and push the detail into a sub-process.
• Notation over value. Strict BPMN swimlanes with pools, events and gateways look professional — but scare off the people who actually live the process. For “who does what,” clarity is enough; no modelling school required.
• Draw once, never maintain. A swimlane goes stale the day responsibility shifts. If it then hangs on the wall as a poster, it points the wrong way.

From lane to living workflow

A swimlane is most useful when it shows how work really happens — not how it was once meant to. When the assignment grows directly out of ongoing process documentation and stays part of the process map, it updates almost on its own. That’s exactly where ProcessCollector comes in: you capture who owns which step, and the handovers stay visible instead of disappearing into the detail.

Bottom line

A swimlane answers the question a flowchart leaves open: who’s up? Its value lies at the handovers — where responsibility shifts and things get stuck. It only stays valuable when it’s current and doesn’t turn into a notation exercise.