Skip to content
All posts

ITIL 4 to ITIL v5: What Actually Changed (Notes From My Bridge Exam Prep)

What changed from ITIL 4 to ITIL v5, in plain English: the new 8-step lifecycle, regrouped practices, service relationships, and AI governance through an M365 lens.

I'm sitting the ITIL® Foundation Bridge (Version 5) exam, so I'm writing up what I learn as I go. Explaining something in my own words is the best test of whether I actually understand it. Hopefully it saves you some reading if you're making the same jump from ITIL 4.

A quick disclaimer: these are my study notes, not official guidance. Where I'm not sure, I'll say so. Once I've passed, I'll come back and correct anything I got wrong.

If you just want the headline, here it is. ITIL 4 was about managing services. ITIL v5 is about managing digital products and services together, across one lifecycle. Most of the rest follows from that.

The big shift: products, not just services

ITIL 4 already treated a service as a way of co-creating value with the customer. It didn't say much about the thing behind the service: the software, platform or tool someone has to design, build and keep improving.

v5 fills that gap. It separates the digital product (something built on digital technology) from the digital service (a service that relies fully or mostly on digital products), and manages both together. One product can support many services, and one service can depend on several products.

Here's how that looks in my day job. A PowerShell and Microsoft Graph automation that provisions Entra ID and M365 accounts is a product. "Automated employee onboarding" for HR is the service it makes possible. In ITIL 4 terms I'd mostly have talked about the service. In v5, the product has its own lifecycle too.

The value system and the new 8-step lifecycle

The Service Value System is now the ITIL Value System. Its five components haven't changed: guiding principles, governance, value chain, management practices and continual improvement. It still turns opportunity and demand into value.

The real change is inside the value chain. ITIL 4 had six activities. v5 replaces them with eight lifecycle activities that follow a product from idea to live support. The left column is my own rough comparison, not an official mapping:

Closest ITIL 4 activity (my reading)ITIL v5 lifecycle
PlanDiscover: keep roadmaps aligned with consumer needs and strategy
Design & transitionDesign: prototypes and specifications, including UX
Obtain/buildAcquire: secure the resources (and record them in the CMDB)
Obtain/buildBuild: develop, integrate, test (think CI)
Design & transitionTransition: get it into live use (continuous delivery or deployment)
Deliver & supportOperate: monitor and maintain (SRE, observability)
Deliver & supportDeliver: provide the service, handle requests, meet SLAs
Deliver & supportSupport: fix incidents, run disaster recovery
Engage, ImproveNo longer steps. Both now run across every activity

The last row is the one I found most interesting. Engagement (through the "service journey") and continual improvement happen everywhere, so v5 stopped treating them as steps in the chain. Like ITIL 4, the activities aren't a strict waterfall. Value streams combine them in whatever order the work needs.

A mnemonic I'm using for the order: Do Dogs Always Bark To Our Delivery Staff?

One small wording change I nearly missed: the last step of the continual improvement model is now "How do we keep the improvements relevant?" In ITIL 4 it was "How do we keep the momentum going?"

Practices, relationships and service quality

Practices: there are still 34, but they're grouped differently. ITIL 4 had three groups: general, service and technical. v5 has two: general management practices and product and service management practices. The technical group has gone.

Service relationships get a lot more detail:

  • A new organizational role, the digital product vendor: whoever creates and keeps improving the digital product. It sits alongside the familiar service provider and service consumer.
  • The consumer roles are the same as before. The sponsor pays, the customer defines requirements, the user uses the service.
  • Three relationship types:
    • Basic: standard services, standard SLAs, focused on efficiency. Buying M365 E5 licences is a good example.
    • Cooperative: customised services and more advanced SLAs, focused on improvement.
    • Collaborative: a real partnership with bespoke or outcome-based agreements, focused on innovation.
  • The service journey (Explore, Engage, Offer, Agree, Onboard, Co-create, Reflect) sits alongside a new idea, the band of visibility: how much of each organization the other can actually see.

Service quality now has four parts instead of two. Utility (fit for purpose) and warranty (fit for use) are joined by user experience and sustainability. Digital SLAs are expected to cover them, and UX metrics are expected for anything user-facing. That's a meaningful change if you've only ever reported uptime.

AI and governance: the part I care about most

AI goes from a passing mention in ITIL 4 to a core topic in v5. The main addition is the AI Capability Model, also called the "6C" model: Creation, Curation, Clarification, Cognition, Communication and Coordination. The idea is that AI works alongside people and strengthens what they do, not that it replaces them.

I work on Copilot adoption, so I tried mapping the model to things I've actually seen:

  • Creation: drafting emails, documents and summaries in Word and Outlook.
  • Curation: pulling the relevant files and threads together from across a tenant.
  • Clarification: explaining a long policy or a messy email chain.
  • Cognition: analysis and reasoning, e.g. spotting trends in data.
  • Communication: meeting recaps in Teams.
  • Coordination: agents that move work between people and systems.

That's my own mapping, not ITIL's. It did help the model click for me, though.

The other half is AI governance: directing, controlling and monitoring how AI is used, so it stays secure, ethical and compliant. Anyone who has rolled out Copilot will recognise this. Copilot can surface any file a user already has permission to see, so data governance (sensitivity labels, DLP, permissions hygiene) has to come first. v5 even lists data governance principles for this: strategic alignment, accountability and ownership, policies and procedures, transparency and auditability, integrity and adaptability.

The guiding principle Optimize and automate is the same, but it now covers AI explicitly. The rule hasn't changed: don't automate a broken process. Optimize it first, then automate, then add AI.

Governance more broadly is framed as governance of digital technology: engage stakeholders, evaluate, direct and monitor.

What stayed the same

If you know ITIL 4, a lot of v5 will feel familiar:

  • The seven guiding principles, word for word.
  • The four dimensions, now called the four dimensions of product and service management, with PESTLE factors still around the outside.
  • The continual improvement model, apart from that last step.
  • Core definitions such as service, value, outcome, incident and problem.

The new ideas worth learning properly are value stream mapping (identify, map the as-is, analyse, map the to-be, improve) and complexity thinking. Complexity thinking means choosing how to work based on how predictable the situation is.

What's next

The bridge exam is 20 questions in 30 minutes, and you need 13 to pass.

If you're preparing for the same exam, or spot something I've got wrong, get in touch.


ITIL® is a registered trademark of PeopleCert group. This post contains my personal study notes and interpretation. It is not official ITIL guidance.

Back to all posts