Daria Golomazova/July 31, 2026/inBlog/tags:ITSM

ITIL Service Value System (SVS): Components, Value Chain, and the Evolution to ITIL 5

Explore the ITIL Service Value System, its five components, six value chain activities, and how ITIL 5 evolves the framework.

Not doing enough is rarely the reason for struggles of IT teams. More often, the problem is that those activities are disconnected.

A service desk resolves incidents, an infrastructure team manages assets, developers release changes, and managers track performance to stay within targets. Each group may do its own work well. Yet customers can still experience delays, repeated issues, inconsistent decisions, and services that do not meet their actual needs.

The ITIL Service Value System, or SVS, was designed to address this problem. Instead of treating service management as a collection of isolated processes, it shows how governance, organizational principles, management practices, operational activities, and continual improvement work together to turn demand into value.

This article first explains the established ITIL 4 Service Value System and Service Value Chain. It then examines what ITIL Version 5 keeps, what it changes, and how organizations can extend their current service management approach without discarding what already works.

What is the ITIL Service Value System?

The ITIL Service Value System is a model showing how the components and activities of an organization work together to enable value co-creation.

Its input is an opportunity or demand. Its intended output is value for the organization, its customers, users, and other stakeholders. Between the two are five interconnected components:

Guiding Principles
Governance
Service Value Chain
Management practices
Continual improvement

The SVS is not a single process, workflow, or department. It is the wider organizational system within which processes and workflows operate. The official ITIL guidance defines it as the way all organizational components and activities unite to enable value co-creation.

The five components of the ITIL 4 Service Value System

The five SVS components are not separate stages. They interact within the same organizational system and may influence the same value stream simultaneously.

Guiding Principles

ITIL 4’s seven guiding principles help teams make consistent decisions through changes in strategy or structure:

“Focus on value” means judging every action—a new tool, a process tweak, a reporting change—by the value it delivers to the customer or stakeholder;
“Start where you are” means examining existing workflows before replacing them;
“Progress iteratively with feedback” favors piloting a new process in one department first;
“Collaborate and promote visibility” means pulling in the people affected by a decision early and keeping work status visible, so blockers surface before they turn into missed deadlines;
“Think and work holistically” means checking how a change to one service ripples into other systems, teams, and suppliers before it goes live;
“Keep it simple and practical” means cutting a workflow to the fewest steps that still get the job done, without stripping out the controls that protect security, compliance, or quality;
“Optimize and automate” means fixing a workflow before automating it, since automating a process that creates no value just moves the waste faster.

Governance

Governance directs and controls the organization through three activities: evaluate, direct, monitor. It sets priorities, decision rights, accountability, policies, risk tolerance, and performance expectations, keeping local improvements aligned with strategy—for instance, which changes need authorization or how failures get reported. Governance sets direction and boundaries rather than doing the work: without it, a service desk might cut handling time by escalating more tickets, improving its own metric while creating delays elsewhere.

Service Value Chain

The Service Value Chain is the SVS’s operational core: a flexible model of six interconnected activities—Plan, Improve, Engage, Design and Transition, Obtain/Build, Deliver and Support—combined into value streams. These aren’t fixed sequential stages; a stream can repeat activities, loop back on new information, or skip steps it doesn’t need. We’ll take a closer look at them later on.

Management practices

ITIL defines a practice as a set of organizational resources for performing work or achieving an objective—broader than a process diagram, spanning people, roles, workflows, records, software, suppliers, and performance measurement.

ITIL 4 defines 34 management practices; however, organizations don’t need every one at the same maturity level or in every value stream. An onboarding stream, for example, might draw on Service Request Management, IT Asset Management, and Change Enablement. Practices supply the capabilities; the value stream decides how they combine to deliver an outcome.

We cover what “maturity level” actually looks like at each stage in our separate guide to the ITIL maturity model.

Continual improvement

Continual improvement runs across strategic, tactical, and operational levels to keep performance aligned with stakeholder expectations—covering services, practices, tools, and the SVS itself, not just an annual review. Reviewing an onboarding stream might ask which tasks get delayed most or whether current metrics reflect real business outcomes. Improvement data comes from tickets, workflow histories, customer feedback, dashboards, and audits.

The ITIL 4 Service Value Chain: six flexible activities

