Definition
A value stream map is a visual diagram that captures the complete end-to-end flow of material and information required to deliver a product from raw material to the customer. It documents every process step, the inventory between steps, the information systems that trigger production, and the time each unit spends in the system — both value-adding processing time and non-value-adding waiting time.
The purpose is diagnostic: to see the entire value stream as a system rather than optimizing individual processes in isolation. By mapping both the current state and a desired future state, it focuses improvement efforts on the changes that will have the greatest system-level impact on lead time, flow, and waste elimination.
Japanese Origin
Mono to joho no nagare zu (モノと情報の流れ図) translates to “material and information flow diagram.” This is Toyota’s internal name for the practice. At Toyota, the emphasis is always on both flows: the physical flow of material through the factory and the information flow (orders, schedules, kanban signals) that directs production. Most production problems are rooted in disconnects between these two flows.
The term “value stream mapping” was coined by the Lean Enterprise Institute to describe this practice for a Western audience. The LEI publication Learning to See by John Shook (a former Toyota employee) made the method widely accessible outside Toyota.
How It Actually Works
Current state mapping:
- Select a product family — a group of products that pass through similar processing steps. Map one family at a time.
- Walk the value stream — physically walk the process from shipping dock back to receiving dock (upstream), observing and recording at each step.
- Record process data — at each operation, capture cycle time, changeover time, uptime, batch size, number of operators, and available work time.
- Record inventory — between each process, count the actual inventory (WIP, finished goods, raw materials) and convert it to days of supply.
- Map information flow — document how each process knows what to produce: MRP schedules, kanban signals, verbal instructions, electronic orders. Map the flow from customer order through the planning system to each process.
- Calculate the timeline — at the bottom of the map, draw a timeline showing processing time (value-adding) and queue/wait time (non-value-adding) at each step. Total these to show overall lead time and the ratio of value-adding time to total lead time.
Future state design:
Using the current state map as the diagnostic, design an improved value stream that:
- Establishes continuous flow where possible (linking adjacent processes)
- Installs pull systems (supermarkets with kanban) where flow is not possible
- Levels production through heijunka
- Reduces changeover times to enable smaller batches
- Establishes a single scheduling point (pacemaker process) rather than scheduling every operation independently
Implementation planning:
Break the future state into achievable improvement loops. Each loop targets a specific section of the value stream. Implement in sequence, starting from the customer end (shipping) and working upstream. Each loop becomes a concrete kaizen project with defined scope, timeline, and ownership.
Implementation Guidance
Map with pencil and paper. Value stream maps are drawn by hand, not in software. The act of walking the process and recording observations by hand forces direct engagement with reality. Software-generated maps from system data miss the physical reality of the shop floor.
Map what you see, not what should be. The current state map must reflect actual conditions — actual inventory levels (count them), actual cycle times (measure them), actual information flows (trace them). Aspirational current state maps are useless for diagnosis.
Focus on one product family. Trying to map everything at once creates confusion. Select the product family that is most important (highest volume, most problematic, or most strategic) and map it completely before moving to the next.
Use standard symbols. The value stream mapping icon set (process boxes, inventory triangles, push/pull arrows, information flow lines) provides a common visual language. Use it consistently so that anyone trained in the method can read any map.
Common Mistakes
Mapping without improving. A value stream map is a diagnostic tool, not an end in itself. Creating beautiful current state maps that are posted on the wall and never acted on is a common failure mode. The map exists to reveal improvement opportunities; the value is in the improvements.
Optimizing individual processes instead of the stream. The entire point of value stream mapping is to see the system. Kaizen at individual operations (faster cycle time at one machine) may not improve the overall value stream if the constraint is elsewhere. The map guides where to focus.
Ignoring information flow. Many value stream maps focus on material flow and treat information flow as an afterthought. At Toyota, the information flow is often where the biggest problems hide — MRP systems that schedule every operation independently, long planning cycles that delay response to demand changes, manual order entry that introduces errors.
Never revisiting the map. The value stream changes as improvements are implemented, demand shifts, and products evolve. Periodic re-mapping (at least annually for critical value streams) keeps the diagnostic current and identifies the next round of improvement opportunities.