Lean Methods · Guide

How to create a process map: a step-by-step guide

A process map makes how work really flows visible to everyone. This guide walks through the seven steps to create one — from choosing the process and gathering the people who do the work, to adding owners, timings, and the delays worth fixing first.

What is a process map?

A process map is a visual description of how work actually gets done — the steps, the order, the decisions, and the handoffs between people and systems. Its value is the shared understanding it creates: most teams find during their first session that no two people described the process the same way.

The symbols you actually need

• Oval (terminator) — start and end of the process.
• Rectangle (activity) — a single step someone performs.
• Diamond (decision) — a yes/no or either/or branch.
• Arrow (flow) — the direction work moves between steps.
• D-shape (delay) — waiting, queues, approvals sitting idle.
• Swimlane — who or which team owns each step.

How to create a process map in 7 steps

1. Pick one process and name it. Something concrete, like "customer order to shipment".
2. Agree the start and end point. The trigger and the finish; everything else is out of scope.
3. Gather the people who do the work. They know the real process, not the intended one.
4. List the steps before you draw. Verb + object, 10–20 steps at first pass.
5. Put the steps in order and add decisions. Mark every handoff — that's where delay lives.
6. Add owners, times, and pain points. This turns a diagram into a diagnosis.
7. Validate, then improve. Walk the map with an outsider, then fix the worst delay.

A worked example

1. Order arrives by email (start)
2. Sales checks the order details
3. Decision: credit approved? If no, finance review (delay: 1–2 days)
4. Warehouse checks stock
5. Decision: in stock? If no, purchase order to supplier (delay: 3–10 days)
6. Order is picked and packed
7. Carrier collects and the customer is notified (end)

Common mistakes

• Mapping the process as it should be instead of as it is.
• Starting with 60 steps instead of a high-level draft.
• Leaving out waiting time, which is usually most of the lead time.
• Drawing it alone and presenting it as fact.

FAQ

How long does it take to create a process map?

A first draft usually takes 45–90 minutes with the team in one room, plus a short session to validate it and add times and owners.

What's the difference between a process map and a flowchart?

A flowchart shows sequence and decision logic; a process map adds context — owners, durations, and where work waits. A value stream map adds information flow and a value-added vs. lead-time timeline.

Do I need special software?

No. Sticky notes work for the first draft. Digital tools matter afterwards, when the map needs to stay current and connect to improvement actions.

Related reading

• Process mapping examples
• Value Stream Mapping (VSM)
• What is Kaizen?