1.2 What ITIL 4 Is and Why It Matters

Key Takeaways

  • ITIL 4 is the leading best-practice framework for IT Service Management, replacing the process-and-lifecycle model of ITIL v3.
  • ITIL v3 centred on a 5-stage service lifecycle with 26 processes; ITIL 4 centres on the Service Value System (SVS) with 34 practices.
  • The SVS is an end-to-end operating model whose engine is the six-activity service value chain.
  • ITIL 4 is built to integrate with Agile, DevOps, and Lean rather than compete with them.
  • ITIL 4 reframes everything around value co-created between a service provider and its consumers.
Last updated: June 2026

What ITIL 4 Is and Why It Matters

ITIL is the most widely adopted IT Service Management (ITSM) framework in the world. It is a body of best-practice guidance — not a rigid standard or a certifiable management system like ISO/IEC 20000 — that organizations adopt and adapt to plan, deliver, and continually improve IT-enabled services. ITIL 4 is the current edition, published by AXELOS, and it represents the framework's biggest reinvention in over a decade.

The central idea of ITIL 4 is value co-creation. A service does not deliver value on its own; value emerges from an active relationship between the service provider and the service consumer, who together combine resources to achieve outcomes. This reframing — away from "we run IT processes" toward "we co-create value" — underpins every concept in the syllabus and is a favourite theme of exam questions.

From ITIL v3 to ITIL 4

ITIL v3 (2007/2011) organized everything around a 5-stage service lifecycle — Service Strategy, Service Design, Service Transition, Service Operation, and Continual Service Improvement — containing 26 processes and four functions. It was powerful but often applied rigidly, process-by-process, in a way that felt heavy and disconnected from modern Agile and DevOps ways of working.

ITIL 4 (2019 onward) replaces that structure with the Service Value System (SVS) and reorganizes the old processes (plus new ones) into 34 practices. Crucially, ITIL 4 stops treating these as a sequence of stages and instead presents a flexible, value-focused operating model.

AspectITIL v3ITIL 4
Organizing model5-stage service lifecycleService Value System (SVS)
Core building blocks26 processes + 4 functions34 practices (3 categories)
Central focusProcesses and the lifecycleValue co-creation and outcomes
PrinciplesRACI, governance, ad hoc advice7 guiding principles
Ways of workingLargely pre-Agile/DevOpsIntegrates Agile, DevOps, Lean
Engine of deliveryLifecycle stages in sequenceSix-activity service value chain

Note that ITIL 4 does not simply rename the lifecycle. The exam expects you to know that processes became practices, that the lifecycle became the SVS and value chain, and that the count moved from 26 processes to 34 practices — a classic distractor is to attach v3 numbers or stage names to ITIL 4 concepts.

The Service Value System and Its Engine

The Service Value System (SVS) is ITIL 4's end-to-end operating model. It describes how all the components and activities of an organization work together to enable value creation. The SVS has five core components:

  1. Guiding principles — seven universal recommendations that steer decisions in any situation.
  2. Governance — how the organization is directed and controlled.
  3. Service value chain — the operating model's engine, with six activities.
  4. Practices — the 34 sets of organizational resources for performing work.
  5. Continual improvement — a recurring activity at every level.

The service value chain is the central engine that converts demand and opportunity into value. Its six activitiesPlan, Improve, Engage, Design and transition, Obtain/build, and Deliver and support — are not a fixed sequence. They combine into flexible value streams that draw on whichever practices are needed for a given piece of work, which is exactly how ITIL 4 supports iterative, Agile, and DevOps delivery.

Why It Matters and How Organizations Use It

Organizations adopt ITIL 4 to get a shared language, predictable service quality, and a structured way to balance speed with stability. Rather than implementing the framework wholesale, mature adopters use ITIL 4 selectively — applying the guiding principles to decisions, designing value streams around real demand, and maturing only the practices that solve their actual problems.

Key reasons ITIL 4 matters in modern IT:

  • It integrates, rather than competes. ITIL 4 is explicitly designed to coexist with Agile, DevOps, and Lean, positioning ITSM as the value-and-governance backbone around fast delivery.
  • It is value-driven and outcome-focused. Teams justify work by the outcomes and value it co-creates, not by process compliance.
  • It is end-to-end. The SVS connects strategy, demand, delivery, and improvement into one model rather than siloed stages.
  • It is adaptable. "Adopt and adapt" means there is no single mandated implementation, which is itself a tested concept.

For the exam, the takeaway is that ITIL 4 is a flexible, value-centric operating model — and many Foundation questions probe whether you can distinguish that modern framing from the older, process-heavy ITIL v3 mindset.

The Four Dimensions and the Practices

Two more pieces complete the ITIL 4 picture and appear throughout the exam. First, the four dimensions of service management are the perspectives you must balance for any service to be effective:

  1. Organizations and people — culture, roles, structures, and competencies.
  2. Information and technology — the data, knowledge, and technologies a service needs.
  3. Partners and suppliers — the external relationships and contracts that support delivery.
  4. Value streams and processes — how the organization's activities are arranged to create value.

Neglect any one dimension and a service suffers, which is why ITIL 4 insists you consider all four together.

Second, the 34 practices are organized into three categories: general management practices (e.g. continual improvement, risk management, information security), service management practices (e.g. incident management, change enablement, service desk), and technical management practices (e.g. deployment management, infrastructure and platform management). A practice is simply a set of organizational resources designed for performing work or accomplishing an objective — and because practices replaced v3's processes, knowing this definition is itself a commonly tested fact.

Test Your Knowledge

Which statement best describes the structural shift from ITIL v3 to ITIL 4?

A
B
C
D
Test Your Knowledge

What is the engine at the centre of the ITIL 4 Service Value System?

A
B
C
D
Test Your Knowledge

How does ITIL 4 relate to Agile, DevOps, and Lean?

A
B
C
D