Library→First Way: Flow→Tools & Techniques→Value Stream Mapping
Value Stream Mapping
The technique for making your value stream visible, measuring flow efficiency, and identifying where to improve.
Video Lesson
A video lesson for this topic is in development. The library articles and mission exercises cover the same material in the meantime.
What is VSM?
Value Stream Mapping is a Lean technique for visualizing the complete flow of work from request to delivery. It originated in Toyota's manufacturing system and was adapted for knowledge work by Karen Martin and Mike Osterling in Value Stream Mapping (2014) and for software by the DevOps movement.
A VSM produces two maps: the current state (how work flows today) and the future state (how it should flow after improvements). The gap between them is your improvement roadmap.
The standard VSM symbols
VSM uses a shared visual language so anyone reading the map understands it immediately. These are the core symbols used in software value stream maps.
VSM Symbol Legend
Process Box
A step where work is actively done
Inventory Triangle
Work waiting between steps
Push Arrow
Work pushed to the next step
Timeline
Shows process time vs wait time
Information Flow
How information moves between steps
Kaizen Burst
Improvement opportunity identified
How to run a VSM session
A VSM session is a structured workshop. It typically takes 4-8 hours for the current state map and another session for the future state. Bring the people who actually do the work — not just managers.
- 1
Define the product family
Choose one type of work to map. Do not try to map everything at once. Start with your most important product or feature flow.
- 2
Walk the value stream
Start from the customer and work backwards. Talk to every person who touches the work. Do not rely on what you think happens — observe what actually happens.
- 3
Draw the current state map
Document every step, queue, and information flow. Measure process time and wait time at each step. Calculate flow efficiency.
- 4
Identify waste and bottlenecks
Where does work pile up? Where are the longest wait times? Where does work get reworked or rejected?
- 5
Design the future state
What would the value stream look like if you removed the biggest waste? Draw the future state and define the improvement initiatives.
- 6
Create an implementation plan
Prioritize the improvements. Assign owners. Set a timeline. The VSM is worthless without action.
The Nexus Corp VSM in detail
In Mission 01, you built a VSM for Nexus Corp. Here is the complete current state map with all measurements:
| Step | Who | Process Time | Wait Time | Issues found |
|---|---|---|---|---|
| Idea to ticket | Product Owner | 2 days | 5 days | Specs too detailed, batch too large |
| Development | Developer | 3 days | 3 days | Waiting for code review |
| Code review | Senior Dev | 4 hours | 1 day | No dedicated review time |
| QA testing | QA Engineer | 2 days | 5 days | One shared test environment |
| ACC deployment | Ops Engineer | 1 day | 8 days | Must be scheduled, manual process |
| Production deploy | Ops Engineer | 4 hours | 12 days | Monthly release window only |
| Total | 7.5 days | 34 days | Lead time: 41.5 days — Flow efficiency: 18% |
5 of 6 steps have more wait time than process time. The two biggest wastes are the monthly production release window (12 days) and the ACC scheduling queue (8 days). Both are eliminated by continuous deployment.
Common VSM mistakes
Warning
Mapping the org chart, not the work
VSM maps the flow of work, not the organizational structure. Follow the work, not the departments.
Warning
Only using post-its
Post-it VSMs are great for workshops but need to be digitized. Measure actual times — do not guess.
Warning
Mapping everything at once
Start narrow. One product family, one end-to-end flow. Scope creep kills VSM sessions.
Warning
No future state
A current state map with no improvement plan is just documentation. The value is in the gap between current and future state.
Further reading
Learning to See — Rother & Shook
The original VSM workbook from Lean Enterprise Institute. Physical manufacturing focused but foundational for understanding the technique.
Value Stream Mapping — Karen Martin
The knowledge work adaptation. Directly applicable to software and service teams. The essential practical guide.
DevOps Handbook — Chapter 2
How VSM applies to software delivery and why the technology value stream is the central unit of improvement.
The Phoenix Project
Parts 1-2 show a fictional VSM in action at a struggling IT organization. The plant tour sequence is VSM in narrative form.