Swimlane Diagram: How to Map a Process by Role, with Example and Template

A swimlane diagram answers a question that comes up in almost every workflow sooner or later: whose turn is it now? It gives every role involved its own lane and shows how a case travels from lane to lane, from the order in sales through accounting to shipping. Those transitions are where most of the day-to-day friction sits, and the diagram makes them visible at a glance.

This guide explains what a swimlane diagram is and how it differs from a flowchart and from BPMN. After that come a five-step method, a worked example from order processing and a template you can copy into PowerPoint, Word, Excel or a diagramming tool. A swimlane diagram is one format within process documentation, and the guide there shows how it fits together with the process map, the process description and the work instruction.

What is a swimlane diagram?

A swimlane diagram (also called a cross-functional flowchart, which is the name Visio uses) is a process diagram that divides the page into parallel lanes. Each lane belongs to a role, a department or a system. Every process step sits in the lane of the role that performs it, and arrows connect the steps in the order they happen.

Three elements carry the diagram:

• Lanes represent the participants, for example customer, sales office, accounting, production, warehouse. Each lane is labelled at its edge.
• Steps and decisions are the boxes and diamonds inside the lanes. A step is an activity with an output, a decision is a branch with labelled exits.
• Handoffs occur wherever an arrow crosses the border between two lanes. Responsibility changes hands here, and this is typically where a case waits longest.

The format was popularised by Geary Rummler and Alan Brache in their book "Improving Performance" (1990), which looks at work across the organisation chart. Their point was that the interesting parts of a process lie in the white space between the boxes on the org chart, at the handoffs from one department to the next.

Process diagram as the umbrella term

"Process diagram" covers any visual representation of a workflow. That includes the simple flowchart, the swimlane diagram, BPMN models, event-driven process chains and value stream maps. A swimlane diagram is one particular kind of process diagram: the one with lanes for responsibility.

Horizontal or vertical?

Both orientations are common. Horizontal lanes, with time running from left to right, fit slides and landscape pages well and are the more widespread variant. Vertical lanes, with the flow running top to bottom, suit long processes with few participants, because they work on a portrait page or a wiki page you scroll down. Pick one orientation for the whole company and stick with it so that every diagram reads the same way.

Swimlane diagram vs flowchart vs BPMN

All three show a workflow with steps and decisions. They differ in how much they say about responsibility and how strict their rules are.

So a swimlane diagram is a flowchart with lanes. BPMN adopts the lanes as pools and lanes and adds a precise notation for events, messages between participants and data objects. A BPMN diagram with lanes is therefore always a swimlane diagram, while the reverse does not hold.

For documentation in a small or mid-sized company, a swimlane diagram with five shapes usually does the job: start, step, decision, arrow and end. Reach for BPMN when a process is going to be implemented in a system or automated and the notation has to be unambiguous.

Where the roles are already settled and only responsibility needs clarifying, a RACI matrix complements the diagram. It records for each task who does the work, who is accountable, who is consulted and who is informed. The swimlane diagram adds the order in which the tasks run and where they change hands.

How to create a swimlane diagram in 5 steps

Drawing goes quickly. Most of the time goes into the knowledge that belongs in it: who actually does which step, where work is passed on and which exceptions exist. The five steps follow that order.

Step 1: Set the scope and the roles

First decide where the process starts and where it ends, for example "order received" to "invoice issued". A SIPOC helps you capture that scope on one page with suppliers, inputs, outputs and customers.

Then collect the roles that do something in the process. The most reliable source is conversations with the people who do the work. Ask each person what they receive, what they do with it and who they pass it on to. Every role they name becomes a lane. How to run these conversations and which as-is process mapping methods suit them is compared in that guide.

Name the lanes after roles. "Sales office" stays correct when someone changes jobs. Five to seven lanes is a sensible upper limit, beyond that the diagram gets hard to read.

Step 2: Place the steps in their lanes

