Value Stream Mapping: Guide, Practical Example & Template for Service Processes

Value stream mapping (VSM) is a Lean method for visualizing every step a product or service goes through from customer request to delivery — including the waiting, queuing, and transfer times that create no value. The goal: make the entire flow visible, identify waste, and design an improved future state. The method was codified by Mike Rother and John Shook in 1999 in Learning to See, but is rooted in the material and information flow diagrams used in the Toyota Production System since the 1950s [1][2].

What distinguishes value stream mapping from a simple process flowchart: it captures not just what happens but how long each step takes, how long the work item waits between steps, and how much of that time actually creates value for the customer. This separation of value-adding and non-value-adding time is the core of the method — and the reason it often delivers shocking results for service processes: in many service workflows, less than 5% of lead time is actually value-adding [3].

Search for “value stream mapping” and you will find results dominated by manufacturing examples: automotive production, assembly lines, warehouse management. Few demonstrate the method in a service process. None systematically compares value stream mapping with the service blueprint — even though both methods visualize service processes, but from entirely different perspectives. And none honestly names the method’s limitations in knowledge-intensive services.

This guide closes those gaps.

From Taiichi Ohno to Learning to See: Where the method comes from

Value stream mapping has its roots in the Toyota Production System (TPS), which Taiichi Ohno (1912–1990) developed at Toyota from the 1950s onward. Ohno identified seven types of waste (muda) and developed tools to make material and information flow visible [2]. For Ohno, visualizing the value stream was never an end in itself — it was the first step toward eliminating waste.

Mike Rother and John Shook codified the Toyota method for a broader audience in 1999 with Learning to See: Value Stream Mapping to Add Value and Eliminate MUDA [1]. Their contribution was standardization: they defined a uniform symbol set, a clear process (current state → future state → implementation plan), and the timeline at the bottom of the map that separates value-adding from non-value-adding time. Learning to See became the best-selling Lean book and established value stream mapping as the standard tool in the Lean world.

James Womack and Daniel Jones had already defined the value stream as one of the five Lean principles in Lean Thinking (1996): define value → identify the value stream → create flow → establish pull → pursue perfection [4]. Rother and Shook delivered the operational tool for the second principle three years later.

From the shop floor to services: The transfer

The transfer of value stream mapping to services began in the 2000s. Beau Keyte and Drew Locher published The Complete Lean Enterprise in 2004, explicitly extending value stream mapping to administrative and service processes [5]. Their central insight: in service processes, the “material” flow is often an information flow — an application, a claim, a credit request — and waste manifests not in physical inventory but in digital queues, redundant data entry, and approval loops.

The 8 types of waste in services

Ohno originally defined seven types of waste for manufacturing. In service applications, an eighth is commonly added — unused talent [6]. Translating to services requires a shift in thinking: “inventory” in service is not a physical warehouse but an inbox full of unprocessed cases.

Waste type	Manufacturing	Service equivalent	Example (insurance)
Overproduction	Producing more than demanded	Generating more information than needed	Creating reports nobody reads
Waiting	Machine idle	Case sits in queue	Claims file waits 3 days for adjuster assignment
Transport	Moving materials between stations	Passing information between departments	Claims file forwarded via email to 4 departments
Over-processing	Higher quality than required	More process steps than necessary	Triple review of a standard claim under EUR 500
Inventory	Buffer stock, raw materials	Unprocessed cases, open tickets	200 open claims files in the digital inbox
Motion	Unnecessary personnel movement	System switching, searching for information	Adjuster copies data from System A into System B
Defects	Scrap, rework	Corrections, callbacks, re-entries	18% of claims require callbacks due to missing data
Unused talent	Workers below their skill level	Experts performing routine tasks	Senior adjuster reviews trivial amendment requests

The key insight for service processes: The largest waste in service processes is almost always waiting. While physical inventory is visible in manufacturing, the digital queue remains invisible — until value stream mapping exposes it. In many insurance claims processes, pure processing time is under 60 minutes — but lead time is 10–15 business days. The remaining time is spent in queues.

