Value Stream Mapping

Value stream mapping is a diagnostic tool. It shows you where the problems are. It does not fix them — that is kaizen’s job. But without a clear diagnosis, kaizen is guessing.

A value stream map captures the flow of materials and information from supplier to customer, including every process step, every delay, every handoff. At each step, you record data: cycle time, changeover time, uptime, operators, WIP. The map reveals the gap between processing time (actual value-added work) and lead time (total time from order to delivery). In most operations, processing time is 1-5% of lead time. The rest is waiting.

What VSM is not

• Not a process map. Process maps show steps. VSM shows steps plus data plus material flow plus information flow plus timeline. The data is what makes VSM a diagnostic instead of a picture.
• Not a one-time exercise. The current-state map is a snapshot. The future-state map is a plan. When the plan executes and the process changes, the current state must be remapped to capture the new reality. VSM is iterative.
• Not done from a conference room. Walk the value stream. Time the operations. Count the WIP. Talk to the operators. A VSM created from estimates and assumptions is fiction. A VSM created from observed data is a diagnostic.

The current-state map answers one question: what is actually happening right now? Not what the process document says. Not what the manager believes. What is physically happening on the floor, measured and recorded.

Data collection rules

• Walk the process. Physically follow the material from receiving to shipping. Record what you see, not what you are told.
• Time the operations. Use a stopwatch or video. Get at least 5-10 observations for each cycle time. Record the range, not just the average — the variation tells you about process stability.
• Count the WIP. Every triangle of inventory between process steps. Count it or estimate it, but get the number. WIP is where lead time hides.
• Record the data boxes. At each process step: cycle time (C/T), changeover time (C/O), uptime, number of operators, batch size if applicable. The data boxes are the diagnostic power of VSM.
• Map the information flow. How does the production schedule reach the floor? How do orders flow from customer to planning to production? Information flow reveals scheduling inefficiencies and communication gaps.

The current-state map is data. The next step is diagnosis: where does flow break? Where is the constraint? Not every red indicator on the map is a constraint. The constraint is the step that limits the entire value stream’s throughput.

The timeline reveals the truth

Processing time: 4.2 hours. Lead time: 11.4 days. Value-added percentage: 1.5%. That means 98.5% of the time, the material is sitting — waiting in a queue, sitting in WIP inventory, or being processed through non-value-added steps. The gap between processing time and lead time is your improvement opportunity. Closing that gap is what the future state targets.

Constraint vs. non-constraint improvement

Improving a non-constraint step does not improve the value stream. If the press is the bottleneck at 62-second cycle time and you kaizen the finishing step from 38 to 30 seconds, the value stream throughput does not change — the press is still the limiting factor. Improving a non-constraint is waste. Focus improvement on the constraint.

The future-state map shows what you want the value stream to look like after improvement. It is not a wish — it is a plan with specific targets, kaizen bursts at specific steps, and a timeline for execution.

Designing the future state

1. Start with takt time. Customer demand / available production time = takt time. Every process step must be capable of producing at takt. If a step’s cycle time exceeds takt, you need to either reduce the cycle time or add capacity.
2. Identify kaizen bursts. At each step where the current state does not meet the future-state requirement, place a kaizen burst. The burst specifies: what needs to change, what the target is, and what type of improvement (SMED, TPM, cell redesign, quality improvement).
3. Design flow. Eliminate WIP between steps where possible. Pull systems instead of push. FIFO lanes instead of batched queues. The future state should show less WIP, shorter lead time, and higher flow efficiency.
4. Plan the information flow. How will scheduling change? Can you move from MRP push to pull signals? Can you reduce the number of scheduling points? Simpler information flow enables simpler material flow.

Kaizen bursts are not vague

A kaizen burst that says “improve changeover” is useless. A kaizen burst that says “reduce Press 4 changeover from 28 min to 12 min using SMED methodology, estimated annual savings $84K (time reduction method)” is a plan. Each burst should specify:

