What Is ITIL? Framework, Benefits and Version 5

Every few months, a new client asks me some version of the same question. Sometimes it comes from a CFO who just signed off on a service desk platform and keeps hearing the word in vendor meetings. Other times, it comes from an IT manager who inherited a team where tickets disappear into a black hole and nobody can say who owns what. Although the question is phrased a little differently each time, it boils down to this: what is ITIL, and do we actually need it?

I have spent most of my career as an ITIL and ITSM consultant, walking into organizations at the moment their technology stopped being a support function and started being the business itself. Along the way, I have seen ITIL rescue chaotic service desks. However, I have also seen it turned into a bureaucratic monster that slowed everyone down. In both cases, the guidance was the same. The difference, in fact, was how people understood it.

So let me explain it the way I would across a conference table, without the slide deck jargon.

What Is ITIL, in Plain Terms?

Put simply, ITIL is a body of guidance on how to manage technology services so they consistently deliver value to the people who depend on them. The name originally stood for Information Technology Infrastructure Library, and the word “library” is a good clue to its character. In other words, it was never a piece of software, a law, or a rigid standard you get audited against. Instead, it is a collection of proven practices, written down so organizations don’t have to learn every lesson the hard way.

When someone asks me what ITIL is, I usually say it is the closest thing our industry has to a shared operating manual. For example, it gives a service desk analyst in Manila, a change manager in Chicago, and a CIO in London a common language. As a result, when all three say “incident,” “problem,” or “change,” they mean the same thing. That alone resolves more confusion than most people expect.

It’s also worth clearing up a common misunderstanding early. You cannot certify a company as ITIL compliant. Only individuals can earn ITIL certification, and there is no formal third party certification for organizations. Therefore, if a vendor tells you their product makes your company certified, that’s marketing talking. Organizations adopt and adapt the guidance, while people get certified in it.

Where the Framework Came From

Understanding the origin story helps explain why ITIL looks the way it does. Originally, it was developed in the 1980s by the UK Government’s Central Computer and Telecommunications Agency, known as the CCTA, as a way to standardize IT practices across departments. At the time, the British government was spending heavily on computing and getting inconsistent, expensive results. So rather than reinvent the wheel in every department, they documented what was working.

Not surprisingly, that first edition was enormous. It ran to around 30 books, and anyone who studied the early material will tell you it read like a set of engineering manuals. Over the following decades, the library was consolidated and modernized several times. ITIL Version 2, for instance, tightened the content around service support and service delivery. Later, Version 3, released in 2007 and refreshed in 2011, introduced the famous service lifecycle of strategy, design, transition, operation, and continual improvement.

Meanwhile, ownership changed along the way too. In 2013, AXELOS was formed as a joint venture between the UK Cabinet Office and Capita to take over ITIL. Then, in June 2021, PeopleCert completed its acquisition of AXELOS, which is why PeopleCert is the name on certificates today.

Of course, the point of this history isn’t trivia. ITIL was born out of a practical need to stop wasting money and frustrating users. Consequently, when an implementation loses sight of that purpose, it stops being true to the original spirit, regardless of how many process diagrams sit on the shared drive.

Why ITIL Still Matters to Businesses Today

Most of my work is with business and professional services firms, such as consultancies, accounting practices, agencies, staffing companies, and managed service providers. Interestingly, none of them think of themselves as technology companies. Even so, every one of them would grind to a halt within an hour if their email, document systems, client portals, or billing platforms went down.

That, above all, is the reason ITIL keeps showing up in boardroom conversations. Once technology carries revenue, how you manage it becomes a business discipline rather than an IT hobby. In turn, the guidance gives leadership a way to ask sensible questions. How quickly do we restore service when something breaks? Who decides whether a risky change goes ahead on a Friday afternoon? Why do the same problems keep returning? Similarly, are we spending on the services our clients actually value?

To give you an example, one professional services firm I advised had a habit that is more common than you’d think. Every outage was handled heroically by the same two senior engineers, who would drop everything, fix the issue, and go back to their projects. Unfortunately, nobody recorded what happened. Six months later, the same outage would occur and the same heroes would scramble again. Introducing basic incident and problem management, two cornerstones of ITIL, didn’t require new software. Instead, it required writing things down, assigning ownership, and looking for root causes. As a result, repeat incidents dropped noticeably within a quarter, and those two engineers finally got their evenings back.

That, in short, is ITIL at its best. It isn’t paperwork; rather, it’s organizational memory.

The Core Building Blocks of ITIL 4

Since most organizations I meet today are running on ITIL 4 concepts, it’s worth walking through the main pieces. After all, if you understand these, you understand the heart of the framework.

The Service Value System

To begin with, ITIL 4 shifted the thinking from a sequence of lifecycle stages to a system. The service value system sits at the center of this version, showing how the different parts and activities of an organization work together to create value.

Specifically, the system has five components: guiding principles, governance, service value chain, management practices, and continual improvement. I like to describe it as the plumbing that connects demand on one side with value on the other. First, a client or user needs something. Next, the organization uses its principles, governance, activities, and practices to turn that need into a useful outcome. Finally, it learns from the experience and gets better.