Enter the steps in the order they happen in practice, each one in the lane of the role that performs it. Use a verb and an object, such as "create order in ERP". One step per box, and every box has an output that the next step needs.

Step 3: Mark the handoffs

Every arrow that crosses a lane border is a handoff. Label it with what is handed over, such as "order confirmation", "production order" or "delivery note", and with how it arrives: ERP status, email or paper. These arrows are where you will later see work piling up.

Step 4: Add the decisions

Decisions are diamonds in the lane of the role that decides. Every exit gets a label, usually "yes" and "no" or concrete conditions such as "under 5,000 euros" and "5,000 euros or more". A diamond with a single exit is an ordinary step and belongs in a box.

Step 5: Add exceptions and review

Finally, ask about the exceptions: rush orders, missing documents, customers with special terms. Note small deviations as a comment on the step and give larger ones their own path. Then walk through the diagram with two or three of the people who do the work. Once everyone recognises their own lane and confirms the handoffs, the diagram is done.

Example: order processing from sales to shipping

The following example (typified) is put together from typical workflows and does not describe a real company: a manufacturer of industrial components with 120 employees that ships standard parts from stock and makes variants to order. The process starts with the customer's order and ends with the invoice.

As a swimlane in table form, the workflow looks like this. Each row is a lane, each column a phase, and the numbers give the order:

The handoffs can be read straight off the diagram:

In a diagramming tool you turn this into five horizontal lanes and connect the steps in numerical order. Step 5 runs in parallel with production: the order confirmation goes out as soon as the delivery date is known.

Three things stand out in the example. In the normal case the arrows cross eight lane borders when the goods are in stock and nine when they are made to order. Accounting is involved twice, once at the front for the credit check and once at the end for the invoice. And the handoff from the shop floor to the warehouse depends on a completion report in the ERP. If that report is missing, finished parts sit in the staging area while shipping has no idea they are ready. Spots like this are the starting point for a process analysis and for process optimization.

Exceptions noted on the diagram: rush orders skip the scheduling in step 6 and go straight to the production manager. Customers with a framework agreement are exempt from the credit check in step 3. Partial deliveries trigger a separate invoice for each delivery.

Copyable template: visualise processes in PowerPoint, Word and Excel

The template has two parts: a profile that collects the knowledge, and a lane grid for the steps. You can copy both directly.

Swimlane diagram: <process name>
Version / date / process owner (role)

Start (trigger):     <event that starts the process>
End (result):        <what exists at the end>
Orientation:         horizontal / vertical

Lanes (roles, max. 7):
  1. <role>
  2. <role>
  3. <role>

Steps:
  No. | Step (verb + object) | Lane | Output | Handed to | Channel
  ... decisions as separate rows with their exits

Exceptions:
  <exception> -> <alternative path or note>

The lane grid as a table, for five lanes and five phases:

How to build the grid in common tools:

• PowerPoint and Word: Insert a table with one row per lane, hide the inner vertical borders and place shapes for steps and diamonds for decisions on top. Connectors from the shapes menu stay attached when you move the shapes.
• Excel: Each row is a lane, each column a phase. For simple workflows, text cells with numbers as in the example above are enough. For a visual version, draw shapes over the grid.
• Visio and draw.io: Both ship ready-made swimlane shapes. In Visio the template is called "Cross-Functional Flowchart", in draw.io you find pools and lanes in the shape library.

Which tool you choose depends on where the diagram will be read. If it lives inside the process description, Word fits. PowerPoint is handy for workshops and presentations, and when many processes need to link up, a diagramming tool with a library pays off.

What makes a good swimlane diagram

A good swimlane diagram can be read by someone who does not know the process, and everyone involved finds their own work in it. These points help:

• Start and end are drawn as their own shapes.
• Each lane carries the name of a role.
• Each step sits in exactly one lane and has an output.
• Each diamond has at least two labelled exits.
• Arrows cross as rarely as possible, and loops back are easy to spot.
• The diagram fits on one page. If it grows longer, split the process into sub-processes and link from one diagram to the next.
• The header shows version, date and process owner.

