ITIL v4: What Changed From ITIL v3

In brief:

1. ITIL 4 replaces the ITIL v3 service lifecycle with a service value system, guided by guiding principles.
2. Former processes become practices, an expanded nomenclature of 34 entries that reaches beyond IT alone.
3. The four dimensions model, absent from ITIL v3, forces a wider view than a sequence of stages.
4. Migrating from ITIL v3 to ITIL 4 is a gradual process, it does not require starting over from scratch.

ITIL v4, more commonly called ITIL 4 since its publication by Axelos in 2019, is not a minor update to the previous framework. It changes the way the management of IT services is described in the first place: where ITIL v3 unfolded a five-stage lifecycle, ITIL 4 organises its content around a service value system and guiding principles. Understanding these changes helps place older content, still widely in circulation, and tells which parts remain usable as is.

The main changes between ITIL v3 and ITIL 4

Before going into detail, a correspondence table helps visualise where the gaps sit.

This table summarises the shape. The substance, how an organisation actually handles a request or an incident, changes less radically: much of the operational vocabulary stays recognisable from one version to the other.

From the service lifecycle to the service value system

ITIL v3 built its entire framework around a service lifecycle with five stages: service strategy, service design, service transition, service operation and continual service improvement. Every process belonged to one of these stages, giving a sequential, almost chronological reading of service management.

ITIL 4 drops that sequence in favour of a service value system, a structure that connects opportunities or demands to be handled, guiding principles, governance, the service value chain, practices and continual improvement. The stated goal is no longer to follow stages in order, but to allow flexible movement between these components depending on the context of each request.

The service value chain and its six activities

At the heart of the service value system sits the service value chain, which replaces the five lifecycle stages with six activities: plan, improve, engage, design and transition, obtain or build, deliver and support. These activities do not follow a fixed order: an organisation can combine them depending on what each request requires, which is precisely what the previous version did not easily allow. This flexibility echoes the logic behind ITIL methodology, which stresses adapting the framework to context rather than applying it mechanically.

From processes to practices: an expanded nomenclature

ITIL v3 described roughly twenty processes, such as incident management, change management or problem management, each tied to a lifecycle stage. ITIL 4 keeps that content but renames it as practices, raising the count to 34, split into three families: general management practices, service management practices and technical practices.

This change in vocabulary is not just a matter of wording. The word “process” evokes a sequence of steps to follow, the word “practice” points to a set of organisational resources mobilised to reach a goal, which allows for a more flexible implementation. The technical content of each building block stays close, though: an organisation that correctly distinguishes incident management from problem management under ITIL v3 finds the same distinction under ITIL 4, under a different name.

The four dimensions model, a notion absent from ITIL v3

ITIL 4 introduces a four dimensions model, meant to guarantee a holistic approach to service management: organisations and people, information and technology, partners and suppliers, value streams and processes. Every practice should be examined through these four angles before being implemented, to avoid a technical decision ignoring its effect on teams or external partners.

ITIL v3 did not formalise this overall view. Organisational or human considerations appeared scattered, process by process, with no shared framework to bring them together. The four dimensions model fills that gap by forcing a systematic review through the same four angles, whatever practice is involved.

The seven guiding principles, a new feature of ITIL 4

ITIL 4 places seven guiding principles ahead of its practices: focus on value, start where you are, progress iteratively with feedback, collaborate and promote visibility, think and work holistically, keep it simple and practical, optimise and automate. They work as rules of conduct for a given decision, not as steps to follow.

This layer of principles did not exist in this form under ITIL v3, whose logic relied more on the detailed description of processes than on cross-cutting decision rules. The detail of each of these seven guiding principles of ITIL 4 deserves its own examination, they shape how practices should be interpreted rather than applied to the letter.

Should you migrate from ITIL v3 to ITIL 4?

No text sets a deadline for dropping ITIL v3. The framework has not been updated since 2019, but an organisation still using it is not in breach of anything: ITIL remains a set of good practices, not an enforceable standard. The question mostly matters for three audiences: teams preparing a certification, those revising their internal documentation, and those wanting to align their vocabulary with recent hiring, often phrased in ITIL 4 terms.

The migration itself generally follows the progress iteratively guiding principle: adapt internal vocabulary gradually, document existing practices under their new name rather than rewriting all documentation at once. Organisations considering a certification should check the equivalences between schemes, a topic covered in the article on ITIL certifications: ITIL v3 certifications do not automatically grant the corresponding ITIL 4 level.

Frequently asked questions