← ArticlesValue-Stream Mapping and Future-State DesignEngineering · ManufacturingLesson 21/32← PrevNext →
GuidePublished 14 Aug 202612 min readBy Kevin JoginManufacturingOperational ExcellenceValue-Stream Mapping and Future-State DesignCurrent-state problem

Engineering · Manufacturing · Operational Excellence

Value-Stream Mapping and Future-State Design

Engineering handbook for value-stream mapping and future-state design, covering current-state problem, the shocking math nobody talks about, what exactly is a...

Executive summary

This handbook section converts the supplied engineering material into a practical, source-controlled reference. It concentrates on the following learning outcomes.

Current-state problem
The Shocking Math Nobody Talks About
What Exactly Is a Value Stream?
Four Elements Every Map Must Have
The Eight Great Sins of Waste (Muda)
"Literal" Waste — Easy to See, Easy to Cost

Current-state problem

Before the transformation, the source manufacturing plant looked like most manufacturing operations around the world. On paper, everything seemed reasonable:

  • Six process steps from stamping to shipping
  • Dedicated equipment at each station
  • An MRP system managing orders and scheduling
  • A team of experienced operators

But beneath the surface, a hidden reality was eating their margins alive.


The Shocking Math Nobody Talks About

Here's what the data revealed when an outside Lean advisor walked the floor:

Activity % of Total Labor Hours Category
Product Transformation 8% Value Adding
Paperwork 4% Value Adding
On the Job (working) 23% Value Adding
Clean Up 13% Incidental Work
Talking 10% Incidental Work
Walking 9% Pure Waste
Waiting 8% Pure Waste
Getting Tools 8% Pure Waste
Standing / Looking 6% Pure Waste
Parts Search 6% Pure Waste
Not in Area 5% Pure Waste

Only 12% of the total effort was actually adding value.

Let that sink in. Out of 100,000 direct labor hours, roughly 88,000 hours were spent on activities the customer would never pay for.

"But we're busy all the time!" — Every team member, before they learned to see.

This wasn't unique to the source manufacturing plant. This is the reality across industries and geographies. Research from the aeronautical industry, the originating manufacturer's own benchmarks, and lean studies across sectors confirm the same brutal pattern:

Company Type Non-Value-Added Value-Added
Typical Manufacturing 95% 5%
the source organisation (Japan benchmark) 50% 50%
the originating manufacturer (best in class) 57% 43%
North American Average 70–95% 5–30%

You're not slow because your people are slow. You're slow because your process is full of invisible waste.



What Exactly Is a Value Stream?

Before you can map it, you need to understand it. A Value Stream is:

All activities and processes required to design, order, produce, and deliver a product or service to a customer.

It's not just the factory floor. It's the entire flow — from the moment a customer places an order to the moment they receive the product. It includes two intertwined rivers:

  • 🔵 Material Flow — the physical movement of raw materials to finished goods
  • 🟢 Information Flow — the orders, schedules, signals, and data that direct the material flow

A Value Stream Map is simply a visual picture of both flows, drawn with commonly understood icons, annotated with real data — cycle times, changeover times, inventory counts, uptime percentages.


Four Elements Every Map Must Have

Element What It Captures
1. Materials Flow Receipt from suppliers → delivery to customers
2. Transformation People, process steps, and equipment that convert raw materials
3. Information Flow Orders, schedules, signals that direct material and transformation
4. Critical Data Volumes, times, values, and measures at each step


The Eight Great Sins of Waste (Muda)

These were first categorized by Taiichi Ohno (the originating manufacturer, 1985) and remain the universal framework for waste identification:


"Literal" Waste — Easy to See, Easy to Cost

Waste Type What It Looks Like Root Causes
Over-production Making too much, too soon, too fast Long set-ups, variable lead times, unbalanced processes
Defective Output Rework, rejects, repairs, uncertainty Uncontrolled processes, incapable processes, undefined standards
High Inventory Excess raw materials, WIP, finished goods Unbalanced operations, unreliable forecasts, unreliable suppliers
Waiting Time People or machines idle Schedule variability, rigid task assignments, poor maintenance

