4.5 The Value Chain: From Six Activities to Eight

The Value Chain: The Operating Model at the Center of the SVS

The value chain is the component of the ITIL Value System that actually converts demand and opportunity into value. It is an operating model: a set of interconnected activities that an organization combines in different ways to respond to each situation. The exam-critical point is that the value chain is not a fixed sequence every request must march through, it is a flexible toolkit whose activities are assembled into value streams to suit the specific demand, opportunity, product, or service context.

Blueprint note: six activities (ITIL 4) versus eight (Version 5)

Here Version 5 makes an important change that candidates must understand. Older material, and the ITIL 4 Service Value Chain, describes six value chain activities:

Version 5 restructures and expands these six activities into the eight-activity Product and Service Lifecycle, which now performs the role of the value chain inside the ITIL Value System. The eight activities are discover, design, acquire, build, transition, operate, deliver, and support. (You may see some training providers still present the six-activity chain and the eight-activity lifecycle as coexisting layers; for this exam, use the Version 5 wording and the mapping below.) The transformation is precise and is directly tested:

So plan and improve move up into the Value System as governance and continual-improvement concerns; engage is no longer a standalone activity but is woven through several lifecycle activities; and the three combined ITIL 4 activities each split into more granular Version 5 activities, with a brand-new Operate activity added to focus specifically on running live services. Overall the count grows from six to eight, and the activities become more specific.

The eight Version 5 activities in brief

Discover understands needs, opportunities, and value potential before committing to a solution. Design shapes how the product or service should work, feel, and integrate, including experience and service levels. Acquire obtains external resources or capabilities (buy, license, contract). Build creates, configures, integrates, and tests components. Transition moves a product, service, or change safely into live use. Operate keeps live products and services reliable, secure, and performing. Deliver provides products and services to consumers so agreed value is realized.

Support helps users and consumers when they have questions or issues. These activities are iterative and non-linear, work moves back and forth between them rather than flowing strictly top to bottom.

How activities combine into value streams

A value stream is a specific series of steps an organization uses to create and deliver products and services to a consumer. Value streams are built by combining value chain activities in whatever order and frequency the situation demands. Two different value streams, say, onboarding a new customer versus resolving a major outage, will call the same activities in different sequences and may revisit some activities several times. This is why the exam insists the activities are combined into value streams that fit the specific demand or opportunity, not run in one fixed order for every request.

A single change might touch discover, design, build, transition, operate, deliver, and support repeatedly before value is fully realized.

Worked example

Consider a value stream for launching a new self-service password reset. It might discover user pain points, design the flow, acquire an identity provider, build and test the integration, transition it live, then operate, deliver, and support it, looping back to design when feedback arrives. Planning and improvement are not steps in this stream; they sit in governance and the continual improvement model around it.

Exam traps

• Six versus eight. If a question uses Version 5 wording, the value chain is realized by the eight lifecycle activities; plan, improve, and engage are not among them.
• Fixed sequence. Value chain activities are combined flexibly into value streams; treating them as a mandatory waterfall is wrong.
• Where did plan and improve go? Up into governance and continual improvement, they were restructured, not deleted.

Practices and value streams work with the value chain

The value chain activities do not act alone: they draw on management practices for capability. When a value stream reaches its support activity, it invokes practices such as service desk, incident management, and problem management; when it reaches transition, it invokes change enablement and release management. Version 5 groups practices into general management practices and product and service management practices (replacing ITIL 4's three-group split).

Value streams themselves come in two kinds: a core value stream delivers value directly to a consumer, while an enabling value stream supports other streams behind the scenes. Cutting an enabling stream to save money usually breaks a core stream later, another reason the value chain is understood as one interconnected system rather than a set of independent steps.