ITIL
ITIL is a framework of practices for managing IT services that began as British government guidance in the 1980s and now describes service management in terms of value, and you can use it as a source of tested ideas without adopting all of it.
Why this matters
ITIL is the most widely recognised name in IT service management (ITSM). Job advertisements list its certifications, auditors ask whether you "follow ITIL," and many organisations organise their service desks around its vocabulary. A team that works in an agile way will meet ITIL sooner or later, often as a set of forms and approvals that seem to belong to another era. Knowing what ITIL actually is, where it came from, and what it claims helps you separate the useful ideas from the baggage.
ITIL also changed. The framework you may remember, with a lifecycle of service strategy, design, transition, operation, and improvement, was replaced in 2019 by ITIL 4, which was written to align with agile, DevOps, and lean ways of working. In 2026 the owner announced another version, called ITIL 5. A guide that treated ITIL as fixed would mislead you, and one that treated every version as equal would too.
This topic describes ITIL's history, ownership, versions, and certification, drawing on the Wikipedia article on ITIL and on the framework owner's public pages. It is careful about dates and about what the public sources actually say. The details of how ITIL 4 works begin with Topic 2.3 — The ITIL Service Value System.
Core concepts
What ITIL is
ITIL, the Information Technology Infrastructure Library, is according to Wikipedia a framework of practices for IT activities such as ITSM and IT asset management, with the aim of aligning IT services with business needs. It is a source of guidance. It is not a standard against which an organisation is certified. Wikipedia states that certification in ITIL is available only to individuals and not to organisations, and that no formal independent third-party assessment exists to show that an organisation complies with ITIL. The related standard that organisations can be certified against is ISO/IEC 20000 (see Topic 2.7 — ITSM Frameworks and Standards).
Where it came from
Wikipedia says the UK government's Central Computer and Telecommunications Agency (CCTA) developed the recommendations in the 1980s to standardise the management of government IT, and links the process-model approach to the work of W. Edwards Deming and the plan-do-check-act cycle. This origin matters: ITIL was written for large, stable organisations running shared infrastructure, a context in which change was expensive and outages were visible. Some of its assumptions look dated in a world of cloud services and daily releases.
Versions and dates
The dates below follow the Wikipedia article. Where the article is silent, this topic is silent.
| Date | Event |
|---|---|
| 1989 | ITIL released as a series of 30 books |
| 1993 | EXIN developed the first ITIL certification scheme |
| 2001 | ITIL version 2 released |
| May 2007 | ITIL version 3 released, with 26 processes and functions grouped into five volumes (also called the 2007 edition) |
| 2009 | The Office of Government Commerce (OGC) announced that ITIL v2 certification would be withdrawn |
| July 2011 | ITIL 2011 edition released |
| February 2019 | ITIL 4 released; version numbering was simplified, and the article says it aligned with Agile, DevOps, and Lean and shifted emphasis from IT service management to general service management |
| January 2026 | PeopleCert announced ITIL 5 |
The article gives no release date for a first version of ITIL, so none is given here.
Who owns it
Wikipedia traces ownership as follows. The CCTA originated ITIL. In April 2001 the CCTA merged into the Office of Government Commerce, an office of the UK Treasury. In 2013 ITIL was acquired by AXELOS, a joint venture between Capita and the UK Cabinet Office. PeopleCert completed its acquisition of AXELOS in June 2021 and has owned the ITIL trademark since 2021. The name ITIL is a registered trademark; this guide uses it accurately and does not imply endorsement by its owner.
ITIL 4 in outline
ITIL 4, released in 2019, is described in the next topics, from Topic 2.3 — The ITIL Service Value System onward. In outline, it has:
- a service value system (SVS), the model of how an organisation's parts work together to create value;
- four dimensions of service management, which PeopleCert's ITIL 4 Foundation page lists as organisations and people, information and technology, partners and suppliers, and value streams and processes;
- seven guiding principles, which Wikipedia lists as focus on value; start where you are; progress iteratively with feedback; collaborate and promote visibility; think and work holistically; keep it simple and practical; and optimise and automate;
- a service value chain of activities, which widely used summaries from training providers list as plan, improve, engage, design and transition, obtain/build, and deliver and support;
- a set of practices, which Wikipedia counts as 34, divided into 22 product and service management practices and 12 general management practices.
One caution. Wikipedia places the guiding principles and the practice count under its ITIL 5 section. They match the published structure of ITIL 4 as widely described, and this guide treats them as ITIL 4 concepts. Check against the owner's current publications before you rely on the numbers.
ITIL 5
Wikipedia reports that PeopleCert announced ITIL 5 in January 2026. PeopleCert's certification page, as read for this guide, says "The new ITIL is here!" and describes it as "Practical and AI-native by design." It lists ITIL Foundation (Version 5), ITIL Product (Version 5), ITIL Service (Version 5), and an ITIL AI Governance (Version 5) module. It still lists ITIL 4 courses and offers an upgrade route for ITIL 4 certified professionals. The page does not give a release date or say whether ITIL 4 certifications are retired.
That is all this guide can state from the owner's public pages. Practice material in Parts 2 and 3 therefore rests on ITIL 4 concepts, and it mentions ITIL 5 only where an owner source supports it. If you work with ITIL 5 material, read the new publications directly.
Certification
Wikipedia describes the ITIL 4 path as starting with ITIL 4 Foundation and then branching into two tracks: Managing Professional, with four specialist modules, and Strategic Leader, with two. PeopleCert's page now organises certifications by version (ITIL 4 or ITIL Version 5) and by qualification paths. Certifications show that a person has studied the material; they do not by themselves show that an organisation runs services well. Prices and the exact catalog change, so check the owner's page for current details (see Topic 6.4 — Learning Paths and Certification).
What ITIL is not
ITIL is not a standard you can pass or fail, a methodology you must follow in full, or a set of rules that audits enforce on their own. The Wikipedia article names no criticisms, but practitioners often raise familiar ones: that implementations drift into paperwork, that earlier versions assumed slow change, and that certification can become the goal. Where those concerns are real in your organisation, the remedy is to adapt ITIL's ideas, which the framework itself encourages through principles such as "start where you are" and "keep it simple and practical."
Best practices
- Treat ITIL as a library of ideas. Read it for practices that fit a problem you have, and take what helps. The framework is guidance, and it is not a compliance regime you can fail.
- Know which version people mean. When colleagues, vendors, or auditors say "ITIL," ask whether they mean ITIL v3, ITIL 4, or ITIL 5. Practices, vocabulary, and certification differ, and misunderstandings are common.
- Check the owner's current publications. Dates, certification paths, and product names change. Read the framework owner's pages for the current state and do not rely on training-provider summaries alone, including this guide's.
- Start where you are. Map the practices you already follow before you add any. Many agile teams already do incident handling, release, and knowledge sharing without using ITIL's names, and the names can be added later.
- Adopt vocabulary before process. Shared terms such as incident, problem, change, and service request help teams talk to operations, audit, and customers. Introduce them first and add formal steps only where a pain justifies them.
- Use ITIL 4's guiding principles for your own decisions. They are short and broadly agile-compatible, and can serve as a checklist for any process. Test a proposed process against "keep it simple and practical" and "progress iteratively with feedback."
- Separate framework use from certification. Training your people in ITIL is useful, but certificates do not prove that your services are well run. Measure outcomes such as time to restore service and customer satisfaction.
- Pair ITIL with ISO/IEC 20000 only when you need external certification. If a customer or regulator demands a certified service management system, the ISO/IEC standard is the route. Otherwise ITIL guidance is enough (see Topic 2.7 — ITSM Frameworks and Standards).
- Be honest in what you claim. Say "we use ideas from ITIL 4" if that is true. Claiming compliance with a framework that has no organisational certification invites trouble with auditors and customers.
- Adapt older practices to faster change. If your organisation still uses processes from ITIL v2 or v3, review them against current delivery speed, and replace long approvals with lighter checks that meet the same purpose (see Topic 3.4 — Change Enablement).
- Involve the delivery teams in any ITIL work. If a service management group designs processes alone, delivery teams will work around them. Include them from the start and test processes with a pilot.
- Watch for new versions without rushing. When a new version is announced, read what the owner publishes, note what changed, and decide what is worth adopting. Do not restructure services to match a new version without a reason.
Questions to discuss with your team
What do we mean when we say "ITIL," and does everyone mean the same thing?
Ask each person to describe ITIL in a sentence and to name the version they know. Differences are common: someone remembers the v3 lifecycle, someone has the ITIL 4 Foundation certificate, someone only knows the ticket tool. Write down the shared meaning. The facilitator can ask what each version suggests about how fast the organisation should change.
Which ITIL ideas do we already use without the name?
List the practices the team follows: handling incidents, recording changes, keeping a knowledge base. Match them to ITIL practices. Many teams are surprised at how much they do. Ask which of those are written down and which live in people's heads. Choose one to record.
Where has ITIL, or something called ITIL, helped us, and where has it hurt?
Collect stories of both. Helpful stories are usually about shared vocabulary and avoiding repeat mistakes. Harmful stories are usually about slow approvals and forms. Ask what separated the two kinds. Often it is whether the process had a clear purpose and an owner who could change it. Agree on one thing to keep and one to change.
What do our customers, auditors, or suppliers expect from us when it comes to ITIL?
Ask people who deal with these groups what is asked. Sometimes the expectation is a certified management system, sometimes only ITIL vocabulary. Clarifying the expectation avoids over-investing. Note that organisational certification against ITIL does not exist, so ask what evidence the other party would actually accept.
Does our certification or training plan match the problems we have?
Look at who holds which certificates and what problems the team faces. Courses help when they are tied to a task. Ask whether the money would do more good elsewhere, such as in tooling or time to improve. Discuss without judgment about individuals' paths. Choose one learning goal that connects to a team problem.
How should we respond to a new version of ITIL?
Ask who is responsible for following the owner's announcements, and what would trigger a change. A sensible rule is to read the new material, list what it changes for the team, and decide on a small experiment. Avoid committing to a wholesale change before the practice is understood. The facilitator can ask what could go wrong if the team moved too early or too late.
In practice: an agile ITIL example
A mid-sized regional bank has an IT operations department of forty people. Its processes were written ten years ago from ITIL v3, with a weekly change advisory board, a long incident form, and a separate problem record for every repeat outage. Delivery teams, who now release most applications every two weeks, complain that the change board is slow and the forms are redundant. Operations staff reply that the forms exist because past outages cost the bank money and a regulatory warning.
The head of service management sets up a working group with two delivery team leads and two operations managers. They begin by listing the purpose of each form and approval, using the question "what does this protect against?" Several turn out to have no clear purpose. They then read ITIL 4's guiding principles and test their processes against two of them: "keep it simple and practical" and "progress iteratively with feedback." The group trims the incident form from 22 fields to nine, replaces the weekly change board for low-risk, well-tested changes with automatic recording, and keeps the board for high-risk changes.
Six months later, changes flow faster and the bank's internal audit finds the evidence for low-risk changes sufficient. Not everything is solved. Some staff still ask for the old form, and a supplier contract written around the old processes requires changes the bank cannot make quickly. Meanwhile the head of service management notices that the bank's training budget still goes entirely to ITIL v3 certificates, which no longer match the practice. She commissions a review of the training plan, and tells staff that the bank uses ideas from ITIL 4 and does not claim compliance with any version.
Four perspectives
Product and delivery teams
Delivery teams can use ITIL as a checklist of things operations care about: how a service is monitored, supported, and changed. Learn the vocabulary and propose lighter ways to meet the same purposes. When someone says "ITIL requires it," ask which version, which practice, and what it protects against.
Service and operations teams
Operations teams are often the carriers of ITIL knowledge. Share the reasons behind your processes, and be ready to simplify. Check that your practice reflects the current version of ITIL where you claim to follow it. Use ITIL's own principles to argue for iterative improvement over big redesigns.
Leadership and governance
Leaders decide how ITIL is used. Avoid treating it as a compliance badge. Ask for outcomes, not certificates. If an external party needs a certified management system, use ISO/IEC 20000 and understand its scope. Keep the training plan aligned with current practice and with the problems the organisation has.
Customers and users
Customers and users rarely care which version of ITIL a provider follows. They care that incidents are handled well, requests are answered, and changes do not break things. Ask providers what they do about those outcomes, and not which framework they cite.
Common failure modes
- Treating ITIL as a standard to pass. Teams chase compliance with a framework that has no organisational certification. Instead, state which ideas you use and measure outcomes.
- Confusing versions. Processes from v3 are defended as "ITIL" against ITIL 4's guidance. Instead, ask which version is meant and read the current publication.
- Implementing everything. Teams build every practice before they have a need. Instead, start with the pains and add practices when the problems justify them.
- Certificate as goal. Training spend replaces improvement work. Instead, tie learning to a problem and measure what changes in the work.
- Process without purpose. Forms and approvals remain because they are in the process. Instead, ask what each protects against and delete those that protect nothing.
- Relying on training summaries. Blog posts and course notes state details with confidence, and some are wrong or out of date. Instead, read the owner's publications and cite them.
- Assuming a new version solves old problems. A new version arrives and teams hope it fixes culture. Instead, read what changed and run a small experiment.
- Excluding delivery teams. Service management designs processes alone. Instead, build with delivery and operations together and test with a pilot.
Maturity model
| Dimension | Initiate | Develop | Standardize | Manage | Orchestrate |
|---|---|---|---|---|---|
| Understanding of ITIL | Staff know the name and little else | Some people are trained and use ITIL vocabulary | Teams share a stated reading of which ITIL ideas they use and which version | Use of ITIL ideas is reviewed against outcomes | Teams, suppliers, and customers use a common vocabulary and review it together |
| Adaptation of practice | Processes are inherited and unchanged | Some teams simplify processes locally | Each practice has an owner and a route for change | Process friction and outcomes are measured | Practices are adapted across teams based on shared evidence |
| Claims and evidence | Compliance is claimed loosely | Some claims are checked | Claims are accurate and backed by records | Evidence is reviewed with auditors and customers | Evidence is shared and trusted across partners |
| Learning and certification | Training is ad hoc | Some staff are certified | Training is planned against team problems | Training effects on work are reviewed | Learning is coordinated across teams and suppliers and updated with new versions |
Checklist
- The team can say which ITIL version its colleagues, vendors, and auditors mean.
- We know which ITIL ideas we use and which we have left out, and why.
- Our claims about ITIL are accurate and do not suggest an organisational certification that does not exist.
- Each process has a stated purpose and an owner who can change it.
- Delivery and operations staff both take part in designing service management processes.
- We read the framework owner's current publications, not only training summaries.
- Our training plan is tied to the team's actual problems.
- We know whether any customer or regulator requires ISO/IEC 20000 or another certified standard.
- We have a named person who follows announcements from the ITIL owner.
- Processes inherited from older versions have been reviewed against current delivery speed.
AI prompts
Purpose: find out which version of ITIL your processes were based on.
Help me work out which version of ITIL my organisation's processes seem to be based on.
Here are descriptions of our processes (names of processes, roles, forms, meetings, and the vocabulary we use): [paste a list].
Here are notes I have from the ITIL owner's public pages for each version I am comparing: [paste only the text you have read from official pages or publications].
Using only the pasted notes, say which version each process appears to follow, quote the words you based that on, and list processes where you cannot tell. Do not add facts about ITIL versions from memory. Ask me clarifying questions first, and list what you are unsure of.
Purpose: ask "what does this protect against?" for each process step.
Here is a process we use: [paste the steps, forms, approvals, and who does each].
For each step, answer: (1) what risk or purpose it may serve, (2) who benefits, (3) what evidence shows it works, using only the text I gave you, and (4) a lighter alternative that could meet the same purpose. Mark every point where you are guessing. Do not claim any standard or regulation requires a step unless I have pasted its text: [paste any rule text, or write "none known"]. Ask clarifying questions first, and list what you are unsure of.
Purpose: prepare a short briefing on ITIL for a team of developers.
Write a one-page briefing on ITIL for a team of [number] developers who run what they build.
Use only these notes, which I have read from sources: [paste notes, such as the history and versions you verified, ITIL 4 guiding principles, and the fact that organisations cannot be certified against ITIL].
Include: what ITIL is and is not, three ideas that suit our team, and three questions to ask operations. Keep it neutral about agile and ITIL. Do not add dates or claims that are not in my notes. Mark assumptions, and list what you are unsure of.
Purpose: plan how to respond to a new version of ITIL.
A new version of ITIL has been announced. Here is what the framework owner's public pages say, copied by me: [paste the text].
Our current practice: [describe in a few sentences which ITIL-based practices we use].
Using only the pasted text, list what appears to have changed that might affect us, what the text does not say, and questions to ask the owner or a training provider. Propose a small experiment we could run in one quarter. Do not guess about content not in the text. Ask clarifying questions first, and list what you are unsure of.
AI skills
- service-level-agreement: use to turn ITIL's idea of agreed service levels into a plain agreement customers can understand.
- change-request: use to draft change records that carry the information operations and auditors need.
- incident-response-plan: use to set out how your team responds to incidents, in line with the practice you choose.
- configuration-management: use to plan how you record the parts of your services and how they relate.
- kaizen: use to turn ITIL's continual improvement idea into small, regular changes.
Key sources
- ITIL (Wikipedia): the history, ownership, versions, and certification of the framework, with citations.
- ITIL certifications (PeopleCert): the current owner's public catalog of ITIL 4 and ITIL Version 5 certifications; check it for the present state.
- ITIL 4 Foundation (PeopleCert): the owner's summary of what the Foundation level covers, including the four dimensions.
- IT service management (Wikipedia): context on where ITIL sits among ITSM frameworks and standards.
References
- ITIL — Wikipedia — https://en.wikipedia.org/wiki/ITIL
- IT service management — Wikipedia — https://en.wikipedia.org/wiki/IT_service_management
- ITIL certifications — PeopleCert — https://www.peoplecert.org/browse-certifications/it-governance-and-service-management/ITIL-1
- ITIL 4 Foundation — PeopleCert — https://www.peoplecert.org/browse-certifications/it-governance-and-service-management/ITIL-1/itil-4-foundation-2565
- ISO/IEC 20000 — Wikipedia — https://en.wikipedia.org/wiki/ISO/IEC_20000
- IT asset management — Wikipedia — https://en.wikipedia.org/wiki/IT_asset_management
- W. Edwards Deming — Wikipedia — https://en.wikipedia.org/wiki/W._Edwards_Deming
- PDCA — Wikipedia — https://en.wikipedia.org/wiki/PDCA