Was ist ITSM? Eine Definition aus der Praxis für 2026

IT service management (ITSM) is how an organisation designs, delivers, supports and improves the IT services its people rely on. It treats IT as a set of services with agreed outcomes (email that works, a point-of-sale system that is available when stores are open, a laptop ready on a new joiner's first day) rather than a collection of systems and tickets.

That is the definition. The rest of this page is what it means in practice, written from running service delivery for retail, pharmaceutical, energy, maritime and telecom organisations across the GCC.

What counts as an IT service

An IT service is something the business uses to get work done, described in the business's terms. "Microsoft 365" is a product. "Email and calendar for every member of staff, available 24×7, with new mailboxes ready within one working day" is a service.

The difference matters because a service has an owner, a target and a cost. A product on its own has none of those. When nobody can say which services IT provides, nobody can say whether IT is doing well.

What ITSM covers

ITSM is a set of practices, each answering one question the business will eventually ask. These seven carry most of the weight in a typical IT department:

ITIL describes 34 management practices in all. Nobody runs all 34 at the same depth, and nobody should try. Start with the ones that hurt.

The frameworks around ITSM

ITSM is the work. Frameworks and standards are guidance for doing it, and each answers a different question.

A note on the name, since nearly everyone gets it wrong: you will hear "ITIL 5" and "ITIL v5" in every meeting room, because that is how version numbers usually work. PeopleCert's official name is ITIL (Version 5), and the qualifications follow the same pattern: ITIL Foundation (Version 5), ITIL Strategy (Version 5). Search engines don't mind which one you type. Your certificate does, so use the official name on your CV, where a recruiter's search will look for the exact wording.

Most mature organisations combine them: ITIL to run the services, COBIT to govern them, ISO/IEC 20000 when a client or regulator wants certified proof. The detail is in ITSM vs ITIL and ITIL vs COBIT.

Four things many ITSM guides still get wrong

Search for "what is ITSM" and many of the top pages, most of them written to sell software, repeat claims that stopped being true years ago.

1. "ITIL is in its fourth version." The current version is ITIL (Version 5). ITIL 4 certificates remain valid, and PeopleCert's current plan is to retire the ITIL 4 exams on 31 December 2027. If your team is planning certification, the ITIL 4 to ITIL (Version 5) guide sets out the routes.

2. "ITSM has five lifecycle stages: strategy, design, transition, operation and continual improvement." That is the ITIL v3 service lifecycle, published in 2007 and revised in 2011. ITIL 4 replaced it in 2019 with a value system built around guiding principles, value chain activities and practices. A guide that still teaches the five stages as current is teaching a model more than a decade old.

3. "The core ITSM processes." ITIL stopped calling them processes. A practice includes processes, but also the people, information, tools and suppliers needed to do the work. The distinction is not pedantry: organisations that "implement the incident process" in a tool and stop there are the ones whose incidents keep coming back.

4. "Change management." In ITIL the practice is change enablement: helping changes happen safely with the right amount of control. Its three change types (standard, normal and emergency) exist so a routine patch isn't waiting for a weekly board while a risky database change still gets a second look.

What ITSM looks like in a GCC organisation

The practices are universal. The calendar isn't. A service desk in Dubai works Monday to Friday, one in Riyadh works Sunday to Thursday, both often support vendors on a different week, and runs reduced hours through Ramadan. An SLA measured on a generic Monday-to-Friday calendar will report breaches that never happened and miss the ones that did.

Three checks I run in every new engagement:

• Is the SLA clock on your real calendar? Working week, public holidays and Ramadan hours, for each country you support. The GCC business calendar builds one in your browser.
• Does every service have one named Service Owner, vendors included, who answers for it end to end?
• Are repeat incidents going to problem management? Structured problem management is how my teams cut recurring incidents by 40%. If you are not sure where to draw the line, run a live case through the incident or problem tool.

Wo Sie anfangen sollten

You don't adopt ITSM: you already do it. The choice is whether you do it on purpose. Pick the one service the business complains about most, name its owner, agree what "working" means for it, and measure that on your real calendar for a month. The numbers will tell you which practice to fix first.

To see where your team stands across all of this, the free ITSM maturity check takes three minutes, needs no sign-up and gives the full result on screen. Terms used on this page are defined in the ITSM Compass glossary.

Häufige Fragen