Updated September 2026.
PeopleCert opened ITIL Foundation (Version 5) exams in February 2026, and IT service management teams have been asking a version of the same question ever since: does this update actually change how ITSM gets run day to day, or is it a certification refresh with little bearing on daily service delivery? The honest answer is that ITIL (Version 5) changes enough of the underlying model, the lifecycle stages, the practice groupings, and the AI governance layered into the framework, that a practice claiming to follow ITIL cannot simply ignore it. It does not, however, require tearing out an ITIL 4 based ITSM practice and starting over.
This post breaks down what actually changed in ITIL (Version 5), why aligning your ITSM practices with it is worth the effort rather than just the certification, and a step by step way to do that alignment without disrupting the services you already run.
What ITIL (Version 5) actually changes
The framework’s own positioning is the biggest shift. ITIL 4 was built around IT service management. ITIL (Version 5) widens that scope to digital product and service management, explicitly bringing product thinking, roadmaps, product ownership, lifecycle economics, into a framework that used to speak almost entirely in service terms. For an ITSM team, that is not a rebrand. It means the framework now expects your practices to talk to product and engineering functions that ITIL 4 mostly left out of the picture.
Underneath that repositioning, five structural changes matter for anyone actually running an ITSM practice.
The Service Value Chain becomes an eight-stage lifecycle model
ITIL 4’s Service Value System is now the ITIL Value System, and its centerpiece, the six-activity Service Value Chain, is replaced by the ITIL Product and Service Lifecycle Model (PSLM). PSLM expands the model to eight activities and runs them as a single end to end flow across both product and service work, rather than the looser, non-linear chain ITIL 4 used. PeopleCert also introduced a companion ITIL Service Relationship Model alongside it, published to describe how the organization interacts with customers and partners across that same lifecycle.
Practices keep their names, but their grouping changes
All 34 ITIL management practices carry the same names into ITIL (Version 5). What changes is how they are grouped and, in PeopleCert’s own material, how the official practice guides describe some of them. ITIL 4 split practices into three categories: General Management, Service Management, and Technical Management. ITIL (Version 5) collapses that into two: General Management, and a combined Product and Service Management category that absorbs the former Technical Management practices. If your practice ownership model is still mapped to the old three-category split, that mapping is now out of date.
The four dimensions stay, and two of them now carry AI guidance
ITIL (Version 5) keeps all four dimensions from ITIL 4. Two of them are explicitly expanded. Organizations and People becomes, in effect, organizations, people, and AI, addressing how AI changes roles, skills, and decision rights. Information and Technology gains the ITIL AI Capability Model, a set of six elements, creation, curation, clarification, cognition, communication, and coordination, that PeopleCert uses to describe what an organization needs in place to run AI responsibly inside its service and product management practices.
The seven guiding principles did not change
Focus on value. Start where you are. Progress iteratively with feedback. Collaborate and promote visibility. Think and work holistically. Keep it simple and practical. Optimize and automate. All seven carry over from ITIL 4 unchanged, which matters practically: whatever cultural work your organization already did to embed these principles is not lost in the move to ITIL (Version 5).
ITIL 4 is not disappearing overnight
Foundation (Version 5) is currently the only broadly available ITIL 5 module, with Strategy, Product, Service, Experience, Transformation, and a separate AI Governance qualification rolling out in phases through 2026. Existing ITIL 4 certifications remain valid and act as a prerequisite for the advanced ITIL 5 modules, and PeopleCert’s current published plan is to sunset ITIL 4 modules on December 31, 2027. That gives most organizations a multi year runway to align gradually rather than switch everything on one date.
Why aligning matters, not just certifying
It is possible to send a team through Foundation (Version 5) training and change nothing about how work actually happens. That satisfies a certification requirement and does very little else. The reasons to actually align your practices go beyond the exam.
A unified lifecycle reduces handoff friction. When product and service work run through the same eight-stage model instead of a separate service chain and a separate product roadmap, the handoffs between engineering, product, and IT operations have a shared vocabulary and a shared set of checkpoints. That is where a lot of ITSM friction actually lives: not inside a single practice, but at the boundary between practices owned by different teams.
Discover and Acquire catch problems earlier. ITIL 4 shops that never formally worked the early parts of the Service Value Chain often skip straight to build and deploy, and only find out about vendor risk, licensing constraints, or unclear requirements once a service is already in flight. The lifecycle model’s explicit Discover and Acquire stages give those checks a defined home instead of leaving them to whoever happens to ask the right question in a kickoff meeting.
AI governance stops being ad hoc. Most ITSM practices already have some AI or automation running somewhere, a triage bot, an auto categorization model, a suggested resolution feature, usually adopted by whichever team got there first, with no consistent review process. The ITIL AI Capability Model gives that adoption a structure to be checked against: is there a defined way the organization creates AI capability, curates the data feeding it, clarifies what it is allowed to do, evaluates its reasoning, communicates its use, and coordinates it across teams. That is a governance checklist you can actually audit against, rather than a policy document nobody reads.
The switching cost is genuinely lower than it looks. Because the seven guiding principles and all 34 practice names carry over unchanged, an ITIL 4 mature organization is not starting from zero. The work is remapping and regrouping what already exists, not replacing it, which is a very different scope of project than most people assume when they hear “new version of the framework.”
A practical roadmap for aligning your ITSM practices with ITIL 5
None of the following steps require pausing live services or scrapping ITIL 4 work you have already done. They are meant to run in parallel with normal operations, over a few months rather than a single project sprint.
1. Baseline your current practices against the new structure
Take an inventory of your current 34 practices as they exist today and map each one to its new category, General Management or Product and Service Management, rather than the old three-category split. This step alone usually surfaces ownership gaps: practices that used to sit cleanly inside Technical Management often do not have a clear owner once they move into a combined product and service category.
2. Remap your delivery flow onto the eight-stage lifecycle
Walk a real service or product through the Product and Service Lifecycle Model stage by stage: Discover, Design, Acquire, Build, Transition, Operate, Deliver, Support. Note which stages already have a defined process and which ones happen informally. Discover and Acquire are the two most commonly missing in organizations that ran a mature ITIL 4 practice, since the Service Value Chain did not force either one into a distinct, visible stage.
3. Stand up AI governance guardrails using the AI Capability Model
Use the six elements, creation, curation, clarification, cognition, communication, and coordination, as a checklist against every AI or automation feature already running inside your service management tooling. For each one, document who created it, what data curates its behavior, how its scope is clarified to users, how its output quality is checked, how its use is communicated, and who coordinates it across teams. Gaps here are common even in otherwise mature practices, because AI features often get adopted by a single team without a central review.
4. Choose a certification and training path deliberately
Because ITIL 4 certifications remain valid and act as a prerequisite into the ITIL 5 advanced modules, there is no need to recertify a whole team on Foundation (Version 5) immediately. A more efficient path is to certify a small group first, let them lead the practice mapping and lifecycle remapping work, and expand training as the advanced modules, Strategy, Product, Service, Experience, and Transformation, become available through 2026.
5. Pilot on one service or product line before scaling
Pick one service or product line to run through the remapped lifecycle and updated practice ownership first. A single pilot surfaces friction, unclear handoffs, missing tooling support, gaps in the AI governance checklist, at a scale that is cheap to fix, before the same issues show up across the whole portfolio.
6. Reassess and reprioritize
Once the pilot has run, reassess maturity across the practice with the new structure in view, rather than assuming the old ITIL 4 maturity score still applies. The new lifecycle stages and AI guardrails frequently expose gaps that were simply never measured before, and those gaps should drive what gets prioritized next, not a generic rollout plan copied from a training vendor’s slide deck.
Where teams get this wrong
Most alignment efforts do not stall because ITIL (Version 5) is complicated. They stall because of a few familiar sequencing mistakes:
- Treating it as a training exercise only: sending the team through Foundation (Version 5) without changing a single workflow, so the certification updates but the practice underneath it does not.
- Trying to remap all 34 practices to the new categories in one pass, instead of prioritizing the small number that actually touch product decisions, AI features, or automation.
- Skipping a fresh baseline and assuming the old ITIL 4 maturity score still applies, when the new lifecycle stages and AI guardrails routinely expose gaps that were never scored before.
Where DesQcon fits
DesQcon runs ITSM maturity assessments as tool-agnostic, evidence-based engagements, scoring people, process, tooling, automation, AI readiness, and governance against a defined model, rather than a generic checklist borrowed from a training course. That is the same lens this alignment work needs: before remapping practices or setting AI guardrails against the new framework, it helps to know exactly where your current practice actually stands.
If your team is starting to plan an ITIL 5 alignment effort, the most useful first step is the same one we recommend before any transformation spend: see our ITSM Maturity Assessment Methodology for how we score people, process, tools, automation, AI, and governance, and read ITSM Maturity Assessment: Why It Should Come Before Your Transformation Budget for why that baseline should come before any new spend, ITIL 5 alignment work included.
Frequently asked questions
Do we have to replace ITIL 4 with ITIL 5 right away?
No. PeopleCert runs both frameworks at the same time, and existing ITIL 4 certifications remain valid and count as a prerequisite for the ITIL 5 advanced modules. PeopleCert’s current published plan is to sunset ITIL 4 modules on December 31, 2027, which gives most organizations a multi year window to align gradually.
Does aligning with ITIL 5 mean we need a new ITSM tool?
Not on its own. ITIL 5 is a practice and governance framework, not a product. The lifecycle model, the practice regrouping, and the AI governance guidance describe how work should be organized and controlled. Whether your current tooling can actually support that organization is a separate question, and it is usually the first thing a maturity assessment surfaces.
Where should a team that already runs mature ITIL 4 based ITSM start?
Start with the two changes that touch daily work the fastest: the AI Capability Model as a governance checklist for any AI or automation already running inside service management, and the two lifecycle stages, Discover and Acquire, that ITIL 4 shops most often handle informally outside a defined process.
Check your own ITSM and ITOM maturity
If this raised questions about where your own organization stands, DesQcon’s ITSM & ITOM Maturity Assessment gives you a structured, evidence-based read on that. Start with a free trial across one process area, or request the full deep-dive assessment across people, process, tools, automation, AI, and governance.
