Mapping the Process People Actually Follow, Not the One on the Wall
Almost every organization has a process map somewhere — a tidy diagram in a binder or a slide deck, drawn the way the work is supposed to happen. And almost every organization runs on a different process, the one people quietly invented to get around the broken parts. In Lean Six Sigma terms, you cannot improve a process you have only described; you have to map the one that actually executes. With teams now split across home offices and sites, the gap between the official map and the real one has often widened, because the workarounds went undocumented and unshared.
Process mapping sits early in the Measure phase of DMAIC for a reason: if the map is wrong, every measurement, root-cause analysis, and improvement built on it is wrong too. Here is a checklist to map what is real, not what is on the wall, and you can start it this week.
Before you draw a single box
Walk the actual work. Do a Gemba walk — go to where the work happens (or screen-share the real system) and watch one real case move through end to end. Do not map from a meeting room.
Interview the doers, not just the managers. The people who run the process daily know every workaround. Ask 'what do you actually do here?' and 'when does this break?' rather than 'what is the procedure?'
Map a real instance, then a typical one. Follow one specific order, claim, or file by name and date. Specifics surface rework loops and waiting that an abstract map hides.
Mark every hand-off and every queue. Hand-offs between people, teams, or systems are where delay and error concentrate — especially when those people no longer sit together.
Signs your map has gone reality-blind
There are no rework loops or rejections drawn — real processes always have them.
Every box flows neatly forward with no waiting, no queues, no 'it sits in someone's inbox for two days.'
Nobody who does the work has reviewed it, so the workarounds are invisible.
It shows decisions but not who is waiting on whom — the hand-offs are missing.
A practical way to validate the map: walk it back to the team and ask them to point at where it lies. They will, immediately and cheerfully. The places they point are not failures of your diagram — they are your improvement opportunities, the spots where the official process and the survival process diverge. That divergence is the data.
Resist the urge to map the future state first. Until the current-state map is honest enough that the people in the room recognize their own day in it, any redesign is just a prettier version of the diagram in the binder. Map the truth, and the waste shows itself.
Getting an honest current-state picture before you redesign anything saves months of fixing the wrong problem — XNM's strategic advisory helps organizations see how their work really flows and where to improve it.