Swimlane Diagrams: From 1940s Process Charts to Multi-Lane Workflows

A swimlane diagram (also called a cross-functional flowchart) places each actor in a row or a column and lets the work move across those bands. The boxes are still steps. The bands answer a question a plain flowchart leaves implicit: who has the work now?

An arrow that stays inside one band is work that role does alone. An arrow that crosses into another band is a handoff. A diamond, if you need one, is still a decision. A dashed arrow is a good place for the exception — the payment that fails, the protocol the review sends back — so the happy path stays readable.

Lanes can run horizontally or vertically. Horizontal lanes suit a left-to-right narrative and a slide. Vertical lanes suit a page that is already tall, or a board where each column is a department. The grammar does not change when you rotate the chart. Pick the direction that keeps labels large enough to read at the size you will print.

Multi-column process charts were already a tool of administrative analysis in the 1940s. In the United States, the Bureau of the Budget’s 1945 pamphlet Process Charting is a public landmark for that practice: office work drawn as a chart with columns, so a procedure could be followed across desks rather than as a single stack of boxes. Later writers treat that multi-column chart as one root of what training courses eventually called a swimlane.

The word itself belongs to a later generation of process teaching. Geary Rummler and Alan Brache’s Improving Performance (1990) put cross-functional maps, with a band per function, in front of a wide management audience. Drawing programs then offered “functional bands.” BPMN pools and lanes, and the partitions of a UML activity diagram, are the standards-shaped descendants: a lane is a participant, and a flow that crosses a boundary is a handoff.

A PDF that circulated at http://www.worksimp.com/articles/processcharting.pdf is the file many older pages still cite for the 1940s pamphlet. That URL is dead. This guide does not reprint that PDF, and it is not an official page of the Bureau, of any later publisher, or of any blog that linked the file.

Public summaries, including the origin note on the Wikipedia swim-lane article, are useful as a map of the lineage. They are not copied here. If you maintain a link to the Worksimp PDF, point readers at this HTTPS guide for the diagrams. The historical file itself is only a footnote: Archived source (PDF): processcharting.pdf. If the browser preview fails, download the file and open it.

Four pieces are enough to read any of the templates below.

• Lane — a role, team, or system. If two names always act as one, they are one lane.
• Phase — a group of columns (or rows) such as Order, Fulfill, Close. Phases keep a long chart from becoming a strip of unrelated boxes.
• Handoff — the next step sits in a different lane. That crossing is the reason to use a swimlane instead of a single column of steps.
• Split, merge, and loop — a split sends one item down two lanes at once (a feasibility note while a packet is in review). A merge is the step that cannot start until both arrive. A loop is a dashed return to an earlier lane, drawn so it cannot be mistaken for the main path.

The anatomy figure uses two lanes and a dashed return so those four words have a picture. The templates add real role names.

Start from a list of steps you could already say out loud. The chart is a rearrangement of that list, not a new process.

1. Name the actors. One lane each. If you have more lanes than a reader can hold without a key, merge roles or split the chart into two processes.
2. Name the starting document or event. An order, a protocol draft, a problem brief. Put it in the lane that creates it.
3. Follow the item. Each move is either more work in the same lane or a handoff. Do not skip the handoff by writing “the team handles it” in a single box.
4. Mark exceptions with a dashed arrow. Returns, rejects, and retries should look different from the path you want.
5. Star the step that hurts. Slow, unclear, or duplicated work gets a mark. A swimlane that only celebrates the official path hides the reason you drew it.

Then redraw it in the AI diagram maker. Say the lane names, the direction, and which arrow is dashed. Read every label against your list before you paste the figure into a slide. The model draws; it does not know your process.

These three charts were drawn for this page. They are not extracted from a manual. Use them as patterns: copy the shape, replace the nouns.

Order fulfillment

Customer, sales, warehouse, and billing. The order moves right. A failed payment is dashed, in billing, before the warehouse ships. That is the difference between a lane chart and a single “fulfill order” box.

Study startup

Investigator, IRB office, and department. This is a responsibility chart for getting a protocol open. It is not a CONSORT flow and it does not count participants. If what you need is the sequence of a study’s methods rather than the roles, use the research flowchart maker and keep the swimlane for the handoffs.

A product change

Product, design, and engineering. Design’s spec and engineering’s spike share a column on purpose: overlap is allowed. A swimlane is not a Gantt chart. It does not encode duration, and it should not be forced to carry a value-stream time ladder in the margin. If you need cycle time, add a separate note. Do not stretch the lanes into a timeline and pretend the boxes are to scale.

To regenerate a template, open the AI diagram maker and paste a lane list plus the steps. There is no separate flowchart-maker URL on this site; the diagram maker is the tool that draws this figure type.

• Too many lanes. A chart with a lane per job title becomes a roster. Merge until each lane is a decision-maker the reader can remember.
• Only the happy path. If every arrow succeeds, the dashed returns were the actual process, and you left them out.
• A value-stream map squeezed into lanes. Value-stream maps care about waiting time between steps. Swimlanes care about responsibility. Using one drawing for both jobs produces a crowded hybrid that answers neither question.
• One box that hides a handoff. “Team completes review” inside a single lane deletes the IRB, the department, or the billing desk you drew the chart to see.
• Confusing it with a study-reporting figure. A research flowchart shows steps of a study. A CONSORT diagram shows trial counts by arm. A swimlane shows who holds the work. One sentence in the caption should say which of the three the reader is looking at.

This page is a Vizcept rewrite, not a reprint. It is not an official publication of the U.S. Bureau of the Budget, of Worksimp, or of any later author who has discussed process charts.

The live Worksimp address no longer resolves: http://www.worksimp.com/articles/processcharting.pdf.

Archived source (PDF): processcharting.pdf, 12 October 2008. If the browser preview fails, download the file and open it. This page does not retype that file.

Lineage used in the short history, as public bibliographic pointers rather than as quoted prose: Bureau of the Budget, Process Charting (1945); Rummler and Brache, Improving Performance (1990); BPMN lanes and UML activity partitions as later standards. Wikipedia’s swim-lane article is a reasonable index of that public story. Follow it for orientation. Do not treat this guide as a mirror of that article, and do not treat a blog post that cited the dead PDF as the source of these templates.

If you are replacing a dead link, this is the stable HTTPS page for the diagrams. The archived PDF above is only the historical file.