What is the ITIL Framework?

An Intro to ITIL 5

As an IT leader, having a solid understanding of the principles of ITIL is essential for developing and growing your organization’s operations. This framework provides an organized approach to service management that helps define and standardize processes related to technology infrastructure, applications, and, increasingly, the AI and automation layered on top of them.

ITIL just went through its biggest update since 2020. ITIL 5 launched in February 2026, and it’s not a cosmetic refresh — it reflects how organizations actually build and run digital products and services today, including how they govern AI. If your organization is standardizing on ITIL, or re-evaluating your ITSM platform against ITIL best practices, here’s what’s changed, what’s stayed the same, and what it means for how you should be thinking about AI in your service desk.

Defining ITIL – What is the ITIL framework?

ITIL is a collection of best practices intended to help organizations manage digital products and services more efficiently. These guidelines define a structured, value-focused approach to the management and continuous improvement of technology-enabled services.

One notable change in ITIL 5: the name no longer stands for “IT Infrastructure Library.” ITIL is now simply “ITIL” — described as a framework and best-practice guidance for digital product and service management. That’s more than a naming exercise. It reflects a shift from managing IT as a back-office function to managing digital products and services end to end, across IT, product, and business teams.

Interest in ITIL adoption continues to grow, and the framework has evolved accordingly: ITIL v3’s Service Lifecycle gave way to ITIL 4’s Service Value System in 2020, which focused on “value co-creation” with customers and treated ITIL more as an integration layer across other methodologies like Agile, DevOps, and project/portfolio management. ITIL 5 builds directly on that foundation rather than replacing it, with existing ITIL 4 knowledge, certifications, and practices carried forward.

From ITIL 4 to ITIL 5: What’s Actually Changed

ITIL 5 is described by its publishers as an evolution, not a reset. The core practices IT teams already know, including incident, change, problem, request management, and the rest, are still there. What’s changed is the structure around them:

• A unified Product and Service Lifecycle replaces the Service Value Chain. Instead of six value chain activities, ITIL 5 organizes work into an eight-stage lifecycle — Discover, Design, Acquire, Build, Transition, Operate, Deliver, and Support — that treats digital products and services as one continuous flow rather than separate disciplines. Early stages lean toward product thinking, later stages toward service thinking, and organizations combine the stages into value streams rather than following them in strict order.
• The Service Value System has been renamed and revised into a broader Value System that ties governance, guiding principles, value stream activities, management practices, and continual improvement together more explicitly.
• AI governance is built into the framework, not bolted on afterward — more on that below.
• New qualification pathways. In addition to ITIL Foundation (Version 5), there are updated core designations — ITIL Practice Manager, ITIL Managing Professional, ITIL Strategic Leader, and ITIL Master — plus a standalone AI Governance extension module with no prerequisites.
• ITIL 4 certifications remain valid. Anyone already ITIL 4-certified doesn’t need to start over. A Foundation Bridge exam covers the delta, and ITIL 4 credentials remain a valid prerequisite for advanced ITIL 5 modules. ITIL 4 is expected to phase out entirely in early 2027.

The ITIL 5 Product and Service Lifecycle

The old “five stages of ITIL” (Strategy, Design, Transition, Operation, and Continual Service Improvement) has effectively been superseded twice over: first by ITIL 4’s Service Value Chain, and now by ITIL 5’s Product and Service Lifecycle. Here’s the current model:

1. Discover — Identify business needs, demand signals, and opportunities, and align them to organizational strategy before committing resources.
2. Design — Translate validated needs into service specifications, architectures, and prototypes.
3. Acquire — Obtain the components needed to deliver — technology, people, suppliers, and cloud infrastructure, whether by buying, building, or hiring.
4. Build — Develop, configure, and test the solution.
5. Transition — Move the product or service into production safely, minimizing disruption.
6. Operate — Keep infrastructure and systems running, and monitor performance.
7. Deliver — Make the service available for consumption and manage access and requests.
8. Support — Resolve incidents and problems and restore normal service operation.

Like ITIL 4’s value chain, this isn’t a rigid sequence. Organizations combine these activities into value streams suited to their context. In an agile environment, Design, Build, and Acquire might run in tight, overlapping loops rather than one after another. The point isn’t to check off stages; it’s continual value co-creation between the organization and the people using its services.

ITIL 5 and AI: Governance Built In, Not Bolted On

The single biggest addition in ITIL 5 is direct guidance for AI. Generative and agentic AI are no longer treated as a future roadmap item — they’re addressed as current operational reality, with a dedicated (though optional) AI Governance extension module covering AI maturity models, risk and decision authority, data governance, and regulatory alignment. Unlike ITIL 5’s other qualification tracks, this module has no prerequisites, reflecting how broad the audience for AI governance has become — it’s no longer just an ITSM practitioner’s concern.

