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

TL;DR

To create a process map: pick one process, agree its start and end points, list the steps with the people who do the work, put them in order, add decisions and handoffs, then note owners, durations, and pain points. Validate it with someone outside the session, and use the worst delays as your first improvement targets.

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 not the picture; it's the shared understanding it creates. Most teams discover during their first mapping session that no two people described the same process the same way.

Process mapping is the entry point to Lean. Once the flow is visible, waiting, rework, and duplicated effort become obvious — and you can start a continuous improvement cycle on the parts that hurt most.

The symbols you actually need

Standard notations list dozens of shapes. In practice, six carry almost every map:

How to create a process map in 7 steps

1. 1. Pick one process and name it

   Choose something concrete: "customer order to shipment", not "operations". A named process with a clear customer keeps the map from sprawling.

2. 2. Agree the start and end point

   Decide the trigger (a request arrives) and the finish (the customer has what they asked for). Everything outside those two points is out of scope for this map.

3. 3. Gather the people who do the work

   Managers describe the intended process; the people doing it know the real one. Map with them in the room — 45 minutes with the team beats a week of guessing.

4. 4. List the steps before you draw

   Write each step on a sticky note or a line in a list. Verb + object, one action each: "check stock", "approve discount", "pack order". Aim for 10–20 steps at first pass.

5. 5. Put the steps in order and add decisions

   Sequence the notes, then add the branch points where the flow splits. Mark every handoff between people or systems — handoffs are where delays live.

6. 6. Add owners, times, and pain points

   Give each step an owner (or swimlane), a rough duration, and a note where things regularly go wrong. This turns a diagram into a diagnosis.

7. 7. Validate, then improve

   Walk the map with someone who wasn't in the session. Fix what's wrong, then pick the one or two worst delays and run a small improvement cycle on them.

A worked example

Take a small company handling an incoming customer order. A first-pass map might read:

1. Order arrives by email (start)
2. Sales checks the order details
3. Decision: is the customer's 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)

Seven boxes, two decisions, two delays — and the two delays already account for most of the lead time. That is the whole point of mapping: the improvement target picks itself. For more patterns like this, see process mapping examples.

Common mistakes

• Mapping the process as it should be instead of as it is.
• Starting with 60 steps — begin high level, then zoom into the messy part.
• Leaving out waiting time, which is usually most of the lead time.
• Drawing it alone and presenting it as fact.
• Finishing the map and stopping there — a map that leads to no change is decoration.

How FollowLean fits

FollowLean is built for exactly this loop: draw the process visually, keep it current as the work changes, and attach improvement actions directly to the steps that cause delay. When you're ready to add flow data and timelines, the same map upgrades into a value stream map.

FAQ

How long does it take to create a process map?

A first draft of a single process usually takes 45–90 minutes with the team in one room. Validating it and adding times and owners typically takes another short session. Detailed, data-rich maps take longer, but you should never need weeks to get a usable first version.

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

In everyday use they overlap heavily. A flowchart shows the sequence and decision logic; a process map usually adds context — who owns each step, how long it takes, and where work waits. A value stream map goes further again by adding information flow and a value-added vs. lead-time timeline.

Do I need special software?

No. Sticky notes and a wall work perfectly for the first draft. Digital tools matter afterwards, when you want the map to stay current, be shared across teams, and connect to the improvement actions that come out of it.

How detailed should a process map be?

Detailed enough that someone outside the team can follow the flow, and no more. If a step never causes confusion, delay, or errors, it doesn't need to be broken down further.