ITSM

What is ITSM? A plain guide for IT managers

Last updated 2 October 2026

What is ITSM? IT service management (ITSM) is the way an IT team designs, delivers, supports and improves the services the business relies on. It covers how requests and incidents are handled, how changes are controlled and how service performance is measured. ITIL is the best-known body of guidance for doing it, and ISO/IEC 20000-1 is the international standard that sets requirements for a service management system.

What is ITSM in practice?

AXELOS, which managed ITIL before PeopleCert acquired it in 2021, describes ITSM as the implementation and management of quality IT services that meet the needs of the business. The word that matters is services. Users do not care which server, licence or network link sits behind a service. They care that they can log in on Sunday morning, that payroll runs before its deadline and that a new starter has access on the first day.

So what is ITSM at its core? It is the operating discipline around the technology. It decides who answers when something breaks, how quickly, who approves a change to a production system and how anyone knows whether IT is meeting expectations. A ticketing tool records that work but does not decide how the work should be done. A team can own an expensive tool and still handle the same issue differently depending on who picks it up.

It is also wider than a help desk. The service desk is one practice within ITSM, and the one users see, so it is the visible part of the answer to “what is ITSM”.

What is ITSM made of? The core practices in plain words

ITSM is made of practices, and ITIL 4 describes 34 of them, grouped into general management, service management and technical management topics. Six of them form the core of most service desks. The purposes of the ITIL 4 practices below are paraphrased from PeopleCert’s descriptions of each practice, and the last column is a practitioner’s observation.

Practice	What it is for	What it looks like when missing
Service desk	Acting as the central point of contact between IT and its users	Users message individual engineers, so nobody sees the whole workload
Incident management	Restoring normal service quickly after an unplanned disruption	A password reset and a finance system outage wait in the same queue
Service request management	Handling predefined, user-initiated requests such as access or equipment in a consistent way	Every request is treated as a one-off and takes a different route
Problem management	Reducing the likelihood and impact of incidents by finding their causes and managing workarounds and known errors	The same fault returns every month and is fixed again each time
Change enablement	Maximising the number of successful changes by assessing risk, authorising changes and managing the change schedule	Updates go live without review or a rollback plan, and cause incidents
Service level management	Setting clear, business-based targets for services and tracking performance against them	IT is judged on its worst week because nothing else is measured

Most teams do not adopt all 34 practices. What is ITSM for a team starting out? A sensible order is service desk, incident and request handling first, then change enablement and service level management, then problem management once there are enough tickets to show patterns. That order is a practitioner’s judgement, not an ITIL rule.

ITSM vs ITIL and ISO/IEC 20000-1: how they relate

They sit at different levels, so treating them as rival choices causes confusion. Part of the answer to “what is ITSM” is that it is the discipline, while ITIL and ISO/IEC 20000-1 are two ways of describing or assessing it.

ITSM is the discipline of managing IT services. PeopleCert describes it as the overall practice of managing IT services, and ITIL as a set of best practices for running and improving them.
ITIL is a framework of guidance. ITIL 4 organises it around a service value system, seven guiding principles, four dimensions (organisations and people, information and technology, partners and suppliers, value streams and processes) and the practices above. People take ITIL exams as individuals.
ISO/IEC 20000-1 is an international standard that specifies requirements for establishing, implementing, maintaining and continually improving a service management system. The current edition is the third, published in September 2018 and confirmed at ISO’s 2023 review. Organisations, rather than individuals, are assessed against it.

A team can use ITIL practices to run the service desk day to day and use ISO/IEC 20000-1 as the yardstick when a customer, tender or board asks for evidence of service management capability. Used together, they give a team both daily discipline and external evidence, which is a practical answer to “what is ITSM”. The standard’s operational clause covers the service portfolio, relationship and agreement, supply and demand, service design, build and transition, resolution and fulfilment, and service assurance.

A note on ITIL versions

This guide’s answer to “what is ITSM” uses ITIL 4 terms. PeopleCert has since released ITIL (Version 5), which it presents as covering digital product and service management across a full lifecycle. PeopleCert’s ITIL FAQ says the current plan is to sunset all ITIL 4 modules on 31 December 2027, and that ITIL 4 qualifications are recognised as prerequisites for Version 5 modules. If you are planning training or certification, check which version a provider teaches and how it describes the practices.

Signs that an IT team needs more ITSM

If you are asking “what is ITSM” because something is already going wrong, these are the usual signs.

Users contact individual engineers directly, so total demand is invisible.
Urgent issues wait behind routine ones because nothing separates them.
Changes to production systems go in without review, and incidents follow.
Management asks for resolution times, but tickets are categorised so inconsistently that the numbers cannot support a decision.

These are gaps in process, so the fix is a shared way of working rather than a reminder to try harder.

Where to start

The question after “what is ITSM” is where to begin, and there is no single correct sequence. This one suits a team that has grown faster than its processes.

Put every request and incident into one queue, whatever channel it arrives by, and decide whether tickets can be raised in Arabic as well as English.
Agree a short priority rule based on business impact and urgency, and a small list of categories people will actually use.
Put changes to production systems through a light approval step with a rollback plan.
Write service levels once a few weeks of ticket data show what is realistic. The IT service desk SLA template lists the fields to include.
Review repeat incidents each month and open problem records for the worst offenders.

A tool can be chosen and configured after these decisions, which stops a product’s defaults from shaping the process. Organisations that want help with that sequence can look at WASNA Digital Solutions’ ITIL-aligned ITSM and service desk design, which covers process design, service desk setup, SLA definition and reporting.

Two questions IT managers ask

Can a small IT team do ITSM without buying a tool first?

Yes. The practices are agreements about how work is handled, and a shared mailbox or spreadsheet can carry a small volume while the rules are set. A tool becomes necessary when volume, approvals and reporting outgrow it. Settle the priority rule, categories and approval path first so the tool is configured to them.

Is ISO/IEC 20000-1 certification a requirement?

The standard is voluntary in itself. Whether you need an assessment against it depends on whether customers, tender documents or your own board ask for evidence. Check the contracts and regulations you answer to before deciding.

Talk through your service desk design

Still asking “what is ITSM” for your own team? Tell us how tickets are handled today, which tool you use and what management wants to see in a report.

Discuss your ITSM setup