Value Stream Mapping Workshop Guide
What is value stream mapping?
Value stream mapping is a technique for visual representation and analysis of value streams. Unlike processes, lifecycle activities, and value chain models that describe "workflows as designed," value streams represent the actual sequence of activities that an organization follows to create value for a consumer. Value stream mapping makes these real workflows visible, measurable, and improvable.
The official ITIL v5 book describes the purpose:
- Identify and eliminate waste to maximize value for consumers and the organization
- Identify and implement improvements to the flow of work
When to use value stream mapping
| Situation | Complexity Context | VSM Appropriate? |
|---|---|---|
| Well-defined process with known bottlenecks | Ordered | Yes (optimize the known flow) |
| Cross-team handoff problems | Ordered/Complex | Yes (make handoffs visible) |
| New service design with unclear dependencies | Complex | Partially (map what you know, experiment for the rest) |
| Crisis or outage in progress | Chaotic | No (stabilize first, map after) |
| "Something feels slow but we do not know why" | Confused | Yes (mapping will reveal the context) |
Complexity consideration: In ordered contexts, the mapped process is reliable and repeatable. In complex contexts, value stream maps should be treated as living documents that emerge and evolve, not as fixed procedures.
The five steps
Step 1: Value stream identification
Purpose: Identify which value streams exist and select which one to map first.
| Item | Detail |
|---|---|
| Duration | 1-2 hours |
| Participants | Service owner, process owners, team leads from all involved teams |
| Materials | Whiteboard or digital collaboration tool |
| Output | List of identified value streams, ranked by priority |
Activities:
- List all products and services your organization delivers
- For each product/service, identify the core value streams (how value flows from demand to delivery)
- Identify enabling value streams (internal activities that support core streams, such as access provisioning, environment setup, knowledge updates)
- Prioritize: which value stream has the most pain, the most volume, or the greatest strategic importance?
Categories (from the official book):
- Core value streams: Create digital products, deliver and support digital services
- Enabling value streams: Support core streams (e.g., onboarding, provisioning, training)
Step 2: Mapping the "as-is" value stream
Purpose: Document how work actually flows today (not how it should flow).
| Item | Detail |
|---|---|
| Duration | 2-4 hours |
| Participants | People who do the actual work (not just managers) |
| Materials | Large paper/wall, sticky notes, or digital tool (Miro, Mural) |
| Output | Visual map of the current value stream with metrics |
Activities:
- Walk the flow: Follow one instance of work from trigger to completion
- Document each step: What happens? Who does it? What tools are used?
- Capture metrics for each step:
- Processing time (how long the actual work takes)
- Wait time (how long work sits idle between steps)
- Rework rate (how often work goes back to a previous step)
- Identify handoffs: Every time work moves between teams or systems
- Mark pain points: Where do delays, errors, or confusion occur?
Recording template:
| Step | Activity | Team | Tool | Processing Time | Wait Time | Rework Rate | Notes |
|---|---|---|---|---|---|---|---|
| 1 | User reports issue | User | Portal | 5 min | 0 | 0% | |
| 2 | Ticket created | Service Desk | ITSM tool | 3 min | 10 min | 5% | Manual classification |
| 3 | Assigned to team | Service Desk | ITSM tool | 2 min | 45 min | 15% | Reassignments common |
| 4 | Diagnosis | L2 Support | Remote tools | 30 min | 0 | 10% | |
| 5 | Resolution | L2 Support | Various | 45 min | 0 | 5% | |
| 6 | User confirmation | Service Desk | 2 min | 4 hours | 0% | Waiting for user | |
| 7 | Closure | Service Desk | ITSM tool | 2 min | 0 | 0% |
Total: Processing = 89 min, Waiting = 295 min. Efficiency = 89 / (89+295) = 23%
Key insight: In most IT organizations, the "as-is" efficiency ratio is between 10-30%. This means 70-90% of lead time is waiting, not working. Making this visible is the most powerful outcome of VSM.
Step 3: Analysing the value stream
Purpose: Identify waste, bottlenecks, and improvement opportunities.
| Item | Detail |
|---|---|
| Duration | 1-2 hours |
| Participants | Same as Step 2 |
| Output | Prioritized list of improvement opportunities |
Waste categories to look for:
| Waste Type | Description | Example in ITSM |
|---|---|---|
| Waiting | Work sitting idle between steps | Ticket waiting for assignment; approval queue |
| Handoffs | Work transferred between teams/people | L1 → L2 → L3 escalation |
| Rework | Work that must be repeated due to errors | Misclassified tickets; failed changes |
| Over-processing | Doing more than the consumer needs | Excessive documentation for low-risk changes |
| Motion | Unnecessary movement of information or people | Switching between multiple tools for one task |
| Defects | Errors that reach the consumer | Unresolved incidents closed without fix |
| Inventory | Work in progress that is not being actively worked on | Ticket backlog |
Analysis questions:
- Where is the longest wait time? Why?
- Where is rework highest? What causes it?
- Which handoffs could be eliminated?
- What would the value stream look like with 50% fewer handoffs?
Step 4: Mapping the "to-be" value stream
Purpose: Design the improved future state.
| Item | Detail |
|---|---|
| Duration | 2-3 hours |
| Participants | Step 2 participants plus decision-makers |
| Output | Target state map with improvement targets |
Design principles (aligned with ITIL v5 guiding principles):
| Principle | Application to VSM |
|---|---|
| Focus on value | Remove steps that do not add value for the consumer |
| Start where you are | Improve the current stream; do not design from scratch |
| Progress iteratively | Plan improvements in small increments, not a "big bang" |
| Keep it simple and practical | Eliminate unnecessary steps and approvals |
| Optimize and automate | Automate repeatable, ordered tasks; keep human judgment for complex ones |
Target metrics example:
| Metric | As-Is | To-Be Target | Improvement |
|---|---|---|---|
| Lead time (trigger to resolution) | 6.4 hours | 2 hours | 69% reduction |
| Process efficiency | 23% | 60% | 2.6x improvement |
| Handoffs | 4 | 2 | 50% reduction |
| Rework rate | 15% at Step 3 | Under 5% | Automation of classification |
Step 5: Planning and implementing improvements
Purpose: Turn the to-be map into actionable improvements.
| Item | Detail |
|---|---|
| Duration | 1-2 hours |
| Participants | Decision-makers, improvement owners |
| Output | Improvement plan with owners and timelines |
Implementation plan template:
| Improvement | Owner | Complexity | Quick Win? | Target Date | Dependencies |
|---|---|---|---|---|---|
| Auto-classify tickets using AI (Cognition capability) | Omar | Medium | No | Q3 | Training data, AI tool |
| Eliminate L1→L2 handoff via swarming | Alex | Low | Yes | Q2 | Team training |
| Add self-service KB for top 10 issues | Anna | Low | Yes | Q2 | Knowledge articles |
| Automate closure confirmation | Omar | Low | Yes | Q2 | ITSM workflow config |
Quick wins first: The ITIL Transformation Model emphasizes identifying quick wins to build momentum. Start with low-complexity, high-impact improvements that can be delivered in weeks, not months.
ICR example: value stream mapping at ITIL Car Rental
From the official ITIL v5 book, Maria (Business Analyst) describes their experience:
"We have well-defined processes in every part of the company, which are followed by most teams at most times. However, in the last few months, we have had coordination issues between the booking service and fleet management teams."
Anna (Product Manager) adds: "We identified bottlenecks, some related to digital products, some to work processes, and managed to significantly improve the workflow. More importantly, value stream mapping helped us understand how our teams interact and where value gets stuck."
Key takeaway from ICR: Value stream mapping is not just about process efficiency. It reveals relationship and coordination problems between teams that are invisible in process documentation.
Adapting VSM for complexity
| Context | VSM Approach |
|---|---|
| Ordered | Map detailed processes; optimize systematically; automate where possible |
| Complex | Map broad flow; accept that details will emerge; use probes and experiments |
| Chaotic | Do not attempt VSM during crisis; map after stabilization |
| Confused | Start with a rough map to reveal which context you are actually in |
Related pages
- Value Stream Mapping (theory and concepts)
- Continual Improvement (improvement model)
- Templates (practical tools)
- Complexity-Based Decisions (four contexts)
- Practices-Value Chain Mapping (Appendix B)