# How to Make a Process Flow Diagram: A Swimlane Method

Canonical: https://sakura5.app/blog/how-to-make-a-process-flow-diagram/  
Published: 2026-10-28  
Author: the Sakura5 team · 8 min read  
Updated: 2026-10-28  
Publisher: Sakura5 (https://sakura5.app) · support@sakura5.app

> **TL;DR:** How to make a process flow diagram: set boundaries, list steps, assign owners, mark decisions, then draw swimlanes. Includes a full print-shop example.

![How to Make a Process Flow Diagram: A Swimlane Method](https://sakura5.app/img/blog/inline/how-to-make-a-process-flow-diagram-1.jpg)

To make a process flow diagram, name the process and its start and end points, list every step as a verb-first action, decide who owns each step, put the steps in order with the decision points marked, and then draw it as boxes and arrows — usually in swimlanes, one lane per person or team, so every handoff is visible. That’s the whole method. The rest is about getting the steps right before you draw anything.

A process flow diagram is worth the effort because it puts a process that lives in several people’s heads onto one page. Once it’s on the page, you can see where work waits, where it bounces between people, and where a decision has no clear owner. Those are the places where processes slow down, and they’re almost impossible to spot from a written procedure.

This guide covers what a process flow diagram actually is (the term means two different things), why first drafts go wrong, a step-by-step method, a full worked example of a print shop’s order process with real numbers, how to handle the awkward cases, and answers to the questions people ask most often.

## What a process flow diagram is — and the two things the term means

In business, a process flow diagram is a flowchart that shows how work moves through a process: the steps, the order they happen in, the decisions that branch the flow, and usually who does each step. It uses the same basic shapes as any flowchart — ovals for start and end, rectangles for actions, diamonds for decisions, arrows for flow. If you need a refresher on those, our guide to [flowchart symbols and meanings for beginners](https://sakura5.app/blog/flowchart-symbols-and-meanings-for-beginners/) covers the six shapes you’ll actually use.

In chemical and process engineering, a process flow diagram (often shortened to PFD) means something more specific: a drawing of a plant or system showing major equipment — tanks, pumps, heat exchangers, reactors — and the streams of material between them, often with flow rates and temperatures.

The two share an idea — things flow from one stage to the next — but they are drawn for different readers. This guide is about the business kind: the diagram an operations lead, a team manager or a student draws to understand and improve how work gets done.

## Why most first drafts of a process flow go wrong

The usual mistake is opening a diagramming tool first. Shapes snap together nicely, so it feels like progress, but you end up drawing the process as you imagine it runs rather than as it does.

![Why most first drafts of a process flow go wrong — how to make a process flow diagram](https://sakura5.app/img/blog/inline/how-to-make-a-process-flow-diagram-2.jpg)

*The usual mistake is opening a diagramming tool first.*

The second mistake is leaving out who does each step. A plain flowchart can show that an order gets approved, but not that approval sits with someone who works two days a week. In most real processes the delays happen between people, not inside a step, so a diagram without owners hides the most useful information.

The third is drawing only the happy path. A process flow that shows what happens when everything works is a description of the ideal. The rework loops and waiting states are where time goes.

## How to make a process flow diagram in six steps

For a process with 10 to 25 steps, plan on an hour or two, most of it spent on the first four steps. Keep those as lists or loose notes. Only start drawing at step five.

### 1. Set the boundaries

Write one line for the trigger that starts the process and one for the outcome that ends it. “Customer submits an order” and “Order delivered and invoiced” is a process. “Sales” is not. If there are several possible endings — approved, rejected, cancelled — list them all now.

### 2. Capture every step, in any order

List everything that happens between the trigger and the end, without sorting. Ask the people who do the work, and read the checklists, templates and tickets that already exist. It is easier to cut a step later than to discover a missing one after the diagram is drawn.

A mind map works well for this stage because it lets you collect steps without committing to an order. In [Mindmap AI](https://sakura5.app/mindmapai/) you can paste an existing procedure or a long description of the process, and the AI (a Pro feature) turns it into a map of its parts, which gives you a first inventory to correct instead of a blank page.

### 3. Rewrite each step as a verb-first action

“Check stock,” “Send proof,” “Print order.” Not “Stock” or “Proof stage.” A verb forces you to say what actually happens, and any label with an “and” in it is probably two steps. Keep every step at roughly the same size: “Handle the order” next to “Click Save” makes the diagram impossible to compare or improve.

### 4. Assign an owner and find the decisions

Next to each step, write who does it — a role, not a name, so the diagram survives staff changes. Then put the steps in order and mark every place the next step depends on an answer. Phrase those as yes-or-no questions with exactly two exits. Viewing the map as an outline helps here; Mindmap AI’s outline view shows the same nodes as a collapsible, ordered list you can check line by line against the real process.

### 5. Draw it in swimlanes

Make one horizontal lane per owner and place each step in its owner’s lane, flowing left to right. Every arrow that crosses a lane boundary is a handoff, and handoffs are where work waits. Label every arrow leaving a diamond “Yes” or “No.” The American Society for Quality keeps a clear reference on [flowcharts and when to use them](https://asq.org/quality-resources/flowchart), including the less common symbols.

### 6. Walk a real case through it

Take one recent, real instance of the process and trace it box by box. Every time the real case did something the diagram doesn’t show, fix the diagram. Then trace one case that went badly.

## A worked example: a print shop’s custom order process

Say you run a five-person print shop that makes custom T-shirts, and customers keep complaining that orders take too long. Nobody can say exactly where the time goes. Here’s how the six steps play out.

![A worked example: a print shop’s custom order process — how to make a process flow diagram](https://sakura5.app/img/blog/inline/how-to-make-a-process-flow-diagram-3.jpg)

*Three turn out to be duplicates described differently, leaving 14 steps.*

**Boundaries.** Start: “Customer submits order form with artwork.” Ends: “Order shipped and invoiced,” plus a second ending you only notice when you ask: “Order cancelled after proof rejected twice.”

**Capture.** A 20-minute conversation with the team produces 17 items: check artwork resolution, ask for better files, create a mockup, email the proof, wait for approval, check blank shirts in stock, order blanks from the supplier, print, cure, quality-check, fold and pack, print the label, ship, send the invoice, and a few more. Three turn out to be duplicates described differently, leaving 14 steps.

**Owners.** Four lanes: Customer, Sales (one person), Design (one person) and Production (three people who also handle shipping).

**Decisions.** Ordering the steps surfaces four diamonds: “Artwork usable?” “Proof approved?” “Blanks in stock?” and “Passes quality check?” The proof loop goes back to the Design lane, with “Fewer than 3 revisions?” deciding whether it continues or ends in cancellation.

**Drawing.** The finished diagram has 14 action boxes, 4 diamonds, 2 end ovals, and 9 arrows that cross a lane boundary. Six of those nine pass through Sales, because Sales forwards every email between the customer and Design.

**Walkthrough.** Tracing last week’s 40-shirt order for a running club shows it took 11 working days. Printing and packing took one. The proof sat in the Sales inbox for three days before reaching Design, and the approved proof sat another two before reaching Production. The bottleneck isn’t the printer; it’s Sales acting as a relay. The obvious experiment — Design emails proofs to the customer directly — removes four handoffs. If you mapped the steps in [Mindmap AI](https://sakura5.app/mindmapai/) first, the same map can be exported as a PDF outline (Pro) to hand the team before the meeting.

## Handling loops, waits and parallel work

**Loops.** When a step can repeat — resubmit artwork, revise a proof — draw the arrow back to the earlier box rather than redrawing the steps. Put the limit in the decision label if one exists, so the reader can see how the loop ends.

**Waiting.** Waiting is a step even though nobody is doing anything. If work sits for days — waiting for approval, for stock, for a weekly meeting — give it its own box, such as “Wait for supplier delivery (2–4 days).” That one box often explains more delay than everything else on the diagram combined.

**Parallel work.** When two things happen at once, like ordering blanks while the proof is being approved, split the arrow into two paths and merge them at the step that needs both. Don’t force them into a fake sequence.

**Too big for one page.** If the diagram passes about 30 boxes, collapse a section into a single “sub-process” box and draw it separately. Our guide to [making a flowchart for a process](https://sakura5.app/blog/how-to-make-a-flowchart-for-a-process/) covers the single-lane version of this method in more detail.

## FAQ

**What is the difference between a process flow diagram and a flowchart?**

A flowchart is the general format: shapes and arrows showing a sequence of steps and decisions. A process flow diagram is a flowchart applied to a business process, usually with swimlanes showing who owns each step. In chemical engineering, a process flow diagram instead shows plant equipment and the material streams between them.

**What should a process flow diagram include?**

At minimum, a clear start and end, every step written as a verb-first action, the decision points with labeled yes and no exits, and the owner of each step. Good diagrams also show waiting steps, rework loops and alternative endings, because those are where delays and errors usually hide in a real process.

**What is the easiest way to make a process flow diagram?**

Separate the thinking from the drawing. List the steps first as notes or a mind map, assign an owner to each, put them in order and mark the decisions. Only then draw the diagram in any tool you like. Once the steps are right, drawing a 20-step diagram usually takes well under an hour.

**How detailed should a process flow diagram be?**

Detailed enough that someone new could follow the process, but with every box at the same level of task. If a single box hides several people’s work, split it. If the diagram passes about 30 boxes, move a section into its own sub-process diagram so the main view stays readable on one page.

About the app: [MindMap AI: Mind Map Maker](https://sakura5.app/mindmapai/) · App Store: https://sakura5.app/go/mindmapai?from=/blog/how-to-make-a-process-flow-diagram/