Lean teams use VSM to see the whole system before fixing parts of it. It separates value-added time from waiting and points improvement at the biggest delays.
Where it comes from
VSM grew out of the material and information flow diagrams used in the Toyota Production System. Mike Rother and John Shook's workbook "Learning to See" codified the method for wider use.
At a glance
A current-state value stream map
Swipe sideways to see the whole diagram.
How to apply Value Stream Mapping
- 1
Choose a product family
Pick a group of products or services that share most process steps. Map one value stream at a time.
- 2
Walk the current state
Follow the work from customer back to supplier at the gemba. Record each process step, inventory point and handoff.
- 3
Collect data per step
Capture cycle time, changeover time, uptime, batch size and people. Note wait times and queues between steps.
- 4
Draw the information flow
Show how orders, schedules and signals reach each step. Mark where work is pushed rather than pulled.
- 5
Build the timeline
Add a ladder of value-added time against total lead time. The gap shows how much of the flow is waiting.
- 6
Design the future state
Use takt time, continuous flow, supermarkets and leveling to sketch a better stream. Turn the gaps into a dated improvement plan.
Worked example (illustrative)
A team maps how a custom order moves from cutting to shipment. The timeline shows 155 seconds of actual work inside 10 days of lead time, a flow efficiency of about 0.02%. Most of the wait is orders queuing for approval and parts waiting for full batches. The future state adds a daily approval slot and smaller batches, with a target lead time of 4 days.
Common mistakes
- Mapping from a conference room instead of walking the actual process.
- Drawing a beautiful current state and never building or executing a future-state plan.
- Mapping too broad a scope, so the map has no clear product family or owner.
When Value Stream Mapping is not the right tool
A value stream map suits one product family with a repeating flow. In very high-mix, low-volume work, start with the most common path or group similar jobs.
It is a planning tool, not an improvement in itself. A map that does not lead to a future state and an action plan has little value.
What a value stream map shows
A value stream map is a one-page picture of how a product or service moves from request to delivery. It shows each process step, the inventory or queue between steps, and the information flow that tells each step what to do.
Under the steps runs a timeline. Its top line adds up waiting time and its bottom line adds up processing time, so the map shows how much of the total lead time is work and how much is waiting.
Value stream mapping template
A basic template has four bands. The top band holds the customer and the supplier, with the planning or control function between them. The middle band holds the process boxes with data boxes underneath. The bottom band holds the timeline.
Each data box usually records cycle time, changeover time, uptime, the number of operators and the batch size. Teams draw the first version by hand with a pencil, then redraw it in a value stream mapping software tool if they want to share or update it.
How to create a value stream map
Pick one product family and walk the process from the shipping end back to the receiving end, so each step is seen from its customer's point of view. Record the data at each step while you are there rather than from reports.
Draw the current state first. Then mark the waste you saw, set a target, and draw a future state that shows flow, pull and fewer handoffs. The gap between the two maps becomes the improvement plan.
Common symbols
Process boxes show each step, with a data box for cycle time, changeover and uptime. Triangles mark inventory. Push arrows, supermarkets and kanban symbols show how material moves.
A timeline along the bottom compares lead time with value-added time. The ratio shows how much of the lead time is spent waiting. In the illustrative example above, 155 seconds of work in 10 days (about 4,320 minutes on a 7.2-hour working day) is a flow efficiency of about 0.06% of working time, or 0.02% of calendar time. The flow efficiency calculator works this out step by step.
Designing the future state
Learning to See, by Mike Rother and John Shook, guides the future state with a set of questions. They cover takt time, where flow is possible, where to use supermarkets and where to schedule.
Each change becomes a kaizen burst on the map, with an owner and a date. Value stream mapping software is covered in the VSM software category.
What to measure on a value stream map
Separate elapsed time, active work, quality and output. One speed figure cannot tell whether work flows well or keeps looping back. Pick the few measures the problem statement needs and write down how each is calculated:
| Measure | What to record | What it means |
|---|---|---|
| Lead time | Time between the defined start and finish events | The full span the customer experiences |
| Processing time | Time spent doing the work at a step | The effort inside a step, without the waiting |
| Waiting time | Time an item waits for capacity, information or approval | The delay to study first |
| Work in progress | Items started but not finished | Where unfinished work piles up |
| Quality | Clearly defined accept or return results | Whether faster flow still meets the requirement |
| Throughput | Finished items per period | Real output inside the boundary |
Lead time
Time between the defined start and finish events
What it means: The full span the customer experiences
Processing time
Time spent doing the work at a step
What it means: The effort inside a step, without the waiting
Waiting time
Time an item waits for capacity, information or approval
What it means: The delay to study first
Work in progress
Items started but not finished
What it means: Where unfinished work piles up
Quality
Clearly defined accept or return results
What it means: Whether faster flow still meets the requirement
Throughput
Finished items per period
What it means: Real output inside the boundary
Mark each number as observed, estimated or target, with its date and source, so a planning guess never quietly becomes the baseline. Define "finished" in work terms: an inspection can be done before its release reaches shipping, and those are two events. Value-added time explains how to sort the timeline into value-added, needed and avoidable time.
Mapping a quality inspection process
Inspection is a common place for orders to stall. Scope the map around a release outcome: start when a batch is complete with its inspection information, and finish when the disposition reaches the next approved process. Record these points:
Readiness
Product ID, required records and inspection instructions are available.
Queue entry
The batch joins the inspection load under a defined priority rule.
Inspection
The assigned check is done and recorded.
Disposition
An approved decision sets the next allowed action.
Exceptions
Nonconforming work follows the right review or correction route.
Release communication
The next process gets what it needs to move the batch.
Take the real sequence, roles and controls from the process you study. Keep unclear requirements on a follow-up list rather than drawing a tidy flow that does not exist.
An inspection value stream in numbers
Illustrative teaching data for one batch with no rework, all in elapsed minutes:
Readiness review waits 90 min, works 10 min
Inspection longest waitwaits 180 min, works 35 min
Disposition review waits 120 min, works 10 min
Release communication waits 60 min, works 5 min
The batch spends 510 minutes in scope with 60 minutes of active work, an active share of about 11.8%. That is a processing-time ratio, not automatically a value-added share.
A new tool that cuts inspection by five minutes may help, but the map points at the 180-minute wait before inspection and the 120 minutes before a decision. Match the test to the evidence: a readiness checklist if missing records block entry, a visible priority rule if batches are picked unevenly, decision cover if inspected work waits for approval. A checklist will not fix too little inspection capacity. Never treat a non-value-added label as a reason to remove an inspection; changes to controls need the quality owner's review.
Mapping software and knowledge work
The same end-to-end view works when the item moving through the stream is information or a code change. A starting route might be request, clarify, prioritize, develop, review, test, release and feedback. Trace real completed work to see where your route differs. Look for:
Thin requests
Work that enters development without enough information to proceed.
Finished but waiting
Completed changes queued for review, testing or release coordination.
Rework loops
Work sent back because expectations were read differently.
Unowned dependencies
Links to other teams with no clear owner or response rule.
Late feedback
Responses that arrive too late to shape the original work.
Pay attention to the gap between a team finishing its task and the customer using the change. Pair delivery time with a quality or customer measure, so faster movement is not mistaken for value. Value stream management software measures this flow continuously.
Who owns the value stream
A map shows the system; someone has to keep improving it. A value stream manager is responsible for results across functional lines, often without controlling all the people or budgets involved, so the role runs on coordination and influence. Record who keeps the map, who owns each improvement and who settles competing priorities. An improvement register keeps each change testable:
- Problem: The observed condition and its customer effect.
- Hypothesis: Why the proposed change should help.
- Owner: Who coordinates delivery.
- Test scope: The family, team or workload in the trial.
- Success measure: The expected result and how it will be measured.
- Guardrail: A quality or service result that must not drop.
- Review point: When the evidence will be examined and a decision made.
Keep implementation separate from evidence: "checklist introduced" shows a change happened, not that readiness improved. Update the current-state map when conditions change, and treat lasting results as something to verify after a good pilot.
Guides on this topic
- Lead time: how to define it, calculate it and shorten itLead time explained: where the clock starts and stops, the common types, how to calculate it, ARO quotes, reorder points, the metrics worth tracking and how to shorten it without cutting quality.Read the guide
- Value stream mapping symbols: the standard VSM icon setValue stream mapping symbols explained: what each VSM icon shows, when to draw it, how to read the timeline, and tips for mapping by hand or in software.Read the guide
- Lean software development: principles, wastes and flowLean software development explained: the seven principles, the seven wastes of software, flow metrics, value stream mapping, and how lean differs from agile.Read the guide
- How to do value stream mapping, step by stepHow to do value stream mapping step by step: walk the process, record data, draw the current state by hand, design the future state, then add software.Read the guide
Sources
Books and papers show their publication year. Web pages show the month we last checked them.
- 1.Mike Rother and John Shook, Learning to See: Value Stream Mapping to Add Value and Eliminate Muda (Lean Enterprise Institute, 1998)
- 2.James P. Womack and Daniel T. Jones, Lean Thinking: Banish Waste and Create Wealth in Your Corporation (Simon & Schuster, 1996)
- 3.Karen Martin and Mike Osterling, Value Stream Mapping: How to Visualize Work and Align Leadership for Organizational Transformation (McGraw-Hill, 2013)