Value Stream Mapping
What is Value Stream Mapping?
Value stream mapping is a lean technique for drawing every step, handoff and delay in a process that delivers customer value, so teams can see where time is lost.
Updated November 2026 · 2 min read
Value stream mapping is a lean technique that draws the entire path a piece of work takes to deliver value to a customer, from the first request to the final result, including every step, handoff, approval and wait. Its purpose is to make waste visible. Most processes look reasonable step by step. Laid out end to end, with how long each step takes and how long work waits between steps, they usually show that most of the elapsed time is spent waiting.
The technique comes from the Toyota Production System. Mike Rother and John Shook brought it to a wide audience with their 1998 book Learning to See, and later work, such as Karen Martin and Mike Osterling's book on value stream mapping for office and knowledge work, adapted it beyond manufacturing. It is now widely used in software delivery, IT operations, finance, health care and services.
How to create a value stream map
- Choose one value stream, such as "customer-requested feature to production" or "new employee to fully equipped."
- Bring together the people who do the work at each step.
- Map the current state: each step, who does it, and for each step the process time (time actively working) and lead time (total time including waiting). Note rework rates, often recorded as percent complete and accurate.
- Calculate totals: total lead time, total process time and flow efficiency, process time divided by lead time.
- Find the biggest sources of delay and rework.
- Design a future state with fewer handoffs, shorter waits and less rework.
- Plan and carry out improvements, then map again.
An example
Consider a hypothetical bank mapping how a small change to its mobile app reaches customers. The team lists 14 steps. Total lead time is 42 days. Total process time, actual work across all steps, is about 3.5 days, a flow efficiency of 8%. The longest waits are a change advisory board that meets every two weeks (an average 7-day wait), a manual security review (9 days) and a shared test environment booked in advance (6 days). Testers also send back about 30% of changes because requirements were unclear. The future-state design replaces the advisory board with automated approvals for low-risk changes, builds security scans into the pipeline and has testers join refinement sessions. A year later, the same kind of change takes 9 days.
Common pitfalls
- Mapping the official process instead of how work really happens.
- Mapping without the people who do the work.
- A map with no follow-through.
- Mapping too much at once. Start with one value stream.
Value stream mapping is a one-time diagnostic. Value stream management measures flow continuously. The resulting improvements are tracked with flow metrics. See also value stream.
Frequently asked questions
How do you calculate flow efficiency in value stream mapping?
Divide total process time, the time someone is actively working, by total lead time, which includes all waiting. If a change takes 42 days end to end but only about 3.5 days of actual work, flow efficiency is roughly 8%. A low figure is common and shows that most elapsed time goes to queues, approvals and handoffs rather than work.
Who should take part in a value stream mapping session?
The people who actually do the work at each step of the value stream should map it together. Without them, teams tend to draw the official process instead of how work really flows, and they miss hidden waits, rework and workarounds. Having each step's participants in the room also makes it easier to agree on the future-state changes.
What is the difference between value stream mapping and value stream management?
Value stream mapping is a one-time diagnostic: a team draws the current flow of work, finds delays and designs a better future state. Value stream management measures flow continuously as an ongoing practice. Many organizations use mapping to find the biggest problems, then track improvement over time with flow metrics.
Related terms
Value Stream Management
Measuring and improving the whole flow from idea to customer value.
Flow Metrics
Measures of how much work flows, how fast and where it gets stuck.
WIP Limits
Caps on work in progress so teams finish work before starting more.
Sprint Velocity
How much work a team completes per Sprint, used for planning, not ranking.