TL;DR
ITSM (IT service management) is the discipline of running IT as a set of services for the people who use them. ITIL is a framework of guidance on how to do that well.
Every IT team that handles requests is doing ITSM in some form. ITIL is optional: it's the framework most people mean, but ISO/IEC 20000-1, COBIT and DevOps practices sit in the same toolbox.
Neither one is software. Tools like ServiceNow, Jira Service Management and Ravenna are where ITSM work happens, and some of them get assessed against ITIL practices.
PeopleCert is releasing ITIL (Version 5) in phases. The relationship between ITIL and ITSM hasn't changed.
ITSM is the job, and ITIL is one well-known set of instructions for doing it. That's the whole difference, and PeopleCert, the company that owns ITIL, frames it the same way: ITSM is "the 'What'" and ITIL is "the 'How'".
The two terms get used interchangeably in job posts, vendor pages and RFPs, which is where most of the confusion comes from. This guide lays out the difference in a few tables and one restaurant analogy. Then it covers where other frameworks, ITIL 5 and your tooling fit.
What's the difference between ITSM and ITIL?
ITSM is what you do. ITIL 4 defines service management as "a set of specialized organizational capabilities for enabling value for customers in the form of services," according to the Introductory Overview of ITIL 4. In IT terms, that's everything involved in getting people the laptops, access, answers and fixes they need. It also means checking whether any of it actually worked. You're doing ITSM the moment someone asks your team for help and you have a way of handling it, even if that way is a Slack channel and a spreadsheet.
ITIL is a framework for how to do it. It was first developed in the 1980s, and early use was mostly confined to the UK and the Netherlands, per the same overview. The name originally stood for IT Infrastructure Library, but PeopleCert says the acronym has been retired because the guidance expanded well beyond running infrastructure. ITIL 4 describes its own guidance as "neither definitive nor prescriptive," which matters more than it sounds: it's guidance you adopt and adapt, not a rulebook you comply with.
Question | ITSM | ITIL |
|---|---|---|
What is it? | A discipline: managing IT as services for the people who use them | A framework of guidance for doing ITSM |
What does it answer? | What services do we provide, and are they working? | How should we run those services? |
Who owns it? | Nobody, it's a general practice | PeopleCert, which acquired AXELOS in 2021 |
Can you be certified? | An organization can be assessed against ISO/IEC 20000-1 | Individuals earn ITIL certifications, and PeopleCert accredits tools |
Can you buy it? | No, you buy tools that support it | No, you buy the books, training and exams |
Example | Deciding employees should get software access the same day they ask | Using ITIL's service request management practice to define how those requests get logged, approved and fulfilled |
So ITIL sits inside ITSM. You can run ITSM without ever opening an ITIL book, but ITIL has no purpose outside of ITSM.
The restaurant analogy
Think about running a restaurant. ITSM is running the restaurant: the menu, the kitchen staff, reservations, getting food to the table and hearing what customers thought. Your employees are the diners, and the dining experience is the support they get from IT.
ITIL is a respected cookbook and kitchen operations manual. It shows you proven ways to handle a dinner rush (incident management), change the menu without chaos (change enablement) and work out why the same dish keeps getting sent back (problem management). You can run a good restaurant without it, and most good kitchens borrow the recipes that suit them instead of cooking every page.
The analogy stretches to the rest of the stack, too:
In the restaurant | In IT | What it is |
|---|---|---|
Running the restaurant | ITSM | The discipline |
The cookbook and kitchen manual | ITIL | A framework of guidance |
The health inspection | ISO/IEC 20000-1 | A standard you're assessed against |
The owners and their accountants | COBIT | Governance and oversight of IT |
The kitchen equipment | Your ITSM tool | Software that supports the work |
The diners | Your employees | The people the service exists for |