When is value stream mapping the right tool?

Value stream mapping is most valuable when you want to understand and optimize an end-to-end process — not individual activities, but the entire flow from customer request to service delivery.

Use value stream mapping when:

• You want to significantly reduce lead time of a service process
• You want to know where in the process time is lost (not just that time is being lost)
• You want to apply Lean principles to a service process
• You want to make cross-departmental waste visible — waiting times created by handoffs between teams
• You want to design a future state, not just document the current state

Use a different tool when:

Situation	Better alternative	Why
You want to visualize the customer perspective on the service	Service blueprint	Service blueprint works from the customer experience; VSM works from the internal process flow
You want to analyze root causes of a specific problem	Ishikawa diagram	Ishikawa analyzes causes; VSM analyzes flows
You want to iteratively improve a process	PDCA cycle	PDCA improves incrementally; VSM delivers the analysis for the future state
You want to observe the process on-site before mapping it	Gemba walk	Gemba walk provides observational data; VSM structures it
You want to prioritize customer needs	Kano model	Kano classifies features by customer impact; VSM optimizes process flow

Comparison: Value stream mapping vs. service blueprint

Both methods visualize service processes — but from entirely different perspectives:

Dimension	Value stream mapping (VSM)	Service blueprint
Perspective	Internal process flow (efficiency)	Customer experience (effectiveness)
Focus	Lead time, waste, flow efficiency	Touchpoints, line of visibility, customer experience
Central measure	Process efficiency (value-adding vs. non-value-adding time)	Customer satisfaction, moments of truth
Time dimension	Explicit — timeline with processing and waiting times	Implicit — sequence, but rarely quantified
Origin	Lean Manufacturing (Toyota, Rother & Shook 1999)	Service Marketing (Shostack 1984, Bitner et al. 2008)
Best for	”How can we make this process faster and leaner?"	"How does the customer experience this service — and where does it fail?”
Weakness	Customer perspective underrepresented	No quantitative time analysis

Our recommendation: Use both methods as complements. Start with the service blueprint to understand where the customer experiences problems. Then use value stream mapping to optimize the internal processes behind the identified problem areas. The sequence matters: first do the right things (service blueprint), then do things right (value stream mapping).

Step by step: Value stream mapping for service processes

Time frame: 1–2 days for current-state capture (including data collection), 1 day for future-state design. 2–3 days total as a team.

Step 1: Define the value stream scope

Define which process you are mapping — from the trigger (customer event) to the endpoint (service delivered).

Typical scopes for service processes:

Industry	Start point	End point
Insurance	Claim is filed	Claim payment reaches the customer
Telecommunications	Customer orders a connection	Connection is active and tested
Banking	Credit application submitted	Approval or rejection communicated
IT services	Support ticket opened	Problem resolved and ticket closed

Common mistake: Choosing too broad a scope. “From first contact to contract end” is not a value stream you can meaningfully map on a single chart. Limit the scope to a completed process with a clear trigger and a clear outcome.

Step 2: Map the current state

Walk the process physically or digitally — do not reconstruct it at a desk. Rother and Shook recommend: “Walk the flow” — trace the value stream backwards from end to start, so you are not distracted by the usual narrative logic [1]. A Gemba walk is the ideal preparation.

For each process step, document:

Data point	Meaning	Example
Processing time (PT)	Pure work time that adds value	15 min. to create a claims file
Lead time (LT)	Total time from step entry to step exit	2 days (because the case sits 1.75 days in queue)
Number of people involved	How many persons/roles are involved?	1 adjuster
Error rate/return rate	How often must the step be repeated?	18% callbacks
Information system	Which IT systems are used?	SAP, Outlook, Excel
Inventory/queue	How many cases are waiting for this step?	47 open files

