In 30 seconds
- Draw each step from idea to customer, with time spent in and between them.
- Waiting time usually dwarfs working time.
- Use it to find and fix the biggest delays.
Origins
Value stream mapping comes from lean manufacturing at Toyota and was popularized by Mike Rother and John Shook's 1999 book Learning to See. Software teams use it to map the path from idea to production.
Mapping a flow
- Pick one type of work, such as a typical feature.
- List every step: request, refine, build, review, test, deploy.
- For each step, note working time and waiting time before it.
- Add up total lead time and total working time.
Reading the map
Divide working time by total lead time. Many teams find work is actively worked on only a small fraction of the time; the rest is waiting. Fix the longest waits first, often with WIP limits, smaller batches or automation.
Myth vs reality
Myth · VSM is only for factories.
Reality · It works for any flow of work, including software.
Myth · The goal is to make people work faster.
Reality · The goal is to cut waiting, not to rush work.
Myth · One map fixes everything.
Reality · Map, improve, then map again.
FAQ
How long does a mapping session take?
A first map often takes half a day with the right people.
Who should attend?
Someone from every step in the flow.
What's a good first improvement?
Usually the longest wait, often approvals or handoffs.