Value Stream Mapping charts every step a request passes through from initiation to delivery, recording for each one the processing time, the waiting time before it, and whether it adds value from the customer’s point of view.
The finding that justifies the effort is almost always the ratio between processing time and elapsed time. A file needing forty minutes of actual work routinely takes eleven days to move through an organisation. Everyone can see the forty minutes. Nobody owns the eleven days, which is precisely why they persist — and why speeding up the forty minutes changes almost nothing.
Maps have to be built by walking the process. Times come from observation, queue lengths from counting what is sitting in them. A map assembled in a meeting room describes the process as designed rather than as run, and the gap between those two is the entire subject.
The current-state map comes first and is not optional. A future state drawn before the current state is understood is a wish with arrows.
The waste is mapping a stream nobody intends to change. VSM is expensive in time and only repays it when the future-state map becomes a plan with owners and dates; maps drawn as analysis end up on a wall.
