Value Stream Mapping
A Lean technique for visualising every step from customer request to delivered value, distinguishing value-add work from waste.
Definition
Value Stream Mapping (VSM) is a Lean technique that visualises every step in the flow of work from customer request to delivered value. Each step is annotated with cycle time, waiting time, information flows, and hand-offs. The goal is not to draw the diagram — the goal is to see, in one honest picture, how much of the elapsed time actually adds value and how much is waste. VSM originated in Toyota's production system, matured in manufacturing, and has been adopted with real effect in construction, software, and services.
What You Draw
- Each process step with cycle time (time doing work).
- Each queue between steps with wait time (time not doing work).
- Information flows (approvals, requests, hand-offs).
- People flows (who is involved at each step).
- Total lead time = sum of cycle + wait.
- Process Cycle Efficiency (PCE) = total value-add time ÷ total lead time.
Most first-time VSMs shock the team. PCE below 5% is common. That means 95% of the elapsed time from customer request to delivery was waiting for something.
Real-World Construction Example
A precast concrete supplier mapped the value stream from "customer order" to "product delivered". Total lead time: 47 working days. Sum of actual working time on the product: 3.2 days. PCE: 6.8%. The queues: design approval (14 days), engineering review (7 days), mould scheduling (6 days), material readiness (5 days), transport queue (4 days). None of the improvement work over the next year was about faster casting — it was about queue reduction. Twelve months later: lead time 22 working days, PCE 15%. Zero new machines were bought.
Real-World IT / Agile Example
A DevOps team mapped the value stream from "code committed" to "code in production". Result: 11 working days on average, of which 47 minutes was value-add build/test time. Queues: code review (2.3 days), QA scheduling (3.1 days), release train wait (4.2 days), production release window (1.4 days). Same lesson as the concrete supplier: engineering was not the bottleneck; governance was. The improvement programme addressed each queue in turn (small-batch PRs, embedded QA, trunk-based development, on-demand deploys). Nine months later: lead time under one working day, deploys many times daily.
Levels of VSM
- Current state VSM — how work flows today, warts and all.
- Future state VSM — a specific target state 6–12 months out.
- Kaizen bursts — the specific improvements between current and future.
Expert Tips
- Walk the flow. Do not draw the VSM from a meeting room; walk it end-to-end with the people who do each step.
- Use real data, not estimates. Pull actual timestamps from your systems. Team estimates are optimistic by roughly 40%.
- One value stream at a time. Trying to map five in parallel produces five superficial maps.
- Fix the biggest queue first. Not the most interesting one, not the easiest one — the biggest one.
- Publish PCE. Watching PCE improve over quarters is one of the most motivating metrics teams can adopt.
Common Mistakes
- Drawing an aspirational VSM instead of the messy real one.
- Skipping queues because "we don't have data for them" — that is exactly the point.
- Attacking value-add steps to trim minutes when queues are days.
- Not returning to the VSM after six months to check whether it still matches reality.
- Treating VSM as a workshop deliverable instead of a governance instrument.
Practical Lessons Learned
- The best VSMs I have seen were drawn on brown paper on a wall, with real timestamps written in marker. Digital VSMs look tidier but often mask the honest ugliness the technique depends on.
- Cross-functional VSMs (spanning design, procurement, construction) reveal far more improvement opportunity than departmental VSMs.
- Once a team internalises PCE, they never look at their process the same way again — the discipline outlasts the specific improvement programme.
Key Takeaways
- VSM visualises the honest flow, cycle + wait, from request to delivery.
- Most PCE numbers are shockingly low — that is the insight, not a problem with the technique.
- Queues, not process steps, are the biggest lever.
- Walk the flow, use real data, fix the biggest queue first.
Related Encyclopedia Entries
Related Research Articles, Case Studies & Tools
Frequently Asked Questions
How long does a VSM workshop take?
A first current-state VSM for a real value stream typically takes 1–3 days with the right people in the room. Anything less usually produces a superficial map; anything more usually reflects poor facilitation.Who should be in the room?
Someone from every step in the flow — including the queues between steps. Excluding a group because 'they don't really matter' guarantees you miss their queue, which is often the biggest.Is PCE the only metric that matters?
It is the most visible one, but total lead time is what the customer experiences. Improve both; do not chase PCE at the expense of extending lead time.How is VSM different from a swimlane diagram?
Swimlane diagrams show who does what; VSM shows cycle time, wait time, and information flows on top of the who. A swimlane diagram tells you the process; a VSM tells you where the waste is.Can VSM work for software?
Yes — Value Stream Mapping is core to the DevOps improvement literature. It works equally well from 'idea' to 'live in production', from 'commit' to 'live', or from 'bug reported' to 'bug closed'.Should we redo the VSM every year?
At least. Some teams do a lightweight refresh quarterly to check whether the last improvements held. Once a year is minimum for a real cross-functional value stream.What if leadership won't invest based on the VSM?
Then you have a leadership problem, not a mapping problem. A well-drawn VSM with real data is one of the most persuasive artefacts in Lean practice. If it does not move leadership, the issue is usually political trust, not evidence.What is a common misconception about Value Stream Mapping?
That the topic is well-defined across all references. In practice, definitions vary between PMBOK, PRINCE2, AACE and ISO 21500 — this entry uses the definition most aligned with field practice on capital projects, and flags where the standards diverge.Which related encyclopedia entries should I read alongside Value Stream Mapping?
Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.How does Dr. Hassan Eliwa's research treat Value Stream Mapping?
Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Value Stream Mapping is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.How is Value Stream Mapping defined on PMMilestone Research & Insights?
A Lean technique for visualising every step from customer request to delivered value, distinguishing value-add work from waste. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.
People also ask
Follow-up questions practitioners search for next — each one points to the calculator, template or reference entry that answers it.
Where is this in the glossary?
Quick-lookup definitions across 1,200+ PM terms. PM Glossary on PMMilestone.org ↗
Which learning track covers this end-to-end?
Structured tracks from beginner planner to programme controls director. Project Controls Academy ↗
Which book goes deeper than this entry?
Practitioner field handbooks with worked numerical examples. Books & Publications ↗
Which calculator on PMMilestone.org applies here?
The integrated EVM workbook covers most cost-schedule diagnostics. EVM Calculator ↗
Related Entries
More in Lean
- Letter GGemba Walk
A lean management practice of going to the actual place where work is performed — site, factory floor, or team room — to observe, ask questions, and learn directly rather than rely on reports.
- Letter JJust-in-Time Delivery
A lean logistics approach where materials, components, or work items arrive exactly when needed for the next activity, reducing inventory, waste, and double-handling.
- Letter LLast Planner System
A collaborative lean construction planning method where the people who will perform the work commit to what they can actually do, replacing top-down schedules with promises and weekly learning.
- Letter TTakt Time Planning
A lean production approach that paces work to a steady rhythm — the takt time — by sizing work zones so each crew finishes one zone in the same time, creating predictable flow.
Further reading on PMMilestone.org
Curated companion resources hosted on the flagship platform, PMMilestone.org.
- For practitioners who want to go deeper, the Learning Tracks.
- Engineers researching this topic typically continue with the Books & Publications.
- A practical companion to this entry is the EVM Calculator.
- Closely related on the flagship platform is the Schedule Health Checker.
- Useful alongside this article is the PMMilestone.org knowledge hub.