Value Stream Mapping

---

Origins

Value Stream Mapping (VSM) was codified by Mike Rother and John Shook in Learning to See (1999), drawing on Toyota Production System practice from the 1950s–80s.¹ The technique was originally developed for manufacturing — mapping how raw materials flow through processes to become finished cars — and was adapted to knowledge work by Karen Martin, Mary Poppendieck, and others in the early 2000s.²

What a VSM Is

A value stream map is a visual representation of every step in the journey from customer request to delivered value, with each step measured for:

• Process time (PT): the time spent actively working on the item in this step.
• Lead time (LT): the total elapsed time at this step, including waiting.
• % Complete and Accurate (%C&A): what fraction of work passes through this step without needing rework.

The map captures the actual current state — not the idealized version. Once captured, the team can identify waste, redesign the flow, and produce a "future state" map showing the target.

The Key Metrics

Total lead time

Sum of all step lead times. The customer-perceived delivery time.

Total process time

Sum of all step process times. The actual active-work time.

Activity ratio (Flow Efficiency)

Process time / lead time. Typically 5–20% in software (see Flow Efficiency Metrics).

Rolled %C&A

The product of each step's %C&A. Steps with 90% individually compound to much lower rolled values. Four 90% steps produces 66% rolled — only two-thirds of items pass through cleanly.

The Two Maps

VSM produces two maps in sequence:

Current state map

What is happening today. Captured by observation, not by assumption. Every wait, every handoff, every rework loop. The team typically discovers the current state is dramatically worse than they thought.

Future state map

What the team wants the value stream to look like. Specific changes named explicitly: eliminate this wait, merge these two steps, reduce this batch size, automate this handoff.

The future state map is then translated into an implementation plan — what changes get made, in what order, by when.

The Discoveries That Recur

Most knowledge-work VSMs reveal:

• Activity ratios of 5–15%. Most calendar time is wait, not work.
• Rolled %C&A under 50%. Half of work needs some kind of rework.
• Specific "stuck" steps — usually review, integration, deployment, or cross-team handoffs.
• Hidden rework loops nobody had explicitly named.
• Specialized "wait for X" queues — waiting for security review, legal approval, marketing input.

How a VSM Workshop Runs

• Pick a value stream: a specific journey (e.g., "from new feature request to feature in production").
• Walk it in person if possible: the genba walk. Observe each step happening in real time.
• Capture the map on a large wall: brown paper, sticky notes, the team gathered around it.
• Measure every step: PT, LT, %C&A.
• Identify the biggest wastes: usually the largest LT or the lowest %C&A.
• Design the future state: specific changes that address specific wastes.
• Plan the transition: sequence the changes, assign owners, schedule re-mapping.

A first VSM workshop typically takes 2–4 days. Subsequent maps are faster as the team learns the technique.

The Investment Question

VSM is heavier than simple process mapping. The investment pays back when:

• The value stream is large and crosses many teams.
• Cycle time problems are significant and persistent.
• Leadership is committed to acting on what the map reveals.
• There's no other comparably-detailed picture of the flow.

For smaller, single-team flows, simpler process mapping or even just adding "Doing/Done" sub-columns to a kanban board may produce enough insight. VSM earns its weight in larger, cross-functional contexts.

Coaching Tips

Walk the genba.

Observe the work actually happening. Imagined maps are fiction.

Measure every step.

PT, LT, %C&A. The numbers are the diagnostic; without them the map is just a flowchart.

Build the future state with the team.

Imposed future states don't get adopted. The team needs to own the changes.

Calculate rolled %C&A.

Individual step quality is misleading. The compound is the customer's experience.

Sequence improvements.

The future state map identifies many changes. Pick three high-leverage ones first; don't try to change everything at once.

Re-map after improvements.

Six months later, re-measure. The new current state becomes the baseline for the next future state.

Summary

Value Stream Mapping is the rigorous version of process mapping, with explicit measurement of waste, value-add time, and quality. By producing both a current-state and future-state map, the technique combines diagnosis with redesign in a single workflow. The investment is real — multiple days for a serious VSM — and the leverage is correspondingly high when the value stream is large, the cycle-time problems are significant, and leadership is willing to act. For smaller flows, lighter techniques suffice; for large cross-functional ones, VSM remains the gold standard.

Back to Flow & Forecasting