Glossary

Swim Lane Diagram

A swim lane diagram is a process map split into parallel "lanes" — one per person, role, team or system — so each step sits in the lane of whoever owns it. It shows not just what happens but who does it and where work crosses from one lane to another, making handoffs and ownership gaps impossible to miss.

A swim lane diagram is a process map divided into parallel "lanes" — one for each person, role, team or system involved — so that every step sits in the lane of whoever is responsible for it. Like lanes in a swimming pool, each actor has their own track, and you can see who does what and exactly where work crosses from one lane into another.

Why a swim lane diagram matters

A swim lane diagram matters because it makes ownership and handoffs visible, which a plain flowchart hides. When you can see a process arrow leave the sales lane and enter the finance lane, you can see the precise moment work changes hands — and those crossing points are where most delay, error and "I thought you had it" failures occur. This is exactly the part of a system The Control Standard cares about: the system lives in the handoffs and the standards around them, not only in the boxes. The diagram turns an invisible handoff into a line you can point at.

Who invented it

The swim lane layout is generally attributed to performance-improvement pioneer Geary Rummler, whose cross-functional process maps in Improving Performance (1990, with Alan Brache) popularised drawing work by the function that owns it. The notation was later formalised as pools and lanes in the Business Process Model and Notation (BPMN) standard maintained by the Object Management Group, which is now the common language for these diagrams and the reason most modern tools render lanes the same way.

A swim lane diagram is usually the next step after a basic process map: once the steps are agreed, add lanes to show ownership. Watching where work crosses lanes also helps you spot the critical path — the chain of dependent steps that sets the shortest possible time to finish.

Frequently asked

What is a swim lane diagram used for?

It is used to map a process across more than one person, team or system, so you can see who owns each step and where work is handed over. It is especially useful for cross-functional processes — anything that passes between departments — because the handoffs between lanes are where delays and dropped work usually hide.

Who invented the swim lane diagram?

The lane-based layout is widely credited to performance-improvement pioneer Geary Rummler, who used cross-functional 'swimlane' maps in his 1990 work with Alan Brache. The notation was later standardised as 'pools and lanes' in the Business Process Model and Notation (BPMN) specification maintained by the Object Management Group.

Should lanes be horizontal or vertical?

Either works; the convention is simply to stay consistent. Horizontal lanes (the classic swimming-pool look) are most common and read left to right with time. Vertical lanes suit tall, sequential processes. What matters is that each lane is clearly labelled with its owner and every step sits in exactly one lane.

What is the difference between a swim lane diagram and a flowchart?

A plain flowchart shows the sequence of steps but not who performs them. A swim lane diagram is a flowchart organised into lanes by owner, so it answers 'who does this?' as well as 'what happens next?'. Use a plain flowchart for a single-owner process and swim lanes the moment work crosses roles or teams.

Term

Process Mapping

Process mapping is the practice of drawing a process as a step-by-step diagram — showing each task, decision, handoff and information flow from trigger to outcome. It makes invisible work visible, exposes where things stall, and creates a shared picture a team can agree on before they try to improve or automate anything.

Term

Critical Path

The critical path is the longest sequence of dependent tasks that determines the shortest possible time to finish a project. A delay to any task on the critical path delays the whole project; tasks off it have slack. Knowing yours tells you where a slip actually costs you time.

← Back to the glossary