The diagram rarely stands alone. The process map shows where the process sits in the company, the swimlane diagram shows its flow across roles, and the process description holds the details such as systems, deadlines and related documents. If you run a quality management system to ISO 9001, this combination makes traceable part of what clause 4.4 of the standard requires: determining the sequence and interaction of the processes and assigning responsibilities and authorities for them. The standard does not prescribe a particular format.

From conversation to diagram

A diagram is only as good as the knowledge in its lanes. That knowledge lives with the people who run the process every day: the sales office, who know which customers always order by fax, and the warehouse team, who have their own proven way of booking partial deliveries.

This is where wissa.ai comes in. An AI interviews your employees in chat sessions of around 15 to 20 minutes, whenever it suits them. It asks what someone receives, what they do with it and who they pass it on to. When the sales office names a colleague in accounting as the next station, the AI suggests that colleague as the next interviewee, and you approve the invitation.

The interviews produce process documentation with roles, steps, handoffs and exceptions, each statement traceable to its source. If two people describe a handoff differently, the contradiction is flagged. That documentation is the basis you draw the swimlane diagram from, and it keeps growing with every further interview. The page on process documentation software shows what this looks like day to day. To get started there is a free trial package (10 credits, once per company, terms) that is usually enough for a first interview. Try one interview for free

Summary

A swimlane diagram is a flowchart with lanes for responsibility. It shows on one page who performs which step and where a case changes hands. For most workflows five shapes and five to seven lanes are enough, and BPMN comes in when a process is to be automated.

Creating one follows five steps: scope and roles, steps, handoffs, decisions, exceptions. The template above gets you to a first draft in a few minutes, and the conversations with the people doing the work fill the lanes with what actually happens.

FAQ

What is a swimlane diagram?

A swimlane diagram is a process diagram in which every role involved has its own lane. Each step sits in the lane of the role that performs it, and arrows show the order. Wherever an arrow moves from one lane to another, a handoff takes place. It is also called a cross-functional flowchart or a Rummler-Brache diagram.

What is the difference between a swimlane diagram and a flowchart?

A flowchart shows the order of steps and the branches in a workflow. A swimlane diagram adds lanes, so you also see who performs each step and where responsibility changes. A flowchart is enough for work within one team, while a swimlane diagram is clearer for work across several departments.

What is a process diagram?

A process diagram is any visual representation of a workflow with steps, decisions and connections. Common forms are the flowchart, the swimlane diagram, BPMN models and event-driven process chains. Which one fits depends on whether you need only the sequence, the responsibilities as well, or an executable notation.

How do I make a swimlane diagram in PowerPoint or Word?

Insert a table with one row per role and label the first column with the role names. Place rectangles for steps and diamonds for decisions on top and join them with connectors from the shapes menu. The template in this guide gives you the profile and the grid to copy. Visio and draw.io offer ready-made swimlane shapes.

Are swimlanes part of BPMN?

Yes. BPMN 2.0 has pools for the participants in a process and lanes for roles within a pool, so every BPMN diagram with lanes is a swimlane diagram. BPMN also defines exactly how events, messages between pools and data objects are drawn, which a simple swimlane diagram does not require.

How many lanes should a swimlane diagram have?

Five to seven lanes is a good guideline. With more, the arrows get long and the diagram is hard to read. Merge roles that have only a few steps, such as warehouse and shipping, or split the process into two diagrams that reference each other.

Sources

• Rummler, Geary A.; Brache, Alan P.: Improving Performance. How to Manage the White Space on the Organization Chart. Jossey-Bass, 1990
• Object Management Group: Business Process Model and Notation (BPMN), Version 2.0, 2011; version 2.0.2 (2013) published as ISO/IEC 19510:2013
• ISO 5807:1985, Information processing: Documentation symbols and conventions for data, program and system flowcharts, program network charts and system resources charts
• ISO 9001:2015, clause 4.4 (Quality management system and its processes)