Value Stream Mapping (VSM) is a Lean management technique that visualizes the flow of materials and information required to deliver a product or service from initial request to customer delivery. Originally developed for manufacturing by Toyota, VSM has evolved into a foundational tool for DevOps, software delivery, and process improvement across industries. The core insight: most time in any process is spent waiting, not working — Flow Efficiency in typical organizations averages just 5-15%, meaning 85-95% of lead time is pure waste. VSM makes this invisible waste visible, enabling teams to identify constraints, eliminate bottlenecks, and design flow-optimized future states that dramatically reduce delivery time while improving quality.
What This Cheat Sheet Covers
This topic spans 31 focused tables and 266 indexed concepts, 134 flashcards. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
A jump-to index of every table row in this cheat sheet.
An interactive map of every table and concept in this topic.
Table 1: Core Concepts & Definitions
The fundamental vocabulary of VSM comes from Toyota's Production System and Lean thinking; without internalizing these definitions, maps are drawn but waste stays hidden. These terms form the shared language that makes cross-functional conversations about flow precise rather than vague.
| Concept | Example | Description | |
|---|---|---|---|
Idea → Code → Build → Test → Deploy → Customer | All actions (value-added and non-value-added) required to deliver a product or service from start to customer delivery | ||
Documenting actual process with measured cycle times, wait times, handoffs | Visual representation of how work actually flows today, based on direct observation at the gemba (where work happens) | ||
Redesigned process eliminating 3 handoffs, reducing lead time 40% | • Envisioned improved state designed to reduce waste, smooth flow, and meet customer demand • typically targets 6-12 months ahead | ||
Zero-queue, single-piece flow process with no handoffs or waiting if all constraints removed | • Ultimate optimized state representing the best-possible process with all waste eliminated and no constraints • used as a north star beyond the next future state | ||
Order placed Monday → delivered Friday = 5 days lead time | • Total elapsed time from customer request initiation until delivery • includes all wait time and active work time | ||
Developer actively codes feature for 6 hours | • Time to complete one unit of work from start to finish of active work • excludes wait time before work begins | ||
Assembly step takes 45 seconds per unit | • Active work duration required to complete a specific process step • also called value-add time or touch time | ||
$\text{Takt} = \frac{28800 \text{ sec}}{400 \text{ units}} = 72 \text{ sec/unit}$ | • Customer demand rate — available production time divided by customer demand • sets the pace the process must run to meet demand | ||
$\text{Efficiency} = \frac{8 \text{ hrs active}}{120 \text{ hrs total}} \times 100 = 6.7%$ | • Ratio of active work time to total lead time • reveals how much time is productive vs waiting • typical organizations: 5-15% | ||
Writing code, assembling components, customer consultation | Activities that transform the product in ways the customer is willing to pay for | ||
Waiting for approvals, moving items between locations, rework | • Activities that consume time/resources but do not increase customer value • often necessary but targets for elimination | ||
15 features currently being developed across team | • Amount of work started but not yet completed • high WIP increases lead time per Little's Law | ||
Testing team processes 20 items/day while dev produces 40/day | Process step with the lowest capacity that constrains throughput of entire value stream |