Process Mapping

Process mapping is the practice of drawing a process as a step-by-step diagram — every task, decision, handoff and information flow from the moment it starts to the outcome it produces. It turns work that normally lives in people's heads into something a whole team can see, point at and agree on. Most improvement and automation efforts fail not because the idea was wrong but because nobody could see the actual process clearly enough first.

Why process mapping matters

Process mapping matters because you cannot fix, standardise or automate a process you cannot see. NHS England, which uses process mapping heavily in service improvement, treats it as one of the most valuable steps a team can take to understand what is currently going on before any change is made. The map becomes a single source of truth the team can argue over and align on, instead of each person defending a different mental version of how the work is "supposed" to go.

How to map a process

The reliable way to map a process is to walk it with the people who actually do the work, capturing each step in sequence. Start with the trigger, list every task and decision through to the outcome, then mark the handoffs — the points where work passes from one person or team to another. Those handoffs are where delay, error and dropped balls cluster, which is exactly why The Control Standard treats the system as living in the handoffs, information flows and standards between steps, not only in the steps themselves. A swim lane diagram is the natural next move once you need to show who owns each lane. For a shared, standardised notation, the Business Process Model and Notation (BPMN) specification maintained by the Object Management Group gives everyone the same symbols to read.

Process mapping is the groundwork for systemising. Map first, agree the current state, then improve or automate from a clear picture rather than paving over a broken process.