"Obscured" Waste — Harder to See, Harder to Cost

Waste Type What It Looks Like Root Causes
Excess Motion Unsafe movements, repetitive strain Poor workspace layout, bad equipment design, poor methods
Inappropriate Processing Idle plant, underused equipment Over-capacity, over-specified plant, schedule variability
Profligate Transport Excessive product movement Process-focused layouts, disjointed processes, centralized storage
Latent Talent Unused mental and physical abilities Poor hiring, poor training, no opportunity to voice opinions

the practitioner's team pinned these eight categories on the wall. Then they walked the floor with fresh eyes.

Within two hours, they'd identified 47 instances of waste they'd walked past every single day for years.


The Three Tests for Waste

Unsure whether something is waste? Apply these three questions:

  1. Is the product physically transformed during this step?
  2. If the customer watched this step happen, would they pay for it?
  3. If you eliminated this step, would the customer know the difference?

If the answer to all three is "no," you're looking at waste.


The "Questionable" Activities

Some activities sit in a grey zone. the practitioner's team debated these hotly:

Activity Definition Waste or Not? The Nuance
Inspection Checking if work is correct Never adds real value Unless the customer explicitly demands and pays for it
Packaging Preparing goods for transit Protective-only packaging = waste The cause of damage is value-destroying and must be eliminated
Transport Moving product within production Never adds value, but often can't be eliminated Target: add value while it moves, or reduce the movement
Management Activities with no outcome on process/product Doesn't add value if it only informs managers after the fact Unless the customer sees and perceives value in the management task


Step 1: Select the Product Family

You don't map everything at once. You pick one product family — a group of products that flows through common process steps and common equipment.

the practitioner's team built a simple matrix:

Product Spot Weld Robot Weld Flash Remove Paint Manual Assy Fixtures Assy Electronic Test
LH Steering Bracket
RH Steering Bracket
Instrument Panel Brace
Seat Rail
Bumper Brackets

The LH and RH Steering Brackets shared nearly identical routings. That was the product family.

Pro tip: Start with the "Babushka approach" — map the big picture first, then nest down into the area with the most waste, like Russian dolls.


Step 2: Draw the Current State Map

This is where the magic happens. And it happens by hand, in pencil, on butcher paper.

Why pencil? Why not software?

Reason Why It Matters
No delays You draw what you see, as you see it
You do it, you understand it Drawing forces comprehension
Focus on flow, not a computer Software becomes a distraction from observation
Fixing mistakes fine-tunes skills Erasing and redrawing builds deeper understanding

The Six Rules the practitioner's Team Followed

  1. The whole team does the entire map. No splitting up.
  2. Start at the customer end if a clear first step isn't obvious.
  3. Walk the actual pathways of both material and information flow.
  4. Do a quick walk-through first, from memory, using team consensus.
  5. Use a stopwatch to collect actual times. No standard times. Real data.
  6. Draw by hand in pencil — transfer to computer tools later for distribution.

Map Layout Geography

The map has a consistent visual structure:

┌──────────────────────────────────────────────────────────┐ │ │ │ Supplier Production Control Customer │ │ Info. ◄──────── Info. ────────► Info. │ │ │ │ │ │ │ │ │ ┌───┘ └───┐ │ │ │ ▼ ▼ ▼ ▼ │ │ │ │ Process Flow Information ───────────► │ │ │ │ ═══ Lapsed Time ─────────────────────────────► ═══ │ │ ─── Value-added Time ────────────────────────► ─── │ │ │ └──────────────────────────────────────────────────────────┘


Collecting Process Data at Each Step

At every process step, the team filled in a Data Box with real measurements:

Data Point What It Means
Cycle Time (C/T) Time to produce one unit and start the next
Person Time Time a person is occupied producing one piece
Equipment Time Time a machine is occupied producing one piece
Changeover Time (C/O) Time from last piece of one product to first good piece of next
Availability Time Total time per day the workstation is available
Uptime % Actual operating percentage after maintenance/breakdowns
Scrap Rate Percentage of defective product requiring rework or scrapping
Number of Operators People required at the workstation
WIP Work in progress inventory sitting between steps
Batch Size How many units move together between steps

