Definition
Value Stream Mapping
Value stream mapping is a lean technique for diagramming every step work passes through from request to delivery, measuring the time spent in each. By distinguishing value-adding time from waiting and rework, it exposes where flow stalls. The goal is to maximize flow efficiency — the share of total lead time during which work is actively progressing.
Key takeaways
- Value stream mapping diagrams every step from request to delivery and measures the time spent in each.
- It distinguishes value-adding time from waiting and rework, exposing where flow actually stalls.
- Most lead time is usually waiting, not working — so attacking queues and handoffs beats asking people to work faster.
- Its target metric is flow efficiency: the share of total lead time during which work is actively progressing.
A value stream map follows a single unit of work end to end and records two numbers at every step: how long the step's actual work takes, and how long the work waits before and after it. Laid out together, these reveal an uncomfortable truth most teams share — the overwhelming majority of total lead time is waiting, not working.
That ratio is the prize. Value stream mapping makes flow efficiency visible: the percentage of lead time that is genuinely value-adding versus idle. When a feature takes three weeks to ship but only two days of real work, the bottleneck isn't the work — it's the queues, handoffs, and approvals between steps. Attacking those waits shortens delivery far more than asking people to work faster.
Originating in lean manufacturing, the technique transfers cleanly to knowledge work, where invisible queues — a ticket waiting for review, a deploy waiting for a release window — are the dominant cost. Mapping the stream turns those invisible waits into explicit, attackable targets and gives a team a baseline to measure improvement against.
Planoda's cycle-time and lead-time charts, drawn from each issue's state transitions, expose where work sits idle between stages — the same waiting time a value stream map sets out to eliminate.
Related terms
- Flow EfficiencyFlow efficiency is the percentage of an item's total time that was spent actively worked on versus waiting. If an issue takes ten days from start to done but only two were hands-on, its flow efficiency is 20%. Most teams are shocked to find theirs is low — proof that delays, not slow work, dominate delivery time.
- Lead TimeLead time is the total elapsed time from when an issue is first created or requested to when it is delivered. Unlike cycle time, it includes the waiting period in the backlog before work begins. Lead time reflects the customer's experience of how long a request actually takes end to end.
- Cycle TimeCycle time is how long an issue takes from the moment work actively starts on it to the moment it is done. Measured in hours or days, it captures the team's hands-on flow efficiency. Shorter, more consistent cycle times mean a more predictable system — the core flow metric Kanban teams optimize.
- Little's LawLittle's Law is a foundational result from queueing theory stating that, on average, the number of items in a system equals the rate items arrive (or complete) multiplied by the average time each spends in the system. For teams: average work in progress equals throughput times cycle time — which is why limiting WIP directly shortens cycle time.
- Cumulative Flow DiagramA cumulative flow diagram (CFD) is a stacked area chart showing how many items sit in each workflow state over time. The colored bands reveal flow health at a glance: a widening band means work is piling up in that stage, a steady set of parallel bands means smooth flow. It is Kanban's richest single picture of a system's behavior.