What Is a Swimlane Diagram? Putting Cross-Department Work on a Single Page

You draw a business process and someone asks, "so who actually does this?" Listing steps in order does not convey ownership. A swimlane diagram solves that. This article covers lane design — how to split them and how to order them — which is the judgment specific to this kind of diagram.

What a Swimlane Diagram Is

A flow diagram divided into bands by owner, with each step placed inside the relevant band. The name comes from the resemblance to lanes in a swimming pool.

The difference from an ordinary flow diagram is that position carries meaning. Which band a step sits in determines whose work it is. You no longer need to write the owner's name inside the shape.

What becomes visible

The greatest advantage is that arrows crossing lanes stand out. Each of those arrows is a handoff.

Work stalls at handoffs more than anywhere else. A request was sent but the recipient did not notice; things are waiting on a review; something came back for a missing detail. Splitting into lanes lets you locate where these occur on the diagram.

Conversely, if no arrows cross lanes, you did not need swimlanes in the first place. Work that one person completes alone is fine as an ordinary flow diagram.

What to Split the Lanes By

The first and most important judgment. How you split determines what the diagram reveals.

Splitting by department

Sales, production, finance. This suits work with a lot of interdepartmental coordination, and it reveals where the load concentrates organisationally.

The caveat is that role divisions within a department stay invisible. Five steps sitting in the sales lane tell you nothing about whether one person does them all, or whether they split between an account owner and a manager.

Splitting by role

Requester, approver, executor, acceptor. This suits work where authority divides within a single department, such as an approval flow.

Splitting by role also insulates the diagram from staff moves and reorganisations. Draw it with department names and you will be redrawing it every time the org chart changes.

Which to choose

Decide by what the diagram is for. To review interdepartmental coordination, split by department. To hand over a procedure, split by role.

When in doubt, use role. Handover and explaining things to new joiners are the most common uses, and what those need is "which position does what."

The Order of the Lanes

Easy to overlook, but it has a large effect on readability.

The default is to order lanes the way the work flows. Requester, manager, finance — the sequence in which documents and data get passed along.

This aligns the crossing arrows in one direction and reduces intersections. Put a department with many touchpoints at one end, and its arrows will keep traversing the whole diagram until it becomes unreadable.