ITIL is in an active transition. ITIL 4 remains available and recognized, while ITIL (Version 5) has become the new foundation for a more product-centric, AI-aware model of digital product and service management. That means current learners need to understand both continuity and change rather than treating the new version as either a complete reset or a cosmetic rename.
The ITIL certification family now includes ITIL Foundation (Version 5) alongside the still-available ITIL 4 Foundation. PeopleCert plans to keep ITIL 4 modules available until the end of 2027, and existing ITIL 4 credentials remain recognized for progression into higher-level Version 5 learning.
The durable learning goal is therefore not to memorize which version introduced which term. It is to understand how value, products, services, practices, people, technology, partners, information, governance, and continual improvement fit together in an operating model that can adapt as technology changes.
Foundation is about how value is created, not just service-desk process
Foundation-level ITIL study should help practitioners see technology work as part of a value system. Incidents, changes, requests, products, suppliers, automation, experience, and strategy all affect whether a customer or user receives the intended outcome. A team can meet internal process targets while still failing to create value.
This is why modern ITIL places stronger emphasis on end-to-end digital products and services. The question is not only whether a practice was followed, but whether the organization can reliably create, deliver, support, improve, and govern the outcomes that matter.
ITIL 4 remains relevant during the Version 5 transition
ITIL 4 concepts do not suddenly become wrong because a newer version exists. PeopleCert explicitly positions Version 5 as an evolution, and ITIL 4 qualifications continue to satisfy prerequisite requirements for higher-level Version 5 modules. The existing ITIL 4 Foundation certification therefore remains useful context for professionals already certified under the previous scheme.
Current learners should avoid mixing course material without labeling the version. Practices, principles, value concepts, and lifecycle framing overlap, but the qualification structures and emphasis have changed. Clear version awareness prevents a candidate from preparing for one exam with the vocabulary or weighting of another.
Version 5 expands the frame from services to digital products and services
ITIL (Version 5) responds to organizations where products and services are tightly connected. Digital teams often own a product lifecycle, platform capabilities, user experience, operations, commercial outcomes, and service relationships at the same time. The framework therefore needs to support both product thinking and service-management discipline.
This broader frame also makes handoffs more visible. Product decisions affect supportability; service commitments affect architecture; user experience affects demand; automation affects controls; supplier choices affect resilience. Foundation-level competence means seeing those dependencies before optimizing one local process.
AI is treated as an operating capability that still requires governance
Version 5 is explicitly designed for an AI-enabled environment. That does not mean every service-management problem should be solved with AI. It means organizations need a coherent way to adopt automation and AI while preserving trust, transparency, accountability, information quality, security, and human oversight.
Practitioners should evaluate where AI improves triage, knowledge, analysis, forecasting, self-service, or workflow execution and where it introduces new uncertainty. The same continual-improvement discipline applies: define the outcome, establish measures, test the change, observe side effects, and adjust based on evidence.
Practices work best when their interfaces are understood
Incident management, problem management, change enablement, service request management, service configuration management, information security management, supplier management, service-level management, and continual improvement are not independent boxes. Each practice creates information and decisions that another practice may need.
A useful study method is to follow one disruption from detection to restoration, root-cause work, change, communication, supplier involvement, knowledge update, and improvement. That reveals the real operating model better than learning one process flow at a time.
Metrics should describe outcomes as well as activity
Service-management teams can easily produce large dashboards: ticket counts, response times, change volumes, backlog size, automation rates, and availability percentages. Those measures are useful only when connected to user experience, business outcomes, risk, cost, and improvement decisions.
The strongest measures combine operational signals with context. A lower incident count can be positive, or it can mean users stopped reporting problems. Faster changes can indicate agility, or weaker review. ITIL thinking encourages teams to interpret measures inside the value system rather than reward activity in isolation.
The transition paths are designed to preserve prior investment
PeopleCert provides a Foundation Bridge for ITIL 4 Foundation holders who want a focused update to Version 5 concepts, and higher-level transition options for experienced designation holders. Existing knowledge remains useful; the transition is intended to let practitioners build on it rather than repeat their entire learning journey.
That matters for organizations as much as individuals. A company with mature ITIL 4 practices does not need to rename everything immediately. It can identify where Version 5 adds useful product, experience, transformation, and AI-governance guidance, then evolve operating models deliberately.
Foundation knowledge becomes valuable when it changes daily decisions
Certification is most useful when practitioners can use the framework to clarify work: what outcome are we trying to create, who is accountable, which practice owns this decision, what information is missing, how does the supplier fit, what risk is being accepted, and how will we know the change improved the service or product?
Those questions remain relevant across versions. Terminology will continue to evolve, but disciplined value creation, explicit responsibility, feedback, measurement, governance, and continual improvement are what make service management durable.
Learn Version 5 by following a digital product and service lifecycle
A practical way to learn ITIL (Version 5) is to follow one digital product or service from idea to retirement. Begin with the outcome: who needs value, what problem is being solved, what experience is expected, and how success will be measured. This keeps the framework grounded in real work before practices and process language begin to multiply.
During product or service design, identify stakeholders, suppliers, technology, data, risks, service levels, support needs, security obligations, and operating costs. Then ask which decisions must be made before launch and which can be improved through feedback. This makes the relationship between strategy, product, service, experience, and transformation more concrete than learning each topic independently.
At launch, focus on readiness. Support teams need knowledge, monitoring, escalation, request paths, incident procedures, change controls, supplier contacts, and clear ownership. The most elegant product design can still create poor value if operations cannot diagnose failures or users do not understand how to obtain help.
Once the service is live, watch the flow of work. Incidents reveal reliability and support weaknesses; requests reveal demand patterns; problems expose recurring causes; changes test governance; service levels show whether commitments still reflect stakeholder needs; experience data reveals whether technically successful service is actually usable. Each practice contributes a different signal about value.
AI can be introduced into the same lifecycle rather than treated as a separate initiative. An AI assistant might improve request fulfillment or knowledge discovery, but it also changes data use, user expectations, monitoring, security, and support. Governance should define acceptable use, evaluation, escalation, and human oversight before the automation becomes operationally critical.
Continual improvement should then use evidence from the live environment. Choose a measurable problem, understand the current state, define the desired outcome, make a controlled change, and observe whether value improved without creating unacceptable side effects. This keeps improvement connected to outcomes rather than to a backlog of disconnected optimization ideas.
Finally, retirement should be planned. Products and services eventually change ownership, merge, migrate, or end. Data retention, supplier obligations, user communication, configuration records, knowledge, access, and dependent services all need closure. Including retirement in study reinforces the Version 5 lifecycle perspective and prevents service management from becoming a framework concerned only with steady-state support.
The Version 5 qualification scheme also reinforces role-based progression. Foundation remains the entry point, while advanced learning moves into product, service, experience, strategy, transformation, and practice-manager combinations. That structure encourages professionals to deepen capability where their responsibilities actually lie rather than treat certification as a single linear ladder.
For someone already certified in ITIL 4, the practical choice is not whether the old credential is suddenly obsolete. It is whether a Foundation Bridge or a higher-level Version 5 module adds enough new value for the role. Organizations can make the same judgment for teams, upgrading knowledge where product, AI, transformation, or experience responsibilities have materially changed.
This transition period is therefore a good time to focus on concepts that survive version changes: value, systems thinking, feedback, clear ownership, reliable practices, meaningful measures, supplier relationships, governance, and continual improvement. Those are the foundations that make either qualification useful in day-to-day service management.
For teams adopting Version 5, pilot the new guidance in one product or service before rewriting the organization’s entire operating model. Compare the new lifecycle, product, experience, transformation, and AI concepts with existing ITIL 4 practices, then keep what improves decisions and clarify where terminology or responsibility genuinely needs to change. This approach preserves working capability while creating evidence for broader adoption.
Certification study should use the same discipline. Learners can map familiar ITIL 4 concepts to Version 5, note what has expanded, and then practice the new material through real service scenarios. That makes the transition easier to retain than memorizing two independent vocabularies.
ITIL Foundation in 2026 is best understood as continuity with a wider operating frame. ITIL 4 remains valid and available, while Version 5 extends the framework for digital products, AI-enabled work, and a streamlined qualification scheme.
Learners who understand the transition without treating either version as disposable can use ITIL for what it was meant to do: improve how organizations create and sustain value through technology-enabled products and services.