Swimlane diagrams: what they are and how to make one

What lanes add to a flowchart

A plain flowchart tells you the order of steps. Lanes add responsibility. Each lane is labelled with an actor (Customer, Sales, Finance, Payment system) and every step is placed in exactly one lane. The diagram is sometimes called a cross-functional flowchart, because it crosses team boundaries.

Hand-offs, the arrows that cross from one lane to another, are the most informative part. Each one is a moment where work waits in someone else's queue, where information can be lost, and where responsibility can become unclear.

When to use swimlanes

• The process involves two or more people, teams or systems.
• You want to clarify who is responsible for each step.
• You are looking for delays: they often hide between lanes.
• You are documenting an integration between people and software, such as a step performed by an API.

For a procedure run entirely by one person, lanes add noise; use a simple flowchart instead. The types of flowcharts overview compares the options.

How to make one

1. List the actors. Keep it between two and six; group minor roles ("Back office") if needed.
2. Create one lane per actor, in the order they first appear in the process.
3. Place the steps in their owner's lane, in reading order.
4. Put decisions in the lane of the person who decides.
5. Connect the steps with arrows and label every branch of a decision.
6. Read the hand-offs: for each arrow that changes lane, ask what is passed on and how.

Horizontal or vertical lanes?

Both work. Horizontal lanes read left to right and suit wide processes. Vertical lanes (columns) read top to bottom, which suits screens and documents. Flowchartio uses columns, one per owner, with the flow running downward.

Systems as actors

A lane does not have to be a person. "CRM", "Payment provider" or "Identity API" are valid actors. Automated steps placed in a system lane make it obvious which parts of the process are manual and which are not. When you import an API specification, Flowchartio can bind those steps to real endpoints; see OpenAPI to flowchart.

Example

In a customer onboarding process, the customer submits an application, sales reviews it, the back office runs a KYC check and the system creates the account. Four lanes make the two hand-offs, from sales to back office and from back office to system, immediately visible.

Draw one from a description

Describe the process in a few sentences, naming who does what, and Flowchartio produces a swimlane flowchart with one column per owner. Naming the owner in each sentence is the most important tip in writing a process description. You can try it now.