The Seven ITIL Guiding Principles

If I could only teach a client one part of ITIL, it would be the guiding principles. That’s because they are short, memorable, and apply to almost any decision you’ll ever make about services. They are:

Focus on value
Start where you are
Progress iteratively with feedback
Collaborate and promote visibility
Think and work holistically
Keep it simple and practical
Optimize and automate

In fact, these principles have a longer pedigree than many realize. They first appeared in the 2016 ITIL Practitioner guidance, where there were originally nine rather than seven.

In my experience, “start where you are” and “keep it simple and practical” save more projects than any other advice in the framework. For instance, I’ve watched organizations try to throw out everything and build a perfect process model from scratch. Inevitably, they spend a year designing and never launch. By contrast, the teams that succeed look at what already works, keep it, and then improve one piece at a time.

The Four Dimensions

In addition, this version asks you to look at every service through four dimensions: organizations and people, information and technology, partners and suppliers, and value streams and processes. This acts as a guardrail against a mistake I see constantly, namely treating a tool purchase as a transformation. After all, a brilliant ticketing platform won’t help if roles are unclear, suppliers aren’t held to agreed service levels, or the workflow doesn’t match how the business actually operates.

Management Practices

Furthermore, ITIL 4 replaced the old idea of rigid processes with 34 flexible management practices, each one a set of organizational resources designed to accomplish a specific type of work. Typically, the ones most organizations start with are incident management, service request management, problem management, change enablement, service level management, and the service desk itself. However, you don’t need all 34. Very few organizations use every practice, and those that try to adopt everything at once usually regret it.

What Changed With ITIL Version 5

This is where many explainers fall out of date, so let me bring you current. PeopleCert officially launched ITIL Version 5 in late January 2026. Shortly after, the ITIL Foundation (Version 5) certification became available in February 2026 as the new entry level qualification.

If you’ve already invested in ITIL 4, though, you can breathe easy. Version 5 is an evolution rather than a revolution, and the previous Foundation certificate is still recognized as a prerequisite for all advanced Version 5 qualifications.

Based on my own reading of the new material and conversations with fellow consultants, three shifts matter most.

From Services to Digital Products and Services

First, the scope expands from IT service management to digital product and service management. This reflects something I’ve seen in client work for years. Namely, the line between “the product” and “the service around the product” has blurred. A client portal, for example, is both a piece of software your team builds and a service your clients experience. Thus, Version 5 finally treats those as two sides of the same coin.

The ITIL Product and Service Lifecycle

Second, the old service value chain, which had six activities, is replaced by the Product and Service Lifecycle Model with eight activities. These are discover, design, acquire, build, transition, operate, deliver, and support.

What I like about this change is that it maps much more closely to how modern teams actually work, especially those using Agile and DevOps. Notably, Stuart Rance, one of the most respected voices in our field, has observed that the value system itself is barely changed, and that the main difference is this lifecycle replacing the value chain. In practice, then, it means fewer awkward translation exercises when I’m helping a development team and an operations team agree on who does what.

AI Governance Built Into the Framework

Third, AI governance is now built into the framework, supported by a dedicated AI Capability Model. Frankly, this is overdue. Nearly every client I’ve worked with in the past two years is either experimenting with AI in their service desk or being pitched AI tools weekly. Accordingly, ITIL Version 5 treats AI not as a shiny feature but as something that must be governed, measured, and managed like any other capability. For example, who is accountable when an AI agent closes a ticket incorrectly? Likewise, how do you audit automated decisions? These are questions the new guidance actually addresses.

At the same time, the practice count remains familiar. All 34 Version 5 practices are available through PeopleCert Plus membership.

How ITIL Works Alongside Other Frameworks

Another question I hear often is whether ITIL competes with Agile, DevOps, Lean, or COBIT. It doesn’t, and treating it that way only causes needless arguments between teams.

Here’s how I think of it. Agile and DevOps tell you how to build and ship things quickly in small increments. Similarly, Lean tells you how to remove waste, whereas COBIT focuses on governance and control of enterprise IT. ITIL, on the other hand, tells you how to manage the services that result, so they stay reliable and valuable over time. Indeed, ITIL 4 was explicitly designed to sit alongside Agile, DevOps, and Lean rather than replace them.

Version 5 continues that direction as well. For instance, training for the new Foundation level now covers AI governance and how ITIL integrates with DevOps and PRINCE2.

Ultimately, the healthiest organizations I’ve worked with borrow from all of these without getting religious about any of them.

Common Mistakes When Companies Adopt the Framework

After many implementations, I’ve noticed the same pitfalls repeating. So if you’re considering ITIL, these are worth avoiding.

Buying the tool first. Admittedly, a service management platform is useful. Still, it should support your way of working, not dictate it. More than once, I’ve walked into companies running an expensive platform configured with every default option, and yet none of the staff understood why tickets moved the way they did.

