ITIL

What is ITIL?

ITIL is a globally adopted framework of best practices for delivering and managing IT services. It defines a common vocabulary, a set of practices, and a service value system that organizations use to align IT with business outcomes, control risk, and improve quality.

Originally the Information Technology Infrastructure Library, now stylized simply as ITIL.

Why ITIL matters

Most enterprise IT organizations run thousands of changes, incidents, and service requests per month across dozens of tools and teams. Without a shared playbook, that work fragments. Definitions of severity drift between teams, change records skip review, and post-incident learning never reaches the people who need it. ITIL gives IT a common language and a structured way of working that scales beyond a single team or platform.

ITIL also matters for compliance and audit. Auditors expect to see defined processes for change, access, and incident handling, with evidence that those processes are followed. ITIL-aligned practices map cleanly to frameworks such as SOX, ISO 20000, and SOC 2, which is part of why it is the default operating model in regulated industries.

Adopted well, ITIL is a backbone for service quality and risk control. Adopted badly, it becomes a paperwork tax. The modern emphasis on lean, value-stream-oriented ITIL 4 is a direct response to that risk.

A brief history

ITIL originated in the late 1980s with the UK’s Central Computer and Telecommunications Agency. It evolved through several major versions, with two still relevant today:

ITIL v3 (2007, refreshed 2011): Organized around a five-stage service lifecycle: strategy, design, transition, operation, and continual service improvement. Dozens of processes were defined within those stages.
ITIL 4 (2019, ongoing updates): Reframes ITIL around a service value system, 34 management practices, and four dimensions of service management. It is designed to coexist with Agile, DevOps, and Lean ways of working.

The ITIL 4 service value system

ITIL 4 centers on the service value system (SVS), which describes how an organization turns demand and opportunity into value. Its core components are:

Guiding principles: Seven principles such as focus on value, start where you are, and progress iteratively with feedback.
Governance: How the organization is directed and controlled.
Service value chain: Six interconnected activities (plan, improve, engage, design and transition, obtain/build, deliver and support) that produce value.
Management practices: 34 practices including incident management, problem management, change enablement, service request management, and monitoring and event management.
Continual improvement: An always-on practice for raising service quality, cost efficiency, and customer experience.

ITIL v3 vs. ITIL 4

ITIL 4 is not a wholesale rewrite of ITIL v3, but the shift in orientation is real. v3 was lifecycle- and process-heavy; ITIL 4 is value-stream- and outcome-oriented, with explicit hooks for Agile, DevOps, and automation.

Dimension	ITIL v3	ITIL 4
Organizing model	Five-stage service lifecycle	Service value system and service value chain
Unit of work	Processes	Practices
Relationship to Agile/DevOps	Limited, often perceived as in tension	Designed to coexist and reinforce
Emphasis	Repeatability and control	Value, outcomes, and continual improvement

ITIL use cases in IT operations

Incident management: Standardized severity definitions, response targets, and escalation paths across the NOC, service desk, and on-call engineering teams.
Change enablement: Categorizing changes as standard, normal, or emergency, with appropriate review and approval for each path.
Problem management: Investigating recurring incidents, recording known errors, and feeding fixes back into change enablement.
Service request management: Defining a catalog of pre-approved requests with predictable lead times and ownership.
Monitoring and event management: Treating alerts and events as inputs to a managed practice, which is where AIOps and event correlation plug into ITIL 4.

Common misconceptions

ITIL is not a standard, and there is no “ITIL certification” for an organization. Individuals are certified; organizations adopt and adapt the framework. ITIL is also not prescriptive: ITIL 4 explicitly tells teams to take what is useful and skip what is not, which is a meaningful change from the more dogmatic interpretations of ITIL v3.

Frequently asked questions about ITIL

Is ITIL the same as ITSM?

No. ITSM is the discipline of managing IT services; ITIL is a framework of best practices for doing ITSM. You can practice ITSM without ITIL, but ITIL is by far the most commonly adopted framework that informs ITSM programs.

What is the difference between ITIL v3 and ITIL 4?

ITIL v3 organizes IT service management around a five-stage service lifecycle and a long list of processes. ITIL 4 reorganizes the same territory around a service value system, 34 management practices, and four dimensions of service management, and it is explicitly compatible with Agile, DevOps, and Lean.

Does ITIL conflict with DevOps and Agile?

Not in ITIL 4. Earlier interpretations of ITIL v3 sometimes felt at odds with Agile and DevOps because of heavy process and approval overhead. ITIL 4 was designed to coexist with those ways of working, emphasizing flow, automation, and continual improvement.

Is ITIL still relevant?

Yes. ITIL remains the most widely adopted framework for IT service management, particularly in regulated industries and large enterprises. The shift to ITIL 4 has kept it relevant alongside DevOps, SRE, and AIOps adoption.

What are the main ITIL certifications?

ITIL 4 has a tiered certification scheme: Foundation, then specialist and strategist modules, then Managing Professional, Strategic Leader, and Master. Foundation is by far the most commonly held certification and is often required for IT service management roles.

How does AIOps fit with ITIL?

AIOps maps directly to ITIL 4’s monitoring and event management practice and supports incident, problem, and change enablement practices. It reduces alert noise, accelerates incident detection, and feeds higher-quality incidents and change risk signals into ITIL-aligned workflows.