Plan builds shared understanding of the organization’s vision, current state, priorities, and improvement direction, covering demand forecasting, capacity, roadmaps, and budgets.

Improve keeps products, services, and practices aligned with changing expectations. Improvement can start anywhere — an incident trend can expose a design flaw, feedback can reshape a catalog — and runs throughout the entire SVS, not only in this named activity.

Engage builds and maintains understanding of stakeholder needs: gathering requirements, managing expectations, communicating status, negotiating with suppliers.

Design and Transition ensures new or changed products meet expectations for quality, cost, usability, security, and operability, factoring in from the start how a solution will be supported and maintained.

Obtain/build supplies the components needed to deliver a product or service — built internally, configured, purchased, or sourced through suppliers.

Deliver and Support ensures products and services are delivered as agreed: daily provision, request fulfillment, incident resolution, and user assistance.

A value stream is a specific path through these six activities. A simple access request might rely mainly on Engage and Deliver and Support; a complex build might use all six, cycling between Design and Transition and Obtain/Build. That flexibility is the whole point—the diagrams can look like a conveyor belt, but the activities aren’t meant to run in a fixed line.

ITIL 5: introduction and evolution

ITIL Version 5 builds on ITIL 4 rather than replacing it: ITIL 4 remains widely used, while ITIL Version 5 is being introduced gradually, and official materials explicitly retain its guiding principles and Service Value System—governance, the value chain, practices, and continual improvement.

That means your organization can keep its existing ITIL 4 practices, workflows, and records as a working foundation; nothing here needs to be discarded. The real changes are less about replacing service management and more about extending it into a few specific areas: how products and services are managed together, AI- and complexity-native design, and a new product-and-service lifecycle model. Let’s take a closer look at one aspect at a time.

Products and services are managed together

Version 5 makes explicit that a digital product and the service built around it are two views of the same solution. A collaboration platform, for instance, is both a product that teams build and a service that users experience and receive support for. This perspective encourages shared responsibility across product, service, operations, security, and supplier teams.

AI-native and complexity-native

Version 5 is “AI-native”: roles, practices, and value streams are built to be AI-enhanced while staying technology-agnostic, with attention to responsible AI governance. It’s also “complexity-native”—organizations need to experiment and adapt rather than execute a fixed plan. This isn’t just about inserting AI everywhere: people still need new skills, cross-team collaboration, and judgment.

The 34 practices remain

The 34 management practices stay largely intact, now grouped as Product and Service Management Practices and General Management Practices. Familiar areas—Incident Management, Change Enablement, Service Request Management, IT Asset Management, Information Security Management—remain relevant.

A note on terminology

Official materials state that Version 5 retains the service value system and includes a simplified, more recognizable ITIL value chain. They separately introduce the eight-stage ITIL Product and Service Lifecycle Model.

Some early training articles refer to the eight stages as a new Service Value Chain. Others describe the lifecycle model as a replacement for the ITIL 4 chain or use “value chain” and “lifecycle” almost interchangeably.

The ITIL 5 Product and Service Lifecycle Model

Eight shared activities for products and services, presented as an integrated ecosystem rather than a fixed sequence—any activity can loop back to another, and different versions of a product can sit at multiple stages at once:

Discover — focuses on understanding opportunities, needs, and desired outcomes and can recur throughout the lifecycle.

Design — defines how the product and service will work and how users will experience them.

Acquire — sources the internal or external resources required and is treated separately from Build.

Build — creates, configures, integrates, and tests components.

Transition — moves a product or service into controlled use and may occur at several points.

Operate — keeps systems and infrastructure available, secure, and performant.

Deliver — makes the product or service available with the intended user experience.

Support — helps users resolve issues and feeds insights back into earlier lifecycle activities.

The eight stages aren’t a clockwise checklist—a support issue can expose a design flaw; one version might be in Build while another is in Operate and Support. The “diamond” model captures this shared, ongoing responsibility better than a linear pipeline.

ITIL 4 Service Value Chain vs. the ITIL 5 Lifecycle Model

The following comparison shouldn’t be treated as an official one-to-one conversion table. You can use it as a practical way to understand the change in emphasis.