The timeline: At the bottom of the map, draw the timeline — a zigzag line showing, for each step, the processing time (below, value-adding) and the waiting time (above, non-value-adding). The sum of processing times yields the value-adding time. The sum of all times yields the lead time.

Process efficiency = Sum of processing times / Total lead time x 100%

Process efficiency below 10% is not unusual for service processes — and this insight is precisely what makes value stream mapping so valuable.

Step 3: Identify waste

Mark all waste locations on the current-state map with the Kaizen burst symbol (jagged line). Use the 8 types of waste as a checklist.

Typical waste patterns in service processes:

• Queues between departments: The case waits for the next department because batch processing occurs (e.g., “All cases are handed over once daily”)
• Redundant data entry: The same information is manually entered into multiple systems
• Approval loops: Standard cases require approvals that add no value
• Media breaks: Information changes medium (paper → email → system), each switch creating error risk and waiting time
• Callbacks: Incomplete inputs from earlier steps generate callbacks in later steps

Step 4: Design the future state

The future state is not a wish list but an achievable next condition. Rother and Shook recommend planning the future state within a 3–6 month horizon — not as a vision but as a concrete next step [1].

Lean design principles for the future state:

1. Create flow: Eliminate batch processing. A case should flow from step to step, not sit in queues.
2. Pull instead of push: The next step “pulls” the case when it has capacity — instead of the previous step “pushing” whenever it finishes.
3. Eliminate waste: Define a concrete countermeasure for each identified waste location.
4. Define the pacemaker process: Identify the process step that sets the pace for the entire value stream — and optimize there first.
5. Consider takt time: How many cases must the process handle per day to meet customer demand?

Step 5: Create an implementation plan

The transition from current to future state does not happen all at once but in loops — each loop improves one section of the value stream. For each loop, define:

• What will be changed?
• Who is responsible?
• By when?
• How will success be measured?

Use the PDCA cycle to implement each individual loop.

Example: Value stream mapping for an insurance claims process

Context: An insurer discovers that the average lead time for motor vehicle claims is 14 business days — the SLA target is 7 days. A cross-functional team from claims processing, IT, and customer service conducts a value stream analysis.

Current state

Step	Processing time	Waiting time	People	System	Issues
1. Claim received	5 min.	0	Customer	Online form	18% incomplete submissions
2. Acknowledgment	2 min.	4 hrs.	Automatic	CRM	Batch send every 4 hours
3. Adjuster assignment	3 min.	2.5 days	Team lead	CRM	Manual assignment, team lead reviews once daily
4. Completeness check	10 min.	1 day	Adjuster	CRM + archive	18% callbacks by phone
5. Waiting for customer response	—	3.5 days	Customer	Phone/email	Customer unreachable, multiple attempts
6. Claim assessment	25 min.	1 day	Adjuster	CRM + Excel	External assessors available only 2x/week
7. Approval	5 min.	2 days	Team lead	CRM	Approval threshold EUR 500 — even standard cases require approval
8. Payment	3 min.	1.5 days	Accounting	SAP	Batch run once daily

Timeline:

• Total lead time: 14 business days (112 hours)
• Total processing time: 53 minutes
• Process efficiency: 53 min. / 6,720 min. = 0.8%

The figure is startling but typical: less than 1% of lead time creates value for the customer. 99.2% of the time, the case is waiting.

Future state

Improvement	Measure	Expected effect
Instant acknowledgment	Real-time auto-send instead of batch	-4 hrs. waiting time
Automatic assignment	Rule-based CRM assignment by claim type and workload	-2.5 days waiting time
Required fields + photo upload	Online form with validation and document upload	Callback rate from 18% to below 5%
Self-service status portal	Customer sees status online, receives push updates	Offloads customer service, reduces phone callbacks
Raise approval threshold	Standard claims under EUR 2,000 without team lead approval	-2 days waiting time for 70% of cases
Twice-daily payment run	2x daily instead of 1x daily	-0.75 days waiting time