How does ITIL compare with other ITSM frameworks?
ITIL isn't the only option, and it doesn't claim to be. The ITIL 4 overview itself names COBIT and SIAM as other frameworks, and says ITIL 4 is designed to work alongside Lean, Agile and DevOps.
Framework | Owner | What it is | Reach for it when |
|---|---|---|---|
ITIL 4 and ITIL (Version 5) | PeopleCert | Guidance on service management practices, from incident management to service request management | You want proven practices to adapt for your service desk |
ISO and IEC | Requirements an organization has to meet to "establish, implement, maintain and continually improve" a service management system | Auditors, customers or contracts ask for proof | |
ISACA | A framework for "the governance and management of enterprise information and technology" | Leadership needs control objectives and oversight | |
DevOps, Agile and Lean | No single owner | Ways of working that speed up delivery and flow | Engineering speed and change frequency are the priority |
Most teams mix these rather than picking one. The most common pairing is ITIL with DevOps, and our guide to ITIL vs DevOps covers how teams run both without the two fighting each other.
What's inside ITIL 4
ITIL 4 organizes its guidance around a service value system made up of five components: the guiding principles, governance, the service value chain, practices and continual improvement. It also asks you to look at every service across four dimensions: organizations and people, information and technology, partners and suppliers, and value streams and processes.
The part most IT teams use day to day is the practices. The ITIL 4 overview lists 34 of them: 14 general management, 17 service management and 3 technical management practices. A service desk usually starts with a handful:
Incident management restores service when something breaks, like the VPN going down.
Problem management finds out why the VPN keeps going down every Friday.
Change enablement gets updates out without breaking the things people rely on.
Service request management handles routine asks like software access or a new laptop.
Knowledge management keeps answers findable, so people can help themselves.
Above the practices sit the seven guiding principles, like Focus on value and Start where you are. They're the decision rules you fall back on when a process doesn't cover the situation, and we walk through each one in our guide to ITSM principles.
What changes with ITIL (Version 5)?
PeopleCert describes ITIL (Version 5) as "AI-native by design," introduced through a gradual, phased release, with digital experience as a core focus. It also says existing ITIL knowledge and certifications "continue to hold their value," and ITIL 4 stays available for anyone partway through a certification path.
For the ITIL vs ITSM question, nothing structural changed. ITSM is still the discipline and ITIL is still a framework for it; Version 5 widens ITIL toward digital product and service management and adds guidance for teams working with AI. The guiding principles kept their names, so if you learned them for ITIL 4 Foundation you don't need to relearn them.
Where do ITSM tools fit?
Neither ITSM nor ITIL is software. You can't buy ITSM, because it's a decision about how your team runs services. You can't install ITIL either; it's guidance you adapt. Tools like ServiceNow, Jira Service Management and Ravenna are just where that work happens.
Some vendors have their tools assessed against ITIL. PeopleCert runs an ITIL-Accredited Tool Vendors programme for ITIL 4-compatible tools, and Pink Elephant's PinkVERIFY assesses tools against ITIL-aligned practices. Treat those as a sign the tool won't fight your process, not as proof your process is any good.
The bigger difference between tools is where the work happens. Here's the same ITIL practice, service request management, run two different ways:
Step | Portal-first service desk | Chat-first service desk |
|---|---|---|
Request | Employee finds the portal and fills in a form | Employee asks in Slack or Microsoft Teams |
Triage | An agent reads the ticket and assigns it | An AI agent identifies the request type and routes it |
Approval | Manager gets an email and logs in to approve | Manager approves from a card in the same chat |
Fulfillment | Someone makes the change by hand | A workflow triggers the change in the identity provider |
Status | Employee checks the portal or asks for an update | Updates post in the original thread |

Both columns follow ITIL. Only one of them meets employees where they already ask for help, and that choice is an ITSM decision, not an ITIL one.
Start with ITSM goals, not ITIL compliance
Our view is that most teams get the order backwards. They start with "we need to be ITIL compliant," buy a tool built around that idea, and end up with a portal full of forms nobody fills in. ITIL calls its own guidance "neither definitive nor prescriptive," so compliance was never really the point; if you need something an auditor can check, that's what ISO/IEC 20000-1 is for.
The order that works:
Define what good support looks like at your company. Write down 3 to 5 statements, like "Help is one message away" or "Access requests are done the same day."
Borrow the ITIL practices that get you there. Most teams need incident management, service request management and knowledge management long before they need the other 31.
Pick tools that serve the goals you wrote down, not the other way around.
This is also why "ITIL vs ITSM" is a slightly odd question. They aren't competitors; the useful version of the question is which parts of ITIL your ITSM actually needs.
Where Ravenna fits
Ravenna is an AI-native service desk that runs in Slack and Microsoft Teams, so ITSM practices happen in the chat where people already ask for help instead of in a separate portal. Its AI agents answer from your connected knowledge sources like Confluence, Notion or Google Drive, a Knowledge Gaps view groups the questions your docs don't answer yet, and you can generate knowledge articles from resolved tickets. That's ITIL's knowledge management practice without a separate writing project.
For service requests, Ravenna routes the request, collects approvals and triggers the change in the system that owns it, like Okta, Microsoft Entra or Jamf. It verifies the result and logs every step. It doesn't create identities or provision accounts itself; your identity provider and MDM still do that. Ravenna's request management processes are also PinkVERIFY certified, and our guide to automating software access requests shows what the flow looks like end to end.
If you want to see how ITIL practices map onto your own request queue, we're happy to show you.
Frequently Asked Questions
What's the difference between ITSM and ITIL?
ITSM is the discipline of managing IT as services for the people who use them, covering how requests, incidents, changes and knowledge get handled. ITIL is a framework of guidance on how to do ITSM well, owned by PeopleCert. ITSM is what you do, and ITIL is one well-established way to do it.
Is ITSM the same as ITIL?
No. ITSM is the overall practice, and ITIL is one framework within it. You can run ITSM without following ITIL, using ISO/IEC 20000-1, COBIT or a process of your own, but ITIL only makes sense in the context of ITSM.
Is ITIL still relevant in 2026?
Yes. PeopleCert is releasing ITIL (Version 5) in phases, describes it as AI-native, and says existing ITIL knowledge and certifications continue to hold their value. Its core practices, like incident management and service request management, still describe how most service desks work, even when the work happens in chat instead of a portal.
Is ServiceNow ITSM or ITIL?
Neither, strictly. ServiceNow is software for running ITSM, and ITIL is a framework, so no product is ITIL itself. ServiceNow's ITSM product supports ITIL-style practices like incident, problem and change management, but your team still decides how those practices run.
Which ITSM tools support ITIL 4?
Most ITSM tools support ITIL 4 practices to some degree, so look for independent assessment rather than marketing claims. PeopleCert's ITIL-Accredited Tool Vendors programme accredits tools for ITIL 4 compatibility, and Pink Elephant's PinkVERIFY assesses tools against ITIL-aligned practices. Ravenna holds PinkVERIFY certification for request management and AI capability.