That timing lines up with what’s happening across the broader ITSM market. According to Gartner’s ITSM platforms market analysis from the 2026 Gartner® Magic Quadrant™ for IT Service Management (ITSM) Platforms, the market reached nearly $9 billion in 2025, growing almost 14% year over year, and it remains the largest segment of the IT operations value management market. AI is the dominant theme among vendors heading into 2026 — the industry has moved from basic machine learning and natural language processing toward generative and agentic AI, with vendors pursuing more autonomous ITSM and smarter, AI-assisted decision-making across the board.

But Gartner also flags a real risk in that shift: for some vendors, chasing more AI agents becomes a distraction from strengthening the underlying system of record — the ticketing, workflow, and data foundation that AI actually depends on. Core ITSM capabilities like ticket management have become table stakes, which is pushing some providers toward a “good enough, low-cost” positioning that’s easy to disrupt. At the same time, the market is seeing a wave of new entrants split into two camps: adjacent workflow vendors bolting service-desk functionality onto existing tools (mature ticketing, but years away from deep parity in change, configuration, and problem management), and self-described “AI-native” startups with fast-evolving AI agent libraries but comparatively immature core ITSM practice support.

Put together, ITIL 5’s shift toward AI governance and Gartner’s read on the market are describing the same problem from two different angles: AI is now assumed, not aspirational, and the organizations that benefit from it are the ones with a solid, unified operational foundation underneath it, not just a growing pile of point-solution AI agents bolted onto a fragmented stack.

What This Means for Your ITSM Platform

This is exactly the structural gap TeamDynamix was built to close. A lot of the legacy ITSM tools were built in an era when customization meant custom code, integration was a separate downstream project, and AI was a future roadmap item rather than part of the architecture. That’s the model Gartner is describing when it warns about AI investment outpacing system-of-record investment — and it’s the model that leaves IT teams maintaining the platform instead of the platform enabling the team.

TeamDynamix takes the opposite approach: a unified, no-code platform that brings IT Service Management, Enterprise Service Management, asset management, automation, and integration into one place, built on three structural differentiators:

• AI and automation are baked in, not bolted on. TeamDynamix delivers a fully managed AI platform — no API keys, no model infrastructure to maintain, no BYOK model to configure. TeamDynamix handles the ongoing evaluation, testing, and optimization of the underlying models so your team can focus on outcomes instead of AI operations — the same “system of record first” discipline Gartner points to as the differentiator that lasts.
• Integration is designed in, not a downstream project. The platform’s iPaaS layer gives AI and automation access to the full integration ecosystem from day one — hundreds of pre-built connectors, plus the ability to build new ones without code, extending well beyond the service desk (think Workday to Salesforce workflows). When it comes to critical capabilities, Gartner specifically calls out TeamDynamix for strength in automation and orchestration.
• No-code, so teams don’t outgrow the platform. Service management, HR, facilities, legal, and other departments can self-administer — custom forms, flows, and integrations — without pulling in developers or specialists for every change.

That structural difference is why TeamDynamix customers see results like 30–60% ticket deflection with AI and automation, 40–90% faster resolution with AI-powered triage and smart service, and two to three months’ worth of manual, repetitive work eliminated through automation — all while holding a 98% customer retention rate and a #1 ranking in the Info-Tech 2026 ITSM Data Quadrant enterprise category, six years running.

If you’re building your ITSM roadmap around ITIL 5 — whether that means training your team on the new AI Governance module or just making sure your platform can keep pace with where the framework and the market are both heading — the underlying question is the same one Gartner is asking vendors: is AI part of your architecture, or an add-on sitting on top of a fragile foundation?

Building a Strong ITSM Foundation with ITIL 5

Whether you’re new to ITIL or updating your practices for version 5, a few fundamentals still hold:

1. Categorize. Differentiate incidents from service requests so your team, and your AI, is working from a common vocabulary.
2. Triage. Establish clear criteria for urgency and escalation so resolution targets are realistic and consistent — this is also foundational to any AI governance framework, since automated triage decisions need the same clarity a human triager would apply.
3. Commit to service. The service desk is often the first point of contact for end users; a courteous, well-supported experience drives adoption and trust — including trust in AI-assisted interactions.
4. Be accountable. Use data, not assumptions, to guide improvement — and extend that discipline to AI: track model performance and drift the same way you’d track SLA compliance.

Want to learn more about ITIL? Read 4 ITIL Best Practices to Revive Your Service Management.

This blog was originally published in May 2020, previously updated in April 2025, and has been refreshed in August 2026 to reflect the launch of ITIL 5.