Expected results:

• Lead time: 14 days → 5 days (target: SLA 7 days with buffer)
• Process efficiency: 0.8% → approx. 2.2%
• Callback rate: 18% → below 5%

Note: This example is illustratively constructed to demonstrate the method in a service context. The figures are based on typical industry values.

Value stream mapping symbols for service processes

The standard VSM symbols originate from manufacturing. Several adaptations are useful for service processes:

Symbol	Meaning (manufacturing)	Meaning (service)
Process box	Manufacturing step	Processing step (e.g., “Review application”)
Triangle	Inventory	Queue (e.g., “47 open cases”)
Curved arrow	Push material	Push information (e.g., “Email forwarding”)
Striped arrow	Pull material	Pull information (e.g., “Database retrieval”)
Burst	Kaizen burst	Improvement opportunity
Timeline	Processing time / waiting time	Processing time / waiting time
Data symbol	—	IT system (e.g., CRM, SAP, Excel)
Person	Operator	Role (e.g., adjuster, team lead)

Recommendation: Use the standard symbols as a starting point, but extend them with service-specific elements — especially IT systems and media breaks. A value stream map for service processes that omits the involved IT systems is incomplete, because system switches are a major source of waste.

Template: Value stream mapping checklist

Preparation (1–2 days before the workshop)

• Value stream scope defined (start and end point)
• Team assembled (4–8 people, cross-functional, process participants)
• Baseline data collected (lead times, processing times, queues, error rates)
• Materials prepared (brown paper or whiteboard, Post-its, markers, symbol templates)
• Gemba walk completed — process observed on-site, not just discussed

Current state (Day 1)

• Each process step documented with data card (PT, LT, people, system, error rate)
• Information flows drawn (who sends what to whom?)
• Queues/inventory captured at every handoff point
• Timeline drawn at bottom (PT below, waiting time above)
• Process efficiency calculated

Analysis

• Waste locations marked with Kaizen burst
• 8 types of waste checked as a list
• Top 3 waste sources prioritized

Future state (Day 2)

• Lean design principles applied (flow, pull, waste elimination)
• Concrete measures defined per waste source
• Expected improvement quantified
• Pacemaker process identified

Implementation

• Improvement loops defined (which section first?)
• Owners and deadlines assigned
• PDCA cycles planned for each loop
• Review meeting scheduled in 4–6 weeks

4 common mistakes in value stream mapping

1. Mapping at the desk instead of observing on-site

Symptom: The team draws the value stream map in a conference room, based on memory and process documentation — without observing the actual process.

Why this hurts: The documented process description almost always diverges from reality. Workarounds, informal communication channels, and undocumented queues remain invisible. Ohno insisted on observing the actual process — “Go see, ask why, show respect” [2].

Solution: Conduct a Gemba walk before mapping. Observe the process from end to start. Ask the people who execute the process daily — not their managers.

2. Only mapping the current state and stopping

Symptom: The team invests two days in a detailed current-state map — and hangs it on the wall. There is no future state, no implementation plan, no improvement.

Why this hurts: The current-state map is not a deliverable but an intermediate step. Without a future state, the value stream analysis is an elaborate inventory with no action plan. Rother and Shook emphasize: “The current state map is only useful if you use it to create a future state map” [1].

Solution: Schedule the future-state design as a fixed part of the workshop — ideally on the same day or the following day. Never create a current-state map without a concrete plan for the future state.

3. Too much detail in the first pass

Symptom: The team tries to capture every sub-process, every exception, and every special case in the map. After one day, the map is 3 meters long and unreadable.

Why this hurts: Details obscure the overall flow. The strength of value stream mapping lies in its end-to-end perspective — if you decompose every step into 10 sub-steps, you lose that perspective.

Solution: In the first pass, map only the 5–15 main steps. If you want to drill into a specific area, create a separate detail map for that section.

4. Confusing waste with work people dislike

