Value Stream Mapping
Value Stream Mapping is a visual technique from Toyota that draws every step in the path from customer request to delivery — including wait times, handoffs, batch sizes, and information flow. Unlike a flowchart, a VSM measures TWO numbers per step: process time (actual work) and lead time (calendar time including waits). The gap between them is waste. Most processes look fast on paper but reveal 90%+ wait time when mapped honestly. A typical software feature 'takes 2 weeks' but mapping shows 6 hours of coding inside 14 days of queue, review, and release wait — process efficiency around 5%.
The Trap
Teams draw the 'official' process from the SOP document instead of the ACTUAL process. The official process says 'PM writes spec → Engineer codes → QA tests → Deploy.' The actual process includes: spec sits in PM queue 5 days, three meetings to clarify, engineer waits for design assets, QA queue 4 days, security review 3 days, release-train wait 7 days, post-deploy hotfix loop. If you map the fantasy, you optimize the fantasy. Walk the floor (or follow a real ticket from start to finish) before drawing anything.
What to Do
Pick ONE product family or one feature type (don't try to map everything). Follow a real unit through the process. For each step record: process time (active work), lead time (wall clock), people involved, batch size, and rework rate. Draw the current state (what is). Then draw a future state (what could be) by attacking the largest waits first. Pin both maps next to each other on a wall. Set a 90-day target for the gap.
Formula
In Practice
When Mike Rother and John Shook documented Toyota's mapping practice in the 2003 book Learning to See, they showed how a stamping plant cut lead time from 23.6 days to 4.5 days — without any new equipment. The map revealed that of those 23.6 days, only 184 seconds were value-adding. The fix wasn't faster machines; it was eliminating six handoffs, shrinking batch sizes from 1,200 to 200, and replacing weekly schedules with hourly pull signals. Same equipment, same people, 80% less lead time.
Pro Tips
- 01
Always map two numbers per step: process time AND lead time. The ratio between them is where waste hides. A step with 2 hours of work and 4 days of wait is screaming for attention.
- 02
Use the 'time ladder' notation at the bottom of the map: a wave going up for wait time, down for process time. Total wait at the bottom right is your lead time. Total process time is your value-add. If wait is 20x process, your process is 95% waste.
- 03
Future-state maps should target a 50% lead time reduction in 90 days. If you can't see how to halve lead time on the page, you haven't found the real wastes yet — go back and walk the process again.
Myth vs Reality
Myth
“VSM is only useful for factories”
Reality
VSM was originally for manufacturing but is used today in software (deployment pipelines), healthcare (patient flow), insurance (claims processing), and HR (hiring funnels). The math is identical — wait time is wait time whether the unit is a car door or a job applicant.
Myth
“A good VSM should fit on one page”
Reality
Good VSMs are A0 wall-sized for a reason. Trying to fit a 30-step process on a slide forces you to abstract away the very details (batch size, queue length, rework loops) that reveal where the waste lives. Print large, draw by hand, walk the actual floor.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
You map your customer onboarding: 6 hours of actual work spread across 18 calendar days. What is your Process Cycle Efficiency?
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets — not absolutes.
Process Cycle Efficiency by Industry
Cross-industry benchmarks from Lean Enterprise Institute studiesWorld-Class Manufacturing
25-50%
Lean Service / Knowledge Work
15-25%
Typical Office Process
5-15%
Untouched Bureaucracy
< 5%
Source: https://www.lean.org/lexicon-terms/value-stream-mapping/
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Virginia Mason Hospital (Toyota-Style VSM in Healthcare)
2002-2010
Virginia Mason Medical Center in Seattle adopted Toyota Production System methods, including aggressive value stream mapping. Their first VSM target: cancer-patient intake. Original lead time from referral to first treatment: 42 days. Mapping revealed only 4 hours of actual clinical work — the rest was scheduling delays, redundant intake forms, lost lab results, and silos between departments. They redesigned around a single coordinated visit ('one-stop clinic'). Lead time dropped from 42 days to under 5 days. They mapped 175 value streams between 2002-2010, freeing thousands of square feet of unused space and dramatically improving patient outcomes.
Cancer Intake Lead Time
42 days → 5 days
Inventory Reduction
53% across system
Floor Space Freed
~25,000 sq ft
Productivity
+44% per FTE
VSM works in services and healthcare exactly as it does in factories. The 'product' is the patient journey, and wait time is just as deadly to the experience.
Hypothetical: B2B SaaS Sales Cycle
Recent
A 60-person SaaS startup mapped their enterprise sales cycle: 84 days from MQL to closed-won. Total active selling time: 18 hours. PCE = 1.1%. The biggest waits were procurement security review (28 days), legal redlines (17 days), and prospect-side IT review (12 days). Rather than hire more AEs, they built a security review microsite (with SOC 2, pen-test reports, DPA template) that prospects could share with their internal IT and legal teams pre-call. Average cycle dropped from 84 days to 51 days. Same sales headcount, 38% more deals/quarter.
Sales Cycle
84 days → 51 days
PCE
1.1% → 2.4%
Deals/Quarter
+38%
Headcount Added
Zero
VSM in revenue ops is high-leverage and underused. Most of your sales cycle is waiting for the prospect's internal process — the highest-impact moves help THEIR process, not yours.
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Value Stream Mapping into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Value Stream Mapping into a live operating decision.
Use Value Stream Mapping as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.