Implementing everything at once. Remember that the framework is a menu, not a set meal. Therefore, pick the two or three practices that address your sharpest pain and get them working well.

Making change management a gatekeeper. Older ITIL implementations often created a weekly change advisory board that approved everything, including trivial updates. Modern guidance, however, calls it change enablement for a reason. In other words, the goal is to help safe changes happen faster, not to block them.

Forgetting the people. Process documents alone don’t change behavior. Instead, training, clear roles, and leadership that actually follows the new practices do.

Measuring the wrong things. Counting closed tickets, for example, tells you very little. By comparison, measuring how users feel about the service, how quickly business critical systems recover, and how often problems repeat tells you far more.

Is ITIL Worth It for Your Organization?

My honest answer as a consultant is that it depends on your size, your dependence on technology, and your appetite for discipline. For example, a five person agency doesn’t need a formal problem management practice. Even so, it does benefit from the ITIL guiding principles and a simple, consistent way to log and resolve issues.

On the other hand, a mid sized professional services firm with a few hundred staff, client facing platforms, and outsourced suppliers almost always benefits from a lightweight ITIL approach. Usually, the return shows up as fewer repeat outages, clearer supplier accountability, and a service desk that users stop complaining about.

Meanwhile, large enterprises and managed service providers typically treat ITIL as a baseline expectation. Clients and auditors ask about it, contracts reference it, and staff often arrive already trained in it.

As for individuals, ITIL certification remains one of the most recognized credentials in IT operations. Foundation is the natural starting point, and moreover, it’s increasingly expected for service desk leads, service owners, and anyone moving into IT management.

Getting Started Without Overthinking It

If you’ve read this far and you’re wondering where to begin, here’s the approach I use with most clients.

Map what you have. First, list your key services, the assets behind them, who owns them, and how issues are currently reported and resolved. Chances are, you’ll find more working practice than you expected.
Find the biggest pain. Next, ask whether it’s slow incident response, risky changes, or poor visibility into supplier performance. Then start there.
Apply one or two practices well. Incident management and service request management are the usual first steps, because they touch users every day.
Train the people doing the work. Additionally, an ITIL Foundation course for team leads goes a long way toward a shared vocabulary.
Review and adjust regularly. Finally, remember that continual improvement isn’t a phase at the end. Rather, it’s a habit you build from week one.

In the end, that’s really the essence of what ITIL is. It is accumulated wisdom about running technology services well, packaged so you can adopt the parts that fit and, meanwhile, leave the rest on the shelf until you need them.

Frequently Asked Questions

What is ITIL in simple words?

In short, ITIL is a set of best practice guidance for managing technology services so they reliably deliver value to users and customers. Specifically, it covers how to handle incidents, requests, changes, and continual improvement. For a broader overview, see this encyclopedia entry on the framework.

What does ITIL stand for?

Originally, it stood for Information Technology Infrastructure Library, which reflects its roots as a library of books produced by the UK government. In addition, this history from IT Process Wiki explains how the name and framework evolved.

Who owns the framework today?

Currently, PeopleCert owns it after acquiring AXELOS in 2021. You can, therefore, read more about the ownership timeline in this ownership guide from ITSM Docs.

What is the latest ITIL version?

At present, the latest is ITIL Version 5, launched in early 2026, with its Foundation certification available from February 2026. For a full breakdown, this InvGate comparison of versions 4 and 5 explains what changed.

Is my version 4 certification still valid?

Yes. In fact, the version 4 Foundation certificate is recognized as a prerequisite for advanced Version 5 qualifications, and a Foundation Bridge is also available for those who want to update. For transition details, see the Global Knowledge certification FAQ.

What are the seven ITIL guiding principles?

They are 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 finally, optimize and automate. Likewise, this University of Utah overview summarizes them clearly.

Can a company become ITIL certified?

No. Only individuals can be certified, so organizations adopt and adapt the practices instead. As this encyclopedia overview notes, there is no formal organizational certification.

What is the ITIL service value system?

Essentially, it’s the model showing how guiding principles, governance, activities, practices, and continual improvement work together to turn demand into value. For more depth, see this service value system explainer from ITSM.tools.

What are the eight activities in the Version 5 lifecycle?

They are discover, design, acquire, build, transition, operate, deliver, and support. Additionally, this Foundation Bridge course outline from Fast Lane describes the lifecycle and related concepts.

Does ITIL replace Agile or DevOps?

No. Rather, ITIL is designed to work alongside Agile, DevOps, and Lean instead of competing with them. Similarly, this Freshworks framework guide covers how these approaches fit together.

References

Sarah Whitmore

Administrator

Technology writer for Foretec.com, covering IT infrastructure, networking, cybersecurity, and practical technology solutions for modern businesses.

View All Posts

Related News

What Is an RFC? How Internet Standards Get Written

Network Topology Types: Star, Mesh, Bus and Hybrid Explained

What Is a CDN? How Content Delivery Networks Make Websites Faster

You may have missed