Symptom: “Documentation is waste” — “Compliance checks are waste” — “Customer communication is waste.”

Why this hurts: Not every unpopular activity is waste. Documentation required by regulation (e.g., MaRisk, BaFin, SOX) is not waste — it is mandatory. Customer communication is value-adding by definition. Waste is only that which creates no value for the customer or the organization and is not legally or regulatorily required.

Solution: Test each activity with the triple question: (1) Does it create value for the customer? (2) Is it required by regulation or law? (3) Is it technically necessary for the process to flow? Only if all three answers are “no” is it genuine waste.

When value stream mapping does NOT work

1. Knowledge-intensive services with high variance: Value stream mapping assumes the process has recurring, standardizable steps. In consulting projects, research, or creative work, each instance varies significantly — there is no “standard value stream.” Here, agile methods or Kanban systems are better suited.

2. Processes without measurable lead times: If you cannot collect time data — because there is no ticketing system, no timestamps, and no process logging — then value stream mapping lacks its most important input. Invest first in process measurement.

3. Politically blocked processes: If the identified waste lies in approval loops demanded by senior management, and management is not willing to change them, value stream mapping becomes an exercise in frustration.

4. One-off processes: Value stream mapping pays off for recurring high-volume processes. Mapping a one-time project process creates effort with no return.

Variations and advanced techniques

Value stream design (Future state mapping)

Value stream design is the second part of the method — designing the improved state. While current-state capture is descriptive, value stream design is prescriptive: it defines how the process should look. Rother and Shook recommend working through eight design questions systematically [1]:

1. What is the takt time?
2. Does the process build to a finished-goods supermarket or to order?
3. Where can continuous flow be created?
4. Where are supermarkets (controlled buffers) needed?
5. Which process step is the pacemaker?
6. How is production leveled?
7. What work increment is released at the pacemaker?
8. What process improvements are needed?

Digital value stream mapping

Modern service value streams can increasingly be reconstructed from system data — process mining based on event logs from CRM, ERP, and ticketing systems. Tools like Celonis, Signavio, or Minit analyze actual process flows from the data and automatically identify deviations from the target. This digital variant complements traditional value stream mapping but does not replace the human eye for context and causes.

Frequently asked questions

What is value stream mapping?

Value stream mapping (VSM) is a Lean method for visualizing every step in a process — from customer request to service delivery. It reveals which steps create value for the customer and which are merely waiting time, rework, or other forms of waste. The goal is to design an improved future state with shorter lead time and higher process efficiency.

How do you conduct a value stream analysis?

In five steps: (1) Define scope — establish the start and end points of the value stream. (2) Map the current state — document each step with processing time, waiting time, people, and systems. (3) Identify waste — use the 8 types of waste as a checklist. (4) Design the future state — apply Lean design principles. (5) Create an implementation plan — define improvement loops with owners and deadlines.

What is the difference between value stream mapping and a service blueprint?

Value stream mapping views the process from an efficiency perspective: Where is time lost? Where does waste occur? The service blueprint views the process from the customer perspective: What does the customer experience? Where does service quality break down? Both methods complement each other: service blueprint for the question “What should we improve?”, value stream mapping for the question “How can we make it faster and leaner?”

What is process efficiency?

Process efficiency = value-adding processing time / total lead time x 100%. It shows how much of the total time actually creates value for the customer. In service processes, process efficiency is often below 5% — the overwhelming majority of lead time consists of waiting.

What types of waste exist in services?

Eight types: overproduction (more information than needed), waiting (cases in queues), transport (information handoffs between departments), over-processing (more review steps than necessary), inventory (unprocessed cases), motion (system switching, information search), defects (corrections, callbacks), and unused talent (experts performing routine tasks).

How long does a value stream analysis take?

For a clearly scoped service process: 2–3 days as a team. 1–2 days for the current state (including data collection and Gemba walk), 1 day for the future state and implementation plan. The actual implementation of improvements typically spans 3–6 months across multiple PDCA cycles.