What Their Current State Map Revealed

When the practitioner's team completed their current state map (based on the ACME Stamping case study they modeled after), the numbers were devastating:

Process Step Inventory (Days) Cycle Time
Raw Material (Coils) 5.0 days
Stamping 7.6 days buffer 1 second
Spot Weld #1 1.8 days buffer 39 seconds
Spot Weld #2 2.7 days buffer 46 seconds
Assembly #1 2.0 days buffer 62 seconds
Assembly #2 4.5 days buffer 40 seconds
TOTALS Production Lead Time = 23.6 days Processing Time = 188 seconds

Read those totals again.

23.6 days of lead time. 188 seconds of actual processing.

That's a value-added ratio of roughly 0.014%. The product spends 99.98% of its journey through the factory waiting.

the practitioner stood in front of that map and felt the weight of it. Every day of inventory was money. Every handoff was risk. Every buffer was a failure to flow.

But now she could see it. And so could her entire team.



The Eight Questions That Design a Future State

the practitioner's team worked through these systematically:

  1. What is our takt time? (The heartbeat of customer demand)
  2. Will we build directly to shipping or to a finished goods supermarket?
  3. Where can we use continuous flow? (Reduce batch sizes first)
  4. Where do we need pull systems? (Eliminate buffers)
  5. At what single point do we trigger production? (The "pacemaker")
  6. How do we level the production mix at the pacemaker?
  7. What increment of work will we release and take away? (Leveling volume)
  8. What process improvements are necessary? (Uptime, changeover, training)

The Three Phases of the Future State

Phase Focus Goal
Phase 1: Customer Demand Thoroughly understand what the customer actually needs Match production to real demand
Phase 2: Continuous Flow Deliver the right work, in the right time, in the right quantity Eliminate batch-and-wait between steps
Phase 3: Leveling Distribute work evenly by volume and variety Make the most effective use of available time

The Results at the source manufacturing plant

After three months of implementing their future state changes:

Metric Before (Current State) After (Future State) Improvement
Production Lead Time 23.6 days 5.0 days 79% reduction
Processing Time 188 seconds 166 seconds 12% reduction
Inventory Turns Low Dramatically higher Freed significant working capital
Defect Rate High variability Reduced through flow Fewer handoffs = fewer errors
Operator Engagement Low (told what to do) High (seeing and solving) Qualitative transformation

The real breakthrough wasn't the numbers. It was the team.

Operators who had been silently watching waste for years finally had a language to describe it, a framework to categorize it, and a process to eliminate it.

They weren't working faster. They were working on the right things.



Engineering takeaway

You don't need to run a factory to use Value Stream Mapping. Any process with a sequence of steps can be mapped:

# Business Process Value-Adding Sequence Outcome
1 Development Concept → Launch New product or service
2 Planning Idea → Action steps Less uncertainty
3 Production Raw material → Finished product A product or service
4 Marketing Awareness → Enquiry Sales enquiry
5 Sales Enquiry → Order Customer order
6 Fulfillment Order → Cash in Satisfied customer
7 Recruitment Vacancy → Appointment Enabled employee
8 Consulting Complaint → Cure Solution
9 Purchasing Requisition → Receipt Satisfied user need
10 Maintenance Out of service → Into service Extended capacity
11 Repair Diagnosis → Correction Restituted capacity

If it involves a sequence, it can be mapped. And if it can be mapped, you can find the waste.