• Current performance (measured, not estimated)
• Target performance (specific number)
• Improvement method (SMED, TPM, cell redesign, quality)
• Estimated savings and calculation method
• Owner and timeline

Before committing resources to a future-state improvement project, test the assumptions. Point estimates of savings are seductive but misleading. “$84K annual savings” sounds precise. But it assumes stable volume, constant cost, and 100% improvement realization. None of these are certain.

Monte Carlo simulation

Run 1,000 simulations with three sources of uncertainty:

• Volume volatility (±15% std): Customer demand fluctuates. A savings estimate based on average volume does not account for months where demand drops 20% or spikes 30%.
• Cost variation (±10% std): Material and labor costs change. The savings estimate should reflect this uncertainty.
• Improvement realization risk (Beta(4,2), mean ~67%): Not every kaizen delivers 100% of its target. A SMED project that targets 12-minute changeover might achieve 16 minutes. The realization rate accounts for this gap.

What simulation tells you

• Median savings: The 50th percentile outcome. More reliable than the deterministic point estimate.
• Confidence bands: P5 and P95 give you the range. “Savings likely between $42K and $118K” is more honest than “$84K.”
• Probability of positive return: What is the chance this project saves money at all? A project with 92% probability of positive return is a different commitment than one with 55%.

Use simulation to prioritize the kaizen burst portfolio. When you have five bursts on the future-state map and resources for three, simulation tells you which three have the highest expected value adjusted for risk.

VSM is the diagnostic. Hoshin kanri is the execution structure. The connection between them is the kaizen burst promotion pipeline.

The promotion criteria

Not every kaizen burst belongs on the X-matrix. Promote when:

• The burst aligns to a strategic or annual objective
• Expected savings exceed the hoshin threshold (typically $25K+)
• The improvement requires cross-functional resources
• Monthly savings tracking is needed for accountability

Bursts that do not meet these criteria execute through MDI as local improvements. Important, but not hoshin-level.

Closed-loop tracking

The lifecycle is not complete until realized savings write back to the VSM. When a hoshin project executes and generates monthly savings, those savings update the kaizen burst on the map. The VSM becomes a living document: constraint identified → project executed → savings realized → map updated → next constraint identified. Without the write-back, the VSM is a one-time artifact. With the write-back, it is a management tool.

Future-state promotion

When all kaizen bursts on a future-state map are completed and verified, the future state becomes the new current state. The old current state is archived. Metric snapshots carry forward. The cycle restarts with a new current-state map that reflects the improved process. This is continuous improvement at the value stream level.

In the Campaign Framework, VSM serves as the diagnostic that informs both the Shape and Execute phases. It tells you where to shape (which areas need 5S and visual management preparation) and where to execute (which constraints to target with kaizen).

VSM and shaping

The areas identified as constraints on the VSM are the areas that need shaping first. If the press is the bottleneck, the press area gets 5S attention before the SMED event starts. Shadow boards fabricated. Tool locations standardized. Changeover procedures documented. The shaping enables the execution.

VSM and execution

The kaizen bursts on the future-state map define the execution portfolio. Each burst is a PDSA experiment — try the improvement, measure the result, study what happened, decide whether to standardize or iterate. The VSM provides the context: why this improvement, at this step, with this target.

VSM and consolidation

After kaizen execution, the VSM provides the verification framework. Did the constraint move? Did lead time decrease? Did the WIP reduction hold? Remap the value stream (or update the map with actual post-improvement data) to verify that the future state was achieved. If it was not, understand why and iterate.

When to remap

• After major kaizen events: Update the map with actual post-improvement data to verify results
• Annually: Full remap to capture cumulative changes and identify new constraints
• After significant changes: New product introduction, equipment change, volume shift, supplier change
• When the constraint moves: If the bottleneck was the press and SMED kaizen resolved it, the constraint has moved. Remap to find the new constraint.