Related methods

A typical sequence in service optimization: With the Gemba walk, you observe the process on-site. With value stream mapping, you chart the flow and identify waste. With the service blueprint, you add the customer perspective. With the PDCA cycle, you implement the improvements.

• Service blueprint: When you want to visualize the customer perspective on the service — complementary to the internal flow perspective of value stream mapping
• Gemba walk: As preparation for value stream mapping — observe the process before you map it
• PDCA cycle: For implementing the improvement measures that result from the value stream analysis
• Service design methods overview: For the overall context of service methods
• Service design: When you want to develop a new service, not optimize an existing one

---

Research methodology

This article synthesizes insights from Rother and Shook’s foundational work Learning to See (1999), Ohno’s Toyota Production System (1988), Womack and Jones’ Lean Thinking (1996), Keyte and Locher’s extension to service and office processes (2004), and the analysis of 8 German-language specialist publications on value stream mapping. Sources were selected for methodological rigor, practical relevance, and currency.

Limitations: Academic literature on value stream mapping originates predominantly from manufacturing. Empirical studies on application in knowledge-intensive service processes are limited. The practical example (insurance claims process) is illustratively constructed, not a documented case study.

Disclosure

SI Labs provides consulting services in the field of service innovation. In the Integrated Service Development Process (iSEP), we use value stream mapping in the analysis phase to examine existing service processes before developing improved service concepts. This practical experience informs the classification of the method in this article. Readers should be aware of the potential perspective bias.

References

[1] Rother, Mike, and John Shook. Learning to See: Value Stream Mapping to Add Value and Eliminate MUDA. Cambridge, MA: Lean Enterprise Institute, 1999. ISBN: 978-0966784305 [Foundational work | Value Stream Mapping | Citations: 5,000+ | Quality: 92/100]

[2] Ohno, Taiichi. Toyota Production System: Beyond Large-Scale Production. Portland: Productivity Press, 1988. ISBN: 978-0915299140 [Foundational work | TPS | Citations: 10,000+ | Quality: 95/100]

[3] George, Michael L. Lean Six Sigma for Service: How to Use Lean Speed and Six Sigma Quality to Improve Services and Transactions. New York: McGraw-Hill, 2003. ISBN: 978-0071418218 [Practitioner guide | Lean Service | Citations: 1,500+ | Quality: 78/100]

[4] Womack, James P., and Daniel T. Jones. Lean Thinking: Banish Waste and Create Wealth in Your Corporation. New York: Simon & Schuster, 1996. Revised edition 2003. ISBN: 978-0743249270 [Foundational work | Lean Thinking | Citations: 15,000+ | Quality: 90/100]

[5] Keyte, Beau, and Drew Locher. The Complete Lean Enterprise: Value Stream Mapping for Administrative and Office Processes. New York: Productivity Press, 2004. ISBN: 978-1563272462 [Practitioner guide | Lean Office | Citations: 500+ | Quality: 80/100]

[6] Liker, Jeffrey K. The Toyota Way: 14 Management Principles from the World’s Greatest Manufacturer. New York: McGraw-Hill, 2004. ISBN: 978-0071392310 [Practitioner guide | Toyota Management | Citations: 8,000+ | Quality: 85/100]

[7] Seddon, John. Freedom from Command & Control: Rethinking Management for Lean Service. New York: Productivity Press, 2005. ISBN: 978-1563273278 [Practitioner guide | Lean Service | Citations: 300+ | Quality: 72/100]

[8] Bonaccorsi, Andrea, Gionata Carmignani, and Francesco Zammori. “Service Value Stream Management (SVSM): Developing Lean Thinking in the Service Industry.” Journal of Service Science and Management 4, no. 4 (2011): 428-439. DOI: 10.4236/jssm.2011.44048 [Journal article | Service VSM | Citations: 150+ | Quality: 70/100]