Process Mapping That Reflects Reality: What Good Looks Like Versus What Bad Looks Like

Process mapping is the practice of creating a visual representation of how a process works -- what steps occur, in what sequence, by whom, and with what inputs and outputs. In Lean and Six Sigma, process maps are foundational tools for understanding current-state performance, identifying waste and bottlenecks, and designing future-state improvements. They are also one of the most frequently misused tools, because organisations often map how they think a process works rather than how it actually works.

Here is what good process mapping looks like versus what bad process mapping looks like -- and how to ensure your process maps are useful rather than decorative.

What Bad Process Mapping Looks Like

• Bad: The process map was created from interviews or documentation alone, without direct observation. The most important question when creating a process map is not 'what does the procedure say?' but 'what do people actually do?' Procedure documents describe the intended process; interviews describe the process people think they follow; only direct observation reveals what they actually do. A process map created without observation will miss workarounds, informal steps, and decision points that are not documented.

• Bad: The process map shows one path through the process and no variation. Real processes almost always have multiple paths -- exceptions, error states, rework loops, and parallel branches. A process map that shows a single, linear flow is almost certainly an idealised version of the process, not the reality.

• Bad: The process map includes what should happen after a proposed improvement without first mapping what actually happens now. 'Future state' process maps are valuable, but they must be preceded by an accurate current-state map. You cannot identify waste without knowing what is currently happening.

• Bad: The process map is created by consultants or analysts without involving the people who do the work. The people closest to a process have the most accurate knowledge of how it actually functions. A process map created without their input will miss important steps and will not have their buy-in when it comes to identifying improvements.

What Good Process Mapping Looks Like

• Good: The process map was validated by direct observation. The mappers spent time on the floor, at the workstation, or in the operations centre observing the process being performed. They asked 'show me' not 'tell me.'

• Good: The map shows variation -- multiple paths, exception handling, and rework loops. The map reflects the real distribution of cases through the process, not just the happy path.

• Good: The map includes time data -- cycle time, wait time, and processing time at each step. Without time data, a process map shows what happens but not how long it takes. Time data is essential for identifying where delays occur.

• Good: Process practitioners reviewed and agreed the map before it was used for analysis. If the people who do the work do not recognise the map as accurate, the map is not accurate -- or the practitioners are performing the process differently from each other, which is itself a finding worth investigating.

XNM applies Lean process analysis and mapping techniques to public-sector and capital-project environments. Reach out to XNM's strategic advisory team to discuss process mapping and improvement for your organisation.