6.1 Value Stream Identification, Mapping & Management

Value Streams in ITIL (Version 5)

A value stream is a series of steps an organization undertakes to create and deliver products and services to a consumer. In ITIL (Version 5) each value stream is a specific, flexible combination of the eight Product and Service Lifecycle activities - discover, design, acquire, build, transition, operate, deliver, and support - assembled to respond to a particular type of demand or opportunity. There is no single "correct" value stream: an organization designs different value streams for different scenarios, such as onboarding a new user, resolving a major incident, or releasing a new feature.

Each stream orchestrates whichever lifecycle activities the work actually requires, which is why the value chain is described as a flexible operating model rather than a fixed sequence.

Value Stream vs Process

Candidates frequently confuse a value stream with a process, and the exam tests the distinction directly. A process is a set of interrelated or interacting activities that transform inputs into outputs; it is usually repeatable, bounded, and owned by a single practice or team. A value stream is broader and end-to-end: it runs from an initial demand or opportunity all the way to the realization of value for a consumer, and it typically spans several processes, practices, teams, and even suppliers.

A useful mental model: a value stream is the whole journey of value; processes are the individual engines that power segments of that journey.

Core and Enabling Value Streams

ITIL distinguishes two types. A core value stream directly creates and delivers value to a consumer - internal or external - and is customer-facing (for example, the stream that takes a service request from submission to fulfilment). An enabling value stream does not touch the consumer directly; it supports other value streams by providing internal capabilities, resources, or governance (for example, recruiting staff, procuring tools, or maintaining infrastructure). A common trap: the level of automation does NOT define the distinction - a core stream can be highly manual and an enabling stream fully automated.

The dividing line is direct value to a consumer versus support for other streams.

Value Stream Mapping

Value stream mapping (VSM) is a visualization technique that makes work visible so a team can see how work and information flow from demand to value. A map records each step, the handoffs between teams, and the measures that reveal where flow breaks down. Typical measures include:

• Lead time - total elapsed time from demand to value delivery.
• Process (cycle) time - the time actually spent working on a step.
• Wait time - idle time between steps, usually the biggest opportunity.
• Percent complete and accurate (%C&A) - how often work arrives usable, without rework.
• Flow efficiency - process time divided by lead time.

By comparing wait time to process time, teams usually discover that value spends most of its life waiting in queues, not being actively worked on.

Identifying Waste and Bottlenecks

Mapping exposes waste and bottlenecks. Waste is any activity that consumes resources without adding value - delays, unnecessary handoffs, rework, waiting, over-processing, and duplicated approvals. A bottleneck is a constraint where work piles up because a step cannot keep pace with demand; it caps the throughput of the entire stream, so improving any step other than the bottleneck rarely speeds up overall delivery.

Complexity thinking helps here: digital workflows involve non-linear dependencies and feedback loops, so teams should treat them as complex adaptive systems - experimenting with small, safe changes rather than assuming simple linear cause and effect.

Value Stream Management

A single map is a one-time snapshot. Value stream management is the ongoing discipline of continually managing, measuring, and improving flow and outcomes across value streams - governing them over time, tracking metrics, removing constraints, and feeding improvements back through the continual improvement model. The exam often contrasts these two ideas: the map is an artifact; management is the continuous activity.

Worked Scenario

A support team maps its "restore a failed login" value stream and finds a lead time of 26 hours but only about 40 minutes of actual process time - a flow efficiency near 3%. Most delay sits in two queues: waiting for identity-team approval and waiting for a change window. The bottleneck is the identity approval step. Adding staff to the service desk (a non-bottleneck) would not help; instead, optimizing the approval rule and then automating the delegated step cuts lead time dramatically. This illustrates the correct sequence: map first, locate the constraint, then optimize and automate.

Why Organizations Map Value Streams

Organizations map value streams to make invisible work visible, break down silos, shorten lead time, raise flow efficiency, remove waste, and ultimately improve the consumer's experience and the value co-created. Because value streams cut across the four dimensions and the whole lifecycle, they are the practical mechanism that connects strategy to day-to-day delivery - which is exactly why "value streams and processes" is one of the four dimensions of product and service management.

On the exam (5% weight) expect questions asking you to distinguish a value stream from a process, a core from an enabling stream, and a map from management, and to recognize why mapping reveals waste and bottlenecks.