ITIL Framework: IT Service Management Practices Explained

By Linh Ngo · Updated Oct 12, 2026

ITIL is a library of guidance on how to design, deliver, and improve IT-enabled services so they create value for the business. It isn't a standard you certify your company against. It's a shared vocabulary and a set of practices, such as incident, change, and service level management, that you adapt to your own situation.

What is the ITIL framework?

ITIL, once short for Information Technology Infrastructure Library, is the best-known framework for IT service management (ITSM). Today PeopleCert provides the ITIL qualification scheme and describes ITIL as the global best practice framework for digital product and service management. On the same page PeopleCert reports more than 3 million ITIL certifications worldwide, and says 90% of organizations report using ITIL practices in some capacity. Treat that second number as the owner's own claim, not independent research.

The core idea is simple. IT doesn't exist to run servers. It exists to help people do their jobs, serve customers, and reach business goals. ITIL organizes the work around that idea of value, and it replaces a rigid process list with flexible practices you combine as needed.

If you've read about business process management, you'll recognize the logic. ITIL applies the same discipline of defined, measured, improvable work to one domain: technology services. The difference is that ITIL gives you ready-made names and purposes for the work, so a service desk in Manila and one in Munich can talk about "incidents" and "changes" and mean the same thing.

ITIL 4 and the newer ITIL Version 5

Two editions are in play right now, so it's worth being precise.

ITIL 4 launched in 2019, with separate guidance for 34 management practices. PeopleCert has since introduced ITIL (Version 5), which it describes as not a reset and which is being released in phases. PeopleCert also states that ITIL 4 remains available for people who want to continue their current certification path.

The Version 5 Foundation guide says the new edition is built on ITIL 4's core concepts, including the guiding principles and the service value system. Its main addition is a lifecycle model of eight activities: Discover, Design, Acquire, Build, Transition, Operate, Deliver, and Support.

So what should you learn first? Most teams still work from ITIL 4 vocabulary, and Version 5 carries those concepts forward. The sections below describe ITIL 4. If you're planning training or exams, check which edition the course covers before you book it.

The ITIL 4 service value system

The service value system (SVS) is the big picture. PeopleCert describes it as a framework for creating, delivering, and managing services, including the service value chain, the guiding principles, and governance. It also includes practices and continual improvement, all aimed at producing value.

Here's what goes in the system.

Key Facts

• ITIL 4 launched in 2019 and defines 34 management practices (PeopleCert).
• The ITIL 4 service value system includes guiding principles, governance, the service value chain, practices, and continual improvement (PeopleCert).
• ITIL (Version 5) is built on ITIL 4's guiding principles and service value system, and adds an eight-activity lifecycle model (ITIL.com).
• PeopleCert says ITIL 4 stays available while Version 5 is released in phases (PeopleCert).

The four dimensions

PeopleCert names four dimensions of service management: organizations and people, information and technology, partners and suppliers, and value streams and processes. The point is to stop you optimizing one at the expense of the others. A shiny monitoring tool (information and technology) won't help if nobody is trained or assigned to act on its alerts (organizations and people).

The seven guiding principles

The principles are short enough to remember, which is why teams actually use them. As commonly listed for ITIL 4, they are:

1. Focus on value
2. Start where you are
3. Progress iteratively with feedback
4. Collaborate and promote visibility
5. Think and work holistically
6. Keep it simple and practical
7. Optimize and automate

"Start where you are" is the one people skip. Before you design a new incident process, look at what your team already does well. You'll often keep more than you replace.

The service value chain

The chain has six activities, per the same guide: Plan, Improve, Engage, Design and transition, Obtain or build, and Deliver and support. They aren't a fixed sequence. You link them into value streams depending on the work. A password reset might touch only Engage and Deliver and support. A new customer portal might use all six.

The 34 ITIL 4 practices

ITIL 4 groups its practices into three categories: 14 general management, 17 service management, and 3 technical management. You don't need to adopt all 34. Most organizations start with a handful.

Service level management is where ITIL meets contract language. If you need to define targets, read what an SLA is and browse SLA examples and templates.

ITIL vs. COBIT, ISO/IEC 20000, DevOps, and TQM

These frameworks overlap, and teams often use several at once. The key is knowing what job each one does.

On COBIT, ISACA calls it a framework for the governance and management of enterprise IT, with COBIT 2019 as the current version and an evolution of COBIT 5. Think of COBIT as the layer that asks whether IT is governed well, and ITIL as the layer that describes how services get delivered day to day. They pair naturally.

On ISO/IEC 20000, ISO describes ISO/IEC 20000-1 as setting requirements for an organization to establish, implement, maintain, and continually improve a service management system, covering planning, design, transition, delivery, and improvement of services. It's a standard you can be assessed against, while ITIL is guidance. A common pattern is to use ITIL to build the practices and ISO/IEC 20000 to prove them to an auditor or a customer. For a sibling in the quality world, see ISO 9001.

On DevOps, the two aren't rivals. DevOps focuses on collaboration between development and operations and on automating delivery. ITIL supplies the service side: how requests, incidents, and changes are handled once software is live. Lean thinking sits behind both, and our guide to Lean Six Sigma covers the waste-reduction roots.

On TQM, the philosophy that quality is everyone's job fits ITIL's continual improvement thread. See total quality management for the background.

How to adopt ITIL step by step

You don't roll ITIL out like a software release. You adopt it practice by practice, driven by real pain.

1. Name the pain. List the top three service problems: slow incident response, failed changes, or unclear ownership. Use real tickets, not opinions.
2. Map your current state. Following "start where you are," write down how each problem is handled today and by whom. Use a standard operating procedure format if nothing is documented.
3. Choose one or two practices. Incident management and service desk are the usual first picks. Don't start with six.
4. Define roles and a simple workflow. Who logs, who owns, who escalates, who closes. Keep it to one page.
5. Set measures before you start. Pick a few indicators such as time to resolve and reopen rate. The article on process KPIs helps you choose.
6. Run it for a quarter. Use your ticketing tool, hold a short weekly review, and adjust.
7. Improve and extend. Review results, fix what hurts, then add the next practice. Judge progress against a ladder like process maturity levels, which echoes the capability maturity model.

ITIL practice planning template

Copy this table for each practice you plan to adopt.

ITIL examples by business function

These are illustrative scenarios, not case studies. The pattern is the same everywhere: someone needs a service, the service has an owner, and the work is measured.

Do's and don'ts

Do:

• Start with one or two practices tied to a visible pain point.
• Treat the guiding principles as decision tools, especially "start where you are."
• Keep workflows to a page and train people on the roles, not just the tool.
• Measure outcomes the business feels, like downtime and wait time, not only ticket counts.
• Use continual improvement as a routine, with a named owner and a regular review.

Don't:

• Try to implement all 34 practices at once.
• Buy a tool and call it ITIL. The tool supports the practice; it isn't the practice.
• Copy another company's process wholesale without testing it.
• Confuse a certified person with a compliant organization. ITIL certifies people.
• Let change approvals become a bottleneck for low-risk, routine work.

Conclusion

ITIL's value is common language plus practical habits. It helps IT teams and the business agree on what a service is, who owns it, and how it gets better. Start small, pick the practices that fix real problems, and keep the seven guiding principles within reach. When you're ready to prove your setup to others, ISO/IEC 20000 and COBIT sit alongside it rather than against it.

Related reading

• Business process management
• What is an SLA?
• ISO 9001
• APQC Process Classification Framework
• Process KPIs
• Process maturity levels