Why Your Process Map Lies, and How to Map What Actually Happens
A process map is supposed to be a mirror. Too often it is a brochure. It shows the clean, official version of the work — the one in the policy binder — while the actual process limps along through workarounds, side channels and undocumented heroics that nobody wrote down. When the map is a brochure, every improvement built on it is built on fiction, and the savings you projected never arrive.
This problem got sharper in early 2021. Teams that had moved to hybrid and remote work were running processes that had quietly mutated — approvals routed through chat instead of a system, handoffs delayed by people who were no longer down the hall. Maps drawn from memory of the pre-pandemic office described a workplace that no longer existed. If you are about to improve a process, the first job is to map the one you actually have.
Mistakes that produce a map of fiction
Mapping from the conference room. Drawing the process from managers' descriptions captures how work is supposed to happen, not how it does. The people doing the work daily know the real path — and the detours — far better than anyone briefing from a slide.
Hiding the rework loops. A clean left-to-right flow with no loop-backs is almost always a lie. Real processes are full of returns, corrections and 'send it back to step 3.' If your map has no rework arrows, you have not found the rework yet — you have just hidden the very waste you were hired to remove.
Leaving out the wait time. Maps that show only the value-adding steps make the process look efficient. But the queue between steps is usually where the days go. Capturing wait and delay is what separates a real value stream map from a flowchart.
Mapping the happy path only. The exceptions — the rush order, the missing signature, the rejected invoice — are not edge cases. They are often the majority of the volume and the source of most of the cost. A map that ignores them optimizes the easy 20 percent.
Calling it done after one pass. A map drawn once and filed is stale within weeks. If nobody returns to confirm it against the floor, it drifts back into being a brochure.
How to map what really happens
Mapping reality is mostly a matter of where you stand and whom you ask. The Lean tradition has a word for it — go to the gemba, the place where the work is done.
Walk the process with the people who run it, in the order the work flows, and ask them to narrate what they actually do — not what the procedure says.
Capture the real timing: how long each step takes, and how long the work waits between steps. The waiting almost always dwarfs the doing.
Draw every rework loop and decision point, including the informal 'kick it back' paths that never made the procedure.
Note where work changes hands; each handoff is a place where time, information and accountability can leak.
Validate the finished map by walking it again with a different person on the line. If their version disagrees, the map is not done.
When the map finally reflects reality, the improvement opportunities tend to announce themselves: the approval that waits two days for a signature, the rework loop that swallows a fifth of the volume, the duplicate data entry that exists only because two systems never talked. None of these are visible on the brochure version, which is exactly why mapping the truth is the highest-leverage hour in the whole project.
Resist the temptation to fix things while you map. Capture first, accurately and without judgement, so the people on the line keep telling you the truth. Improvement comes next — and it comes far easier when it stands on an honest picture.
If your processes have drifted from what the documentation claims, XNM's strategic advisory can help you map what is really happening and target the improvements that matter.