New to this topic?
We recommend reading these guides first to get the most out of this one:
End-to-End
Process Visibility
2
Maps (Current + Future)
5-95%
Typical Waste in Lead Time
#1
Lean Analysis Tool

What Is a Value Stream Map?

A value stream map (VSM) is a visual representation of every step — material and information — required to deliver a product or service from start to finish. It's the single most powerful tool in lean because it reveals waste that's invisible in day-to-day operations.

💡 Why VSM Matters

Most managers know their individual process times. VSM shows what happens between processes — the waiting, the batching, the handoffs — which is usually where 90%+ of lead time hides.

How to Create a Current State Map

Walk the process (backwards)

Start at shipping and walk upstream to receiving. This follows the flow of customer value. Bring a pencil, stopwatch, and clipboard — go to the gemba (actual workplace), don't map from a conference room.

Record each process step

For each workstation: cycle time (how long one unit takes), changeover time, uptime %, batch size, number of operators, and available time per shift.

Measure the inventory between steps

Count WIP at every queue, buffer, and staging area. Convert to time: if 500 units sit between steps and the next process handles 100/hour, that's 5 hours of wait time.

Map information flow

How does each step know what to work on next? Is it a schedule push, a kanban pull, or "whoever yells loudest"? Draw information flows across the top of the map.

Calculate the timeline

Draw a timeline at the bottom: cycle time (value-adding) on the rises, wait time (non-value-adding) in the valleys. Total them up to see your value-add ratio.

Simplified Value Stream — Before Improvement
Receiving
CT: 2 min
⏳ 4h
Assembly
CT: 8 min
⏳ 6h
QC Check
CT: 3 min
⏳ 2h
Shipping
CT: 5 min

Total lead time: 12h 18min → Value-add time: 18 min → Value-add ratio: 2.4%

Reading a VSM: What to Look For

Symptom on MapWhat It MeansAction
Large inventory triangles between stepsBatching or unbalanced processesReduce batch sizes, balance line
Information flows going to every step separatelyPush scheduling — no flowImplement pull signals (kanban)
One step with much longer CT than othersBottleneck constraining the systemApply Theory of Constraints
High changeover time at one stepLong setup blocking flowSMED (Single Minute Exchange of Die)
Low uptime % at a stepEquipment reliability issueTPM (Total Productive Maintenance)
📋 Before and After Packaging Line

Current state: 14-day lead time from raw material to shipped product. Only 47 minutes of actual processing time. Value-add ratio: 0.23%.

Future state changes: Replaced batch scheduling with FIFO lanes, added supermarket pull between cutting and assembly, reduced changeover from 45min to 12min.

Result: Lead time dropped to 3.5 days. Same 47 minutes of processing, but 75% less waiting. On-time delivery went from 82% to 97%.

🗺️
SymplProcess automates your VSM The Process Flows tool in SymplProcess builds your value stream map interactively — drag to connect processes, see cycle times, WIP, and bottlenecks highlighted automatically. No pencil needed.

Build Your Own VSM

Try mapping a simple value stream. Edit the process times and wait times to see how they affect total lead time and Process Cycle Efficiency.

⚡
Try It Yourself
Mini Value Stream Map
▼
Edit process times and wait times for each step. Watch how wait time dominates lead time — and how Process Cycle Efficiency (PCE) reveals the truth about your value stream.
Receive
→
Machine
→
Inspect
→
Ship
Lead Time Breakdown
120m
15m
60m
45m
30m
Value-AddWait / Non-Value-Add
286 min
Total Lead Time
31 min
Process Time
255 min
Wait Time
10.8%
PCE
Process Cycle Efficiency: Only 10.8% of total lead time adds value. Good progress — keep reducing wait times to reach world-class (25%+).
Ready for the full knowledge check? Test your understanding with guided scenarios and data export.
PROTake the Pro Knowledge Check →

Take the workbook to the floor

The Value Stream Mapping Workbook is a single self-contained file: build the stream stage by stage, put your own times and piles in, and it works out the metrics, the biggest opportunities, area capacity against a target, shared-resource load and a modelled future state as you go. It exports your data as CSV and a summary you can paste into a report. Works offline, on a laptop in a meeting room, with nothing to install.

Free forever · Every feature included

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.

Open Workbench → Pro Knowledge Check

Take this to a room

The running order

For a team about to map a value stream. They should leave knowing to walk it backwards from shipping, to convert every pile into hours, and to expect the timeline to be mostly waiting.

7 beats · 9 min
  1. 1

    What a map is for

    Everyone already knows their own process times. A value stream map is about what happens between processes.

    • The waiting, the batching, the handoffs.
    • That gap is usually 90 per cent or more of lead time.
    • Nobody owns the space between two departments, which is exactly why it hides.

    Ask the room Who owns the queue between our two busiest steps?

  2. 2

    Walk it backwards, on foot

    Start at shipping and walk upstream. That follows the flow of customer value, and it stops you mapping what you assume.

    • Pencil, stopwatch, clipboard. Not a conference room.
    • Backwards keeps you honest about what the customer actually receives.
    • If you did not walk it, you did not map it.
  3. 3

    What to write at each step

    Six numbers per station, and none of them is an opinion.

    • Cycle time, changeover time, uptime per cent.
    • Batch size, operators, available time per shift.
    • If a number is disputed on the floor, that is a finding in itself.
  4. 4

    Turn every pile into hours

    WIP counts mean nothing to an audience. Time does.

    • Count WIP at every queue, buffer and staging area.
    • 500 units in front of a step that handles 100 an hour is 5 hours of wait.
    • Now the pile is on the same axis as the process time.

    Ask the room What is the biggest pile on our floor, in hours?

  5. 5

    Draw the information flow too

    Half the map is the question: how does each step know what to work on next?

    • A schedule push, a kanban pull, or whoever shouts loudest.
    • Information flows go across the top, material along the bottom.
    • Where the information is unclear, the material is usually late.
  6. 6

    The timeline is the punchline

    Cycle time on the rises, wait time in the valleys. Total them and the ratio does the arguing for you.

    • A real case: 14-day lead time, 47 minutes of processing. Value-add ratio 0.23 per cent.
    • Nothing about that number is unusual.
    • It is not a criticism of anyone's work rate.
  7. 7

    Then the future state

    The current map is a diagnosis. The changes come from the valleys, not the rises.

    • That case: FIFO lanes instead of batch scheduling, a supermarket between cutting and assembly, changeover 45 down to 12 minutes.
    • Result: 3.5-day lead time. Same 47 minutes of processing, 75 per cent less waiting.
    • On-time delivery 82 to 97 per cent.

    Ask the room Which stream do we map, and who walks it with us?