Based on publicly available information about ITIL 5, I’ve created, supported by AI, an interactive guide to bring you up to speed in no time.
The original intent of this article was to shed light on the new ITIL 5, but I soon went down the rabbit hole of Framework Proliferation. This article ended up serving two purposes: to convey what the new ITIL 5 is and to offer my critical take on the growing Framework Proliferation.
DISCLAIMER: Despite my attempt to qualify the guide, AI does make mistakes. Also, this is my understanding, interpretation, and selected focus. Do not perceive this guide as anything other than inspiration. It is not a substitute for the actual books and resources behind.
What is it - officially
ITIL (Information Technology Infrastructure Library) is the world’s leading framework for managing digital products and services. While ITIL 4 established the modern operating model by integrating Agile, Lean, and DevOps, ITIL Version 5 represents a major structural evolution. It shifts the framework from a purely service-centric model to a unified Digital Product and Service Management approach, designed specifically to be “AI-native” and suited for rapid digital transformation.
What purpose does it serve - officially
At its core, ITIL provides individuals in IT service organizations with a shared language and a structured operating model to ensure technology investments directly drive tangible business outcomes. It serves several critical purposes:
Unified Lifecycle Management: ITIL 5 introduces an 8-stage end-to-end lifecycle (Discover, Design, Acquire, Build, Transition, Operate, Deliver, Support). This allows teams to manage digital products (like applications and APIs) alongside traditional IT services without forcing product teams to use outdated, service-only vocabulary.
Value Co-Creation & Experience: It shifts the focus from simply delivering technical outputs to actively collaborating with stakeholders. In Version 5, User/Customer Experience (UX/CX) has been elevated to its own dedicated discipline.
Risk, Cost, and Reliability: It utilizes 34 standard management practices (such as Incident, Problem, and Change Enablement) to minimize operational risk, reduce waste, and ensure high availability.
AI and Automation Governance: It provides a built-in framework for adopting AI and automation ethically, transparently, and securely, ensuring regulatory alignment and responsible deployment.
My critical take and concern - the Framework Proliferation crisis
The enterprise digital operating environment has become highly fragmented, inefficient, and redundant due to direct conflicts among competing corporate frameworks (such as POM, ITIL 5, and SAFe).
The core problem is that commercial framework owners must continually expand their scope to remain market-relevant and protect certification revenues. As a result, frameworks that historically managed entirely different domains (e.g., IT Operations vs. Product Innovation) have expanded until their definitions completely overlap.
The exploration and alignment phase. Teams actively listen to the market, capture user demands, and identify opportunities. The goal is to align the product roadmap with the organization’s overarching business strategy.
Design
The architectural blueprint phase. Focuses on planning the engineering and technical requirements, user experiences (CX/EX), information security, support structures, and risk mitigation strategies
Acquire
The resource procurement phase. Organizations secure the necessary third-party tools, vendor partnerships, technical skills, software licenses, or cloud infrastructures required to move forward
Build
The creation and integration phase. Developers and platform engineers write software, configure systems, and perform exhaustive automated or manual testing to ensure solutions are ready for production.
Transition
The deployment and change management phase. The product or feature is safely introduced into the live environment. The primary metric here is minimizing disruption to existing infrastructure.
Operate
The stability and systems management phase. Focuses on maintaining day-to-day backend operations, managing databases, keeping cloud environments active, and ensuring the technical infrastructure performs smoothly
Deliver
The actual service consumption phase. This is the critical touchpoint where the customer or employee interacts with the digital product to realize tangible business value.
Support
The safety net and incident management phase. Focuses on resolving issues, helping users when errors occur, and restoring normal operations rapidly when things do not go as planned.
You do not have to know much about the Product Operating Model to spot the obvious overlaps.
Should you have read some of the articles here on the blog about harmonized standards, you’ll probably have noticed how standardization work addresses the overlap of standards: through mapping and through the use of Lex Specialis.
The caveat in the commercial space is that it is commercial. The SAFe organization is known for stealing (e.g., Team Topologies and POM!) Now, ITIL 5 includes, e.g., a new lifecycle structure that clearly overlaps with the Product Operating Model.
Commercial players do not have the same high ethical standards or incentive to keep the “framework space” consistent as standardization organizations do when dealing with harmonized standards.
Let me guide you
You have now been warned!
I’ve decided to provide an interactive guide that, on the one hand, conveys what is publicly available about ITIL 5 and, on the other hand, includes my concerns about the growing mess of frameworks.
Steps 1-6 provide the objective, factual ITIL 5 syllabus, and Step 7 provides my critical, real-world analysis. Finally, the Exam Simulator takes you through the pure ITIL 5 material, without any of my framework rants.
ITIL 5 and the Framework Trap
Surviving Enterprise Governance in a Product-Driven World
Digital Product & Service Management
ITIL 4 Upgrade Note
The Scope has Expanded: If you are transitioning from ITIL 4, the biggest conceptual shift is the explicit inclusion of "Digital Products." You no longer have to shoehorn software development and modern product management into traditional "service" terminology.
Official Concept
Digital Product and Service Management: A unified approach for managing digital products (like applications and APIs) alongside traditional IT services, enabling value co-creation in an AI-native ecosystem.
ITIL 5 represents a major structural evolution. It shifts the framework from a purely service-centric model to a unified approach. This allows teams to manage end-to-end digital products effectively and transparently.
Technology is advancing faster than ever. Developments like Artificial Intelligence, advanced cloud-native computing, and automation are no longer aspirational—they are standard operating conditions. ITIL 5 is specifically designed to be AI-native, providing a built-in framework for adopting these technologies ethically.
Key Concepts & Value Co-creation
ITIL 4 Upgrade Note
Elevation of UX/CX: While ITIL 4 introduced the concept of value co-creation, ITIL 5 formalizes User Experience (UX) and Customer Experience (CX) as measurable, primary disciplines. It's no longer just about meeting technical specs (utility and warranty), but ensuring a seamless qualitative experience.
Developing specialized organizational capabilities requires a shared understanding of the nature of value, the stakeholders involved, and how value is enabled through products and services.
Value and Value Co-creation
Official Definition
Value: The perceived benefits, usefulness, and importance of something.
The purpose of an organization is to create value for stakeholders. Value is co-created through active collaboration between providers and consumers.
Service Providers and Consumers
Customer
A person who defines the requirements for a service and takes responsibility for the outcomes of service consumption.
User
A person who uses services or interacts directly with digital products.
Sponsor
A person who authorizes budget for service and product consumption.
Utility and Warranty
U Utility
The functionality offered by a product or service to meet a particular need ("Fit for purpose").
W Warranty
Assurance that a product or service will meet agreed requirements ("Fit for use").
The 4 Dimensions of Service Management
ITIL 4 Upgrade Note
The Dimensions are Retained: The structure of the Four Dimensions remains identical to ITIL 4. However, the "Information and Technology" dimension explicitly covers Large Language Models (LLMs), AI data modeling, and Zero-Trust cloud security in modern deployments.
1. Organizations and People
Ensures that the way an organization is structured and managed is well defined. People are key: it covers their culture, skills, competencies, management styles, and collaboration.
2. Information and Technology
Includes the information and knowledge necessary, as well as the technologies required. In ITIL 5, this heavily emphasizes AI data models, automated workflow systems, cloud architecture, and security.
3. Partners and Suppliers
Encompasses relationships with other organizations involved in the design, development, and continual improvement of services. It involves managing service integration and AI/Cloud vendor relationships.
4. Value Streams and Processes
Concerned with how the various parts of the organization work in an integrated and coordinated way to enable value creation.
The Service Value System (SVS) & AI
ITIL 4 Upgrade Note
The SVS remains the Core: The overarching Service Value System (SVS) is fully retained in ITIL 5. However, Guiding Principle 7 (Optimize and Automate) now explicitly provides governance for deploying autonomous AI agents and automated telemetry.
The ITIL Service Value System (SVS) describes how all the components and activities of the organization work together to enable value creation. It relies on 7 core principles.
The 7 Guiding Principles
Everything that the organization does needs to map, directly or indirectly, to value for the stakeholders. This encompasses the experience of customers and users (CX/UX).
In Practice: Before starting an initiative, ask "Who is this for?" and "How does this improve their experience or business outcome?" Avoid vanity metrics.
Do not start from scratch and build something new without considering what is already available to be leveraged. Investigate and observe the current state directly.
In Practice: Avoid the temptation to rip out legacy systems immediately. Assess current processes objectively using data, not assumptions, to find what is already working.
Do not attempt to do everything at once. Organize work into smaller, manageable sections that can be executed in a timely manner. Use feedback loops continuously.
In Practice: This aligns with Agile methodologies. Deliver Minimum Viable Products (MVPs) quickly to test hypotheses and adjust course based on actual user reactions rather than long-term theoretical plans.
Working together across boundaries produces results that have greater buy-in and relevance. Work and consequences should be made visible.
In Practice: Break down silos between development and operations. Use shared dashboards (like Kanban boards or Jira) so everyone understands the current constraints, flow of work, and strategic goals.
No service, practice, process, department, or supplier stands alone. Results are delivered through the dynamic integration of all components.
In Practice: Recognize that altering a single line of code can impact support teams, cloud costs, and third-party vendor agreements. Always assess the end-to-end impact across the Four Dimensions.
If a process, service, action, or metric fails to provide value or produce a useful outcome, eliminate it. Use the minimum number of steps necessary to accomplish an objective.
In Practice: Don't create bureaucratic red tape just because "it's the way we've always done it." If an approval step doesn't reduce risk, remove it to speed up delivery flow.
Eliminate waste and use AI/automation to achieve whatever technology is capable of. Human intervention should only happen where it uniquely contributes value.
In Practice: This is a massive focus in ITIL 5. Automate repetitive tasks (like password resets or server provisioning) using scripts and AI, freeing up humans for complex problem-solving and innovation.
Goodbye Service Value Chain (SVC)! While the broader SVS remains, ITIL 5 formally retires the internal 6-activity Service Value Chain (Plan, Improve, Engage, etc.). It is replaced by the unified Product and Service Lifecycle Model (PSLM), consisting of 8 distinct linear stages.
The Official 8 Stages
Purpose: To identify market needs, opportunities, and understand stakeholder requirements for new value.
In Practice: It involves active user research, competitive analysis, and validating business viability before significant resources are committed. Outputs include a clear product vision and validated hypotheses.
Purpose: To create solutions that deliver value, ensuring that the utility, warranty, and overall user experience (UX) meet the criteria identified in Discovery.
In Practice: Translating discovered needs into architectural blueprints, UX/UI wireframes, and technical specifications. It also involves ensuring that InfoSec, regulatory compliance, and cloud architecture constraints are mapped out early.
Purpose: To source the necessary components, licenses, partnerships, or capabilities required.
In Practice: Procuring SaaS software, cloud compute structures, or specialized APIs from third-party vendors.
Purpose: To physically build, code, configure, or assemble the product or service components.
In Practice: This is the execution phase. It involves writing application code, training AI data models, configuring SaaS platforms, and integrating APIs.
Purpose: To move built solutions and updates safely into live production environments.
In Practice: Utilizing automated CI/CD (Continuous Integration / Continuous Deployment) pipelines, automated testing, and release toggles to ensure new features are deployed rapidly with zero downtime and a minimal blast radius.
Purpose: To run the live environment, monitor performance, and ensure infrastructure stability.
In Practice: Active monitoring of cloud environments, managing automated telemetry, and ensuring platform availability meets defined service levels.
Purpose: To provide ongoing service delivery, execute agreed service actions, and make the value available to the consumer.
In Practice: The product is live and in the hands of the user. Focus shifts to delivering the agreed utility, managing automated service fulfillment, and ensuring users can successfully achieve their outcomes using the product.
Purpose: To resolve issues, handle user inquiries, and maintain high service quality.
In Practice: This involves rapid incident response, finding workarounds for problems, and answering standard user service requests via AI chatbots or human agents.
The 34 Management Practices
⚡ ITIL 4 Upgrade Note: The 34 practices remain structurally intact, but core terminologies have evolved to better suit modern workflows. For example, **Change Control** has been fully renamed/modernized to **Change Enablement** to reflect peer-reviews and decentralized, rapid automated change authorization.
14
General Management Practices
Purpose: To provide an understanding of all the different elements that make up an organization and how those elements interrelate, enabling the organization to effectively achieve its current and future objectives.
Purpose: To align the organization's practices and services with changing business needs through the ongoing improvement of products, services, and practices, or any element involved in the management of products and services.
Purpose: To protect the information needed by the organization to conduct its business. This includes understanding and managing risks to the confidentiality, integrity, and availability of information, as well as aspects such as authentication and non-repudiation.
Purpose: To maintain and improve the effective, efficient, and convenient use of information and knowledge across the organization.
Purpose: To support good decision-making and continual improvement by decreasing the levels of uncertainty. This is achieved through the collection of relevant data and the valid assessment of this data in an appropriate context.
Purpose: To ensure that changes in an organization are smoothly and successfully implemented, and that lasting benefits are achieved by managing the human aspects of the changes.
Purpose: To ensure that the organization has the right mix of programmes, projects, products, and services to execute the organization's strategy within its funding and resource constraints.
Purpose: To ensure that all projects in the organization are successfully delivered. This is achieved by planning, delegating, monitoring, and maintaining control of all aspects of a project.
Purpose: To establish and nurture the links between the organization and its stakeholders at strategic and tactical levels. It ensures that the organization continually creates and maximizes value.
Purpose: To ensure that the organization understands and effectively handles risks. Managing risk is essential to ensuring the ongoing sustainability of an organization and creating value for its customers.
Purpose: To support the organization's strategies and plans for service management by ensuring that the organization's financial resources and investments are being used effectively.
Purpose: To formulate the goals of the organization and adopt the courses of action and allocation of resources necessary for achieving those goals.
Purpose: To ensure that the organization's suppliers and their performances are managed appropriately to support the seamless provision of quality products and services.
Purpose: To ensure that the organization has the right people with the appropriate skills and knowledge and in the correct roles to support its business objectives.
17
Service & Product Management Practices
Purpose: To ensure that services deliver agreed levels of availability to meet the needs of customers and users.
Purpose: To analyse a business or some element of it, define its associated needs, and recommend solutions to address these needs and/or solve a business problem.
Purpose: To ensure that services achieve agreed and expected performance, satisfying current and future demand in a cost-effective way.
Purpose: To maximize the number of successful service and product changes by ensuring that risks have been properly assessed, authorizing changes to proceed, and managing the change schedule.
Purpose: To minimize the negative impact of incidents by restoring normal service operation as quickly as possible. An incident is an unplanned interruption to a service or reduction in the quality of a service.
Purpose: To plan and manage the full lifecycle of all IT assets to help the organization maximize value, control costs, manage risks, support decision-making, and meet regulatory/contractual requirements.
Purpose: To systematically observe services and service components, and record and report selected changes of state identified as events.
Purpose: To reduce the likelihood and impact of incidents by identifying actual and potential causes of incidents, and managing workarounds and known errors.
Purpose: To make new and changed services and features available for use by consumers.
Purpose: To provide a single source of consistent information on all services and service offerings, and to ensure that it is available to the relevant audience.
Purpose: To ensure that accurate and reliable information about the configuration of services, and the configuration items (CIs) that support them, is available when and where it is needed.
Purpose: To ensure that the availability and performance of a service are maintained at sufficient levels in case of a disaster. The practice provides a framework for building organizational resilience.
Purpose: To design products and services that are fit for purpose, fit for use, and that can be delivered by the organization and its ecosystem.
Purpose: To capture demand for incident resolution and service requests. It is the entry point and single point of contact for the service provider with all of its users.
Purpose: To set clear business-based targets for service levels, and to ensure that delivery of services is properly assessed, monitored, and managed against these targets.
Purpose: To support the agreed quality of a service by handling all pre-defined, user-initiated service requests in an effective and user-friendly manner.
Purpose: To ensure that new or changed products and services meet defined requirements.
3
Technical Management Practices
Purpose: To move new or changed hardware, software, documentation, processes, or any other component to live environments. It may also be involved in deploying components to other environments for testing or staging.
Purpose: To oversee the infrastructure and platforms used by an organization. This enables the monitoring of technology solutions available, including the technology of external service providers.
Purpose: To ensure that applications meet internal and external stakeholder needs, in terms of functionality, reliability, maintainability, compliance, and auditability.
The Reality: Surviving the Framework Trap
If you are looking closely at ITIL 5 and SVPG, your frustration is entirely justified. The corporate framework landscape has become a bloated, commercialized battleground where different methodologies are constantly rewriting the same basic concepts. When frameworks expand their scope to cover everything, they stop being helpful guidelines and start creating operational gridlock.
1. The Commercial Framework Trap
Frameworks like ITIL are no longer just public best practices; they are massive commercial businesses. To stay profitable, governing bodies must convince the market that their framework is still relevant in a product-driven, AI-centric world. Their solution is often to absorb Agile, DevOps, and SVPG product principles, slap an ITIL label on them, and sell them back to enterprises. The result is a confusing hybrid that borrows heavily from product management while trying to keep traditional IT managers happy.
2. Semantic Gymnastics
We have reached a point where different departments are doing the exact same work but using different dictionaries to describe it, forcing teams to spend more time translating words than building software:
The Real Goal
What SVPG Calls It
What ITIL 5 Calls It
What SAFe Calls It
Figure out if we should build it
Discovery (Value / Viability)
Discovery (Feasibility)
Epic Refinement / Lean UX
Can our tech actually handle it?
Feasibility Risk
Service Viability
Architectural Runway
Will it break corporate rules?
Business Viability
Governance & Compliance
Guardrails
3. How to Protect Your Teams
If you are trapped in an organization trying to roll out both models, the worst thing you can do is let them run as separate, redundant processes. To survive this mess, you must force a mapping strategy:
Declare SVPG as the Primary Engine
Keep your product teams firmly rooted in the SVPG Product Operating Model. Do not let them change their terminology or workflow to suit ITIL. SVPG drives the value.
Treat ITIL 5 as a Checklist, Not a Process
When ITIL auditors or enterprise ops managers ask to see your "ITIL Discovery" phase, do not build a separate one. Instead, show them your SVPG Discovery artifacts. Prove to them that Cagan’s Feasibility and Viability risk assessments already answered their operational and compliance questions.
Rebrand ITIL as "The NFR Input"
Force traditional IT and Operations staff to feed their specific constraints (Non-Functional Requirements like uptime, security compliance, deployment pipelines) directly into the SVPG Product Trio during regular discovery, rather than letting them act as a gatekeeper later in the lifecycle.
Ready to test your knowledge?
Switch to the Exam Simulator to prove your mastery of these official ITIL 5 concepts (Steps 1-6).
ITIL 5 Foundation Exam Simulator
Test your understanding of the official ITIL 5 framework (Sections 1-6 of this guide), including Digital Product Management, the 8-stage PSLM, and AI Governance. Passing score is 65%.
Question 1 of 20Score: 0
Question text here?
Quiz Complete!
0%
Wrap-up
My primary takeaway is that organizations really need to approach the various frameworks with a critical eye. You might have read my article on PRINCE2 and PRINCE2 Agile®. The same message.
Do not expect the various commercial players to ensure consistency in your framework landscape. That burden is on your shoulders!
