Planning and Building a Service Value Stream
What the exam asks
This domain tests whether you can build and improve a service value stream, not just describe one. Expect questions on the mapping steps, on the different value streams an organization needs, and on where ITIL practices are invoked inside them.
Core rules
- A value stream is the specific sequence of steps, handoffs, decisions and wait states an organization uses to turn a demand into value. The service value chain is the generic six-activity model (plan, improve, engage, design and transition, obtain and build, deliver and support); value streams are its concrete instances.
- Value stream mapping: (1) understand the demand and trigger, (2) map the current state including handoffs and queues, (3) analyze for waste, delay and bottlenecks, (4) design and validate the future state, then iterate.
- Build at least three streams: a new service (concept to live), a restoration stream (incident to resolution) and a request stream.
- Map from the customer's perspective; the customer journey and demand entry points matter more than the internal org chart.
- Practices are building blocks inside steps; the map should show where each practice is invoked.
Worked example
A provider wants a value stream for onboarding a new SaaS HR tool. Demand arrives from HR via the service catalogue. Steps: capture demand, assess and design, build/configure and test, transition and release, support. Reasoning: design and transition dominates, but the stream must include the support hand-off and an early plan/engage step, or the service goes live without capacity and security checks. Mapping the wait states between design and test reveals the true lead time.
Traps
- Confusing the value chain (generic) with a value stream (specific) - a very common distractor.
- Mapping only the happy path and omitting support and continual improvement.
- Treating the map as a one-off document rather than a continual improvement tool.