Blog / Guides 5 min read ·

After the process map: measure it, then plan the fix

A finished process map feels like the end of the work. It is the middle. The map shows where the handoffs, loops and waits are; it does not say which of them matter most, or how the fix will actually happen. Two more diagrams do that: one that puts numbers on the paths, and one that turns the chosen change into a plan.

A map is a diagnosis

Most process maps end with a workshop full of ideas: remove this approval, merge those two steps, stop sending the form back. All of them are plausible, and there is rarely time for more than one or two. The map alone cannot rank them, because every path on it is drawn the same width whether one case a year takes it or a thousand a week do.

Measure: put volumes on the paths

Count how many cases take each path over a normal month: how many go straight through, how many loop back for rework, how many wait at each handoff. The numbers usually come from the system the process runs in, or from a week of tally marks.

A Sankey diagram shows those numbers on the process itself: each step is a node, and the band between two steps is as wide as the number of cases that make that move. The rework loop that looked minor on the map turns out to carry a third of the volume, or the scary exception turns out to happen twice a year.

Pick one change

With volumes on the paths, the choice is usually obvious: the change that touches the most cases, or removes the longest wait on a busy path. Redraw the swimlane map as it will be after the change (the to-be map) and check it with the people in each lane: every handoff you remove is a conversation someone no longer has to have, and every one you add is a new place for work to wait.

Plan the fix as a project

Even a small process change has steps that depend on each other: agree the new process, update the form or the system, train the people in each lane, pilot it with one team, roll it out, and review the numbers again. A Gantt chart puts dates on those steps and shows which ones hold up the rest. Many teams run it as a short kaizen event: a week of preparation, a few days of workshop, and a follow-up plan.

Choosing a method

Lean, Six Sigma, PDCA and the other improvement methods each give this loop of measure, change and check a different emphasis. QueryChart's guide walks through them step by step.

Frequently asked questions

What do you do after mapping a process?

Measure it, then change one thing. Count how many cases take each path on the map, pick the change that affects the most cases or removes the longest wait, draw the to-be map, and plan the change with dates and owners.

How do you show volumes on a process map?

With a Sankey diagram drawn over the same steps: each step is a node and each band is as wide as the number of cases that take that path, so the busiest paths and the biggest rework loops stand out.

Try it on your own process

The editor is free and opens with a starter template. One row per step — the swimlane diagram renders as you type. No signup required.

Start Process Mapping Free