Why Value Stream Mapping Exists
Most improvement efforts in manufacturing focus on individual operations: “Speed up the CNC,” “Reduce changeover time at press 3,” “Add an inspector at Station 7.” These are local optimizations. They may improve one operation while leaving the system unchanged — or worse, they may improve a non-constraint and create no benefit at all while consuming improvement resources.
Value stream mapping forces you to see the whole. Instead of asking “how can we make this step faster?” it asks “what happens to this product from the moment material arrives until the customer receives it?” The answer is always humbling. A part that takes 3 hours of actual machining may spend 6 weeks in the factory. An aircraft with 18,000 labor hours of work content may take 14 months to deliver. The vast majority of that time is not value-add — it is waiting.
Current-State Mapping: What Is Actually Happening
A current-state map captures reality, not aspiration. You build it by walking the floor — not by reading ERP reports in a conference room. Here is the step-by-step process:
Select the Product Family
Map one product family at a time — a group of products that share similar processing steps. In aerospace, this might be “all wing skins” or “fuselage panels for the 737 program.” Do not try to map everything at once.
Walk the Flow Backward
Start at shipping and walk backward to raw material receiving. At each step, record: cycle time (C/T), changeover time (C/O), uptime, batch size, number of operators, available time, and the inventory count between operations. Use a stopwatch and count inventory yourself — do not trust the ERP numbers.
Map Information Flow
How does each operation know what to work on next? Is it an MRP dispatch list? A supervisor’s verbal instruction? A kanban card? Map where production information originates, how it travels, and how often it is updated. Information flow problems cause as much waste as material flow problems.
Build the Timeline
Below the process boxes, draw a stepped timeline. The bottom steps show value-add time (cycle time at each operation). The top steps show lead time between operations (inventory days). Add them up to get total lead time and total value-add time. The ratio is your Process Cycle Efficiency.
Product family: Aluminum wing rib machining (12 part numbers, similar processing).
Customer demand: 200 parts/month. Available time: 20 days × 460 min = 9,200 min/month. Takt time: 9,200 ÷ 200 = 46 min/part.
| Operation | C/T (min) | C/O (min) | Uptime | Batch | Operators | WIP Before (days) |
|---|---|---|---|---|---|---|
| Raw Material | — | — | — | — | — | 15 days |
| CNC Rough | 38 min | 45 min | 82% | 25 | 1 | 5 days |
| CNC Finish | 42 min | 30 min | 88% | 25 | 1 | 8 days |
| Deburr | 12 min | 0 | 100% | 1 | 1 | 3 days |
| Anodize (external) | — | — | — | 50 | — | 10 days |
| Inspect | 8 min | 0 | 100% | 1 | 1 | 4 days |
| Ship | — | — | — | — | — | 2 days |
Results:
- Total lead time: 15 + 5 + 8 + 3 + 10 + 4 + 2 = 47 days
- Total value-add time: 38 + 42 + 12 + 8 = 100 min (1.67 hours)
- Process Cycle Efficiency: 100 min ÷ (47 days × 460 min/day) × 100 = 0.46%
A part that requires 100 minutes of actual work spends 47 days in the system. 99.5% of its time, nothing is happening to it.
Reading the Current-State Map: Where Waste Hides
The current-state map reveals several patterns:
| Pattern | What It Tells You | In Our Example |
|---|---|---|
| Large inventory triangles | Material is queuing — usually because of batching, unreliable upstream, or push scheduling | 15 days raw material + 10 days at anodize = 25 days of inventory in two locations |
| Batch sizes > 1 | Operations are batching instead of flowing — usually to amortize long changeovers | CNC batches of 25 (because changeover takes 30–45 min) |
| Push arrows | Work is being pushed by schedule rather than pulled by downstream demand | MRP dispatch list drives all operations — no pull signals |
| External processing | Parts leave the facility, adding transport time and batch accumulation | Anodize adds 10 days with a batch minimum of 50 |
| Inspection as separate step | Quality is checked after the fact instead of built in (violates jidoka) | 4 days waiting for inspection that takes 8 minutes |
Future-State Map: What Could Be
The future-state map applies lean principles to redesign the value stream. You do not start from scratch — you take the current state and ask a series of questions:
| Question | Principle | Action in Our Example |
|---|---|---|
| What is the Takt time? | Match pace to demand | 46 min/part — both CNC operations are near Takt, which is good |
| Can we create flow? | Continuous flow | Connect CNC Rough → CNC Finish → Deburr into a cell with FIFO lanes (eliminate 8-day queue) |
| Where must we use pull? | Pull | Supermarket before CNC cell. Kanban signal from inspect to cell. CONWIP limit on total WIP. |
| Can we reduce batch sizes? | Reduce waste | SMED on CNC Rough (45 → 10 min changeover) enables batch of 5 instead of 25 |
| Can we bring external processing in-house? | Reduce lead time | Negotiate with anodize vendor: deliver twice/week in lots of 20 instead of once/month in lots of 50 |
| Can we move inspection to the point of production? | Jidoka | In-process CMM check at CNC Finish (8 min absorbed into cycle). Eliminate separate inspect queue. |
| Metric | Current State | Future State | Improvement |
|---|---|---|---|
| Total lead time | 47 days | 12 days | 74% reduction |
| WIP inventory | ~470 parts | ~120 parts | 74% reduction |
| Batch size (CNC) | 25 | 5 | 80% reduction |
| PCE | 0.46% | 1.8% | 4× improvement |
| Number of handoffs | 6 | 3 | 50% reduction |
PCE of 1.8% is still low in absolute terms — but it is a 4× improvement, and the 74% lead time reduction means parts that used to take 47 days now take 12. That is a competitive advantage the customer can feel in delivery performance.
⚠️ Common Mistake: The Conference Room VSM
If your value stream map was created by managers in a conference room using ERP data, it is wrong. VSM requires walking the floor, counting inventory by hand, timing operations with a stopwatch, and asking operators what actually happens (not what the SOP says). The ERP says changeover is 15 minutes; the floor says 45. The ERP says WIP is 200; the floor has 380. The map must reflect reality.
The Implementation Roadmap
The future-state map is not a wish list. It is an implementation plan. Break it into “value stream loops” — each loop is a focused improvement that can be completed in 1–3 months:
Loop 1: Pacemaker Process
Start at the pacemaker — the single process that sets the schedule for the entire value stream. Implement Takt, level the schedule, and install the pull signal. In our example: set up the machining cell with FIFO and kanban replenishment.
Loop 2: Upstream Flow
Connect upstream operations to the pacemaker. Implement SMED to reduce batch sizes. Install supermarkets where flow is not yet possible. In our example: reduce CNC changeover and connect rough→finish→deburr into a cell.
Loop 3: External Dependencies
Address external processing, supplier lead times, and shipping logistics. These often require negotiation rather than internal improvement. In our example: renegotiate anodize vendor schedule.
🎯 The Bottom Line
Value stream mapping is the diagnostic tool of lean. It reveals what no spreadsheet or ERP report can show: the complete picture of how material and information flow from door to door, and where the 95–99% of non-value-add time hides. Map current state first (by walking the floor, not reading reports), design a future state using lean principles, then implement in focused loops. The goal is not a perfect map — it is actionable insight that drives real improvement. Next: The 8 Wastes Deep Dive — the taxonomy of everything your value stream map reveals.
Stop reading, start modeling
Model your process flow, run simulations, optimize staffing with TOC math, and test your knowledge with 107 interactive checks — all in one platform.