When VSM Works Best (and When It Doesn't)

Be strategic about where you apply it:

Factor VSM Works Well VSM May Struggle
Volume High-volume production Erratic, low-volume jobbing shops
Variety Low variety, similar products Highly varied products with different methods
Equipment Dedicated equipment per family Multiple shared equipment with different routings
Routings Simple, consistent routings Complex, divergent routings
Components Few parts per product Many parts and sub-assemblies
Strategy Part of ongoing Lean thinking One-off exercise with no follow-through

Note: Many variants of VSM exist for complex situations, including Group Technology mapping and Four Fields Mapping (which adds swim lanes for sections involved, phases, tasks, and standards).



Your Quick-Start Playbook

Ready to try this? Here's exactly how to begin:


The Three Prerequisites

1. Management Commitment

  • Articulate urgency: "My job is on the line."
  • Admit vulnerability: "I don't have the answers."
  • Allocate real time: "Every Wednesday morning."

2. Team Establishment

  • Appoint a Value Stream Champion (team leader)
  • Assemble a broad-based team — all areas, all levels
  • Seek diverse perspectives and backgrounds

3. Individual Involvement

  • Train everyone on the basics before you start mapping
  • During mapping, the entire team sees the entire map
  • No taboos. Every detail is fair game.

The Balance of Focus

Here's something counterintuitive: 90% of improvement effort should be on waste elimination at the front lines. Only about 10% needs to be top-down value stream strategy.

Senior Management ───────────────────────► │ │ VALUE STREAM ELIMINATION │ IMPROVEMENT OF WASTE │ (Strategic) (Tactical) │ ▼ Front Lines ─────────────────────────────► 10% 90% ◄── Focus Ratio ──►

Value stream improvements drive waste elimination projects. But the tool must be used selectively and strategically — not as a bureaucratic exercise.



What VSM Is — and What It Isn't


What It Is

  • A "new pair of glasses" for seeing your process
  • A way to enable the whole organization to see waste simply
  • A system view that provides the customer's perspective
  • A roadmap for improvement that identifies operating culture

What It Is NOT

  • ❌ A logic diagram
  • ❌ A flow diagram
  • ❌ A data map
  • ❌ A consultant's deliverable
  • ❌ A one-time exercise

It's a living practice. The future state you design today becomes the current state you map tomorrow. Then you improve again.



The Ending the practitioner Didn't Expect

Six months after that first mapping session, the practitioner stood in front of her leadership team with a new dashboard. Lead times had dropped. Inventory was under control. On-time delivery had climbed. And her team — the same people, on the same equipment — were delivering results that would have seemed impossible before.

But the metric she was most proud of wasn't on any dashboard.

It was the operator who stopped her in the hallway and said:

"For the first time, I understand why I do what I do. And I can see what needs to change."

That's the real power of Value Stream Mapping. It doesn't make people work harder. It makes waste visible. And when waste is visible, people — smart, capable, motivated people — eliminate it.



Your Next Step

You don't need expensive software. You don't need a consultant. You need:

  • 📝 A pencil
  • 📋 A roll of butcher paper (or a whiteboard)
  • 🟩 A pack of post-it notes
  • ⏱️ A stopwatch
  • 👥 Your team

Pick one process. Walk it end to end. Draw what you see. Time every step. Count every piece of inventory. Ask "why?" five times at every bottleneck.

The waste has been there all along. You just need to learn to see it.


What process in your organization would benefit most from a Value Stream Map? Drop your answer in the comments — the more specific, the better. Let's make the invisible visible.


Engineering use and verification

Choose and control a process from the required function, material, geometry, tolerance, surface condition, volume, safety and inspection plan. Confirm the process window with representative trials, identify the variables that move quality, and connect each critical characteristic to an observable control and reaction plan. Do not convert a successful source example into a universal limit; validate capability using the actual machine, tooling, material batch and operating conditions.

  • Confirm scope, assumptions, interfaces and required outcome.
  • Use one controlled unit system and show every conversion.
  • Identify current project, customer and regulatory requirements.
  • Separate source examples from mandatory acceptance criteria.
  • Check calculations, tables and selections by an independent method.
  • Verify safety, maintainability and credible failure modes.
  • Record evidence, revisions, approvals and unresolved limitations.
  • Validate the result under representative operating conditions.

Continue learning

Gemba Observation and Work-Study PracticeGuide · ManufacturingNEXT LESSON →Leadership Waste, Risk and Operational GovernanceGuide · ManufacturingSelecting Lean, Six Sigma and Constraint-Based ImprovementGuide · ManufacturingLeading Organisational Change and Managing Resistance: The Myth That Kills Every Change InitiativeGuide · Manufacturing