What is it?
A Value Stream Map shows how work and information move from a request to a completed outcome. It brings together the steps, delays, decisions and handovers so you can see where time is spent and where value is actually created.
What's it really for?
A Value Stream Map is a rather effective antidote to local optimisation. Every department may be busy, efficient and hitting its targets while the work itself goes nowhere in particular. The map changes the question from “How is my bit performing?” to “How well does the whole journey work?”
You know when…
The team proudly explains that each stage meets its target. Finance turns things around in two days, engineering in three, approvals in five. Someone then asks why the customer has been waiting eleven weeks.
There is a pause while everybody discovers that excellent parts do not automatically create an excellent whole.
Have a go
- Choose one clear product, service or request to follow.
- Map the work from customer need to completed outcome.
- Add activity time, waiting time, queues and information flows.
- Mark where value is created and where the journey stalls.
Why it works
Most organisations measure how long people spend doing the work, but customers experience the whole journey. A task may take twenty minutes and still sit in queues for twelve days. Putting activity time and waiting time on the same page makes that difference impossible to politely ignore.
Look for…
Waiting often outweighs working by a slightly embarrassing margin. Look for queues before approvals, repeated checking, batches, rework and places where information travels separately from the work. The longest delays are not always found in the busiest parts of the map.
Watch out…
Do not try to map the entire organisation in one heroic afternoon. Choose a meaningful value stream and follow one representative piece of work. A map that is broad enough to impress everyone is often too broad to improve anything.
Worth noticing…
The greatest opportunity is often not making the work faster. It is helping the work spend less time waiting for permission to continue.
Try next…
Use a Spaghetti Diagram when physical movement appears wasteful. Use Standard Work or a future-state map when the team is ready to redesign the flow.