ITIL 4 Service Value Chain	ITIL 5 Evolution
Focuses on creating service value	Explicitly integrates digital product and service management
Uses six broad value chain activities	Introduces eight product and service lifecycle activities
Combines Design and Transition	Shows Design and Transition separately
Combines Obtain/Build	Distinguishes Acquire from Build
Combines Deliver and Support	Distinguishes Operate, Deliver, and Support
Includes Plan, Engage, and Improve as named chain activities	Planning, stakeholder engagement, and improvement continue across the wider system and lifecycle
Uses flexible value streams	Emphasizes an interconnected ecosystem with repeated, backward, and forward movement

How the SVS components work together: a practical example

The SVS is easiest to understand applied to a real scenario. Leo Burnett provides a useful example.

Leo Burnett experienced significant growth, adding 90 employees during one year. Their IT team needed a scalable way to handle support, assets, accounts, and compliance across countries. When a new employee joined, HR submitted a request; IT created the account while Active Directory Import synced data with Alloy Navigator. The original requests and the activity logs in Incident and Work Order tickets later provided an audit trail for Sarbanes-Oxley compliance.

Operationally, this may look like a routine onboarding request. From an SVS perspective, however, it is an outcome involving people, technology, and controls: the demand is the need to onboard a new employee, and the value is a properly provisioned employee who can work productively, while the organization maintains security, accountability, and reliable audit evidence.

Guiding principles at work:

Focus on value: an operational employee, not isolated IT tasks.
Collaborate and promote visibility: HR initiates the request, IT performs technical work, and shared records provide visibility into progress.
Think and work holistically: The employee, account, equipment, software, permissions, requests, and compliance evidence are related parts of the same outcome.
Optimize and automate: Active Directory synchronization and automated ticket creation reduce repetitive administration without removing human accountability.

In the Leo Burnett example, requests, Work Orders, and activity histories helped demonstrate authorization and the work performed. This example shows how governance can turn onboarding into a controlled and traceable business process rather than a series of disconnected tasks.

What should organizations using ITIL 4 do now?

ITIL Version 5 doesn’t call for an immediate migration project. The practical move is to extend what already works.

Keep effective ITIL 4 practices: don’t redesign a stable incident, request, change, or asset management practice just because a new version exists — check first whether it still creates value.
Map the products behind your services: document which digital products enable each service, who owns them, and how feedback reaches the right teams.
Review one important product against all eight lifecycle activities—Discover, Design, Acquire, Build, Transition, Operate, Deliver, and Support—to expose handoff gaps without requiring a full reorganization.
Involve operations and support earlier, factoring in security and monitoring during Design and Build rather than after transition.
Add governance for AI and automation: define where AI can assist, which decisions need human review, and who stays accountable, so automation accelerates a well-governed stream instead of obscuring responsibility.
Measure outcomes across the whole stream — a metric like ticket closure time is useful but isn’t value on its own; tie it to productivity, customer experience, or compliance.
Progress iteratively, applying the Version 5 perspective to one value stream before touching the whole operating model.

Common misunderstandings about the ITIL SVS and ITIL 5

“ITIL 4 is obsolete now” — It stays available through the transition; its core concepts carry into Version 5.

“Every value stream must use every activity” — A stream only uses what its outcome needs.

“The eight lifecycle activities must occur in order” — The model is explicitly non-linear.

“The SVS and the value chain are the same thing” — The value chain is one component of the wider SVS.

“Practices disappeared in ITIL 5” — The 34 practices remain largely the same, just regrouped.

“Buying ITSM software means we’ve implemented ITIL” — A tool supports records and workflows; the organization still defines value and governance itself.

Conclusion

Conclusion: from processes to a connected value system
The lasting contribution of ITIL 4 is the recognition that value cannot be produced by isolated processes. Guiding principles shape decisions, governance sets direction, practices supply capabilities, value streams coordinate the work, and continual improvement keeps the system adapting.

ITIL Version 5 carries this logic forward. Its expanded product-and-service perspective reflects how digital organizations now operate: development, acquisition, transition, operations, delivery, and support are interconnected rather than separate worlds.

Organizations can keep what works from ITIL 4 while building a more integrated view of the products, people, and technologies that create value—with a platform like Alloy Navigator connecting requests, assets, approvals, and performance data to make value streams visible and manageable.