What Is ITSM? IT Service Management, Processes and ITIL 4 Explained

The short answer: ITSM (IT service management) is how an IT team designs, delivers, supports and improves the technology services the rest of the organisation depends on. In practice it is a set of processes, such as incident, service request, problem, change and asset management, run through a service desk and supported by ITSM software. ITIL is the most widely used framework for those processes; ITIL 4 is its current version.

This guide is for IT managers, service desk leads and anyone setting up or maturing an IT function. It explains what ITSM covers, how the core processes work together, where ITIL fits, how ITSM differs from a help desk, and how to start without drowning in process.

What is ITSM?

IT service management treats IT as a provider of services, not just a department that fixes computers. A “service” is something a user values: email, the VPN, a laptop that works, access to the finance system, a new starter’s accounts on day one. ITSM is the discipline of defining those services, agreeing what good looks like (for example, response and resolution targets), delivering them reliably and improving them over time.

Most people meet ITSM through the service desk: the portal where they raise a ticket and the team that resolves it. Behind that front door sit the processes that decide how tickets are prioritised, when a recurring fault becomes a problem to investigate, how changes to systems are approved and who owns each asset.

What does ITSM stand for?

ITSM stands for IT service management. You will also see ESM (enterprise service management), which applies the same processes and tools to HR, facilities, legal and finance requests.

The core ITSM processes

Incident management

An incident is an unplanned interruption or reduction in the quality of a service: an app is down, a printer is broken, the Wi-Fi is slow. The goal of incident management is to restore service as quickly as possible, even with a workaround. Good practice includes clear priority definitions (usually impact multiplied by urgency), escalation rules, and a separate major incident procedure for outages that affect many users.

Service request management

Service requests are routine, pre-approved asks: reset a password, install approved software, provide a new laptop, grant access to a shared drive. Separating requests from incidents keeps reporting honest and lets you automate the routine. A service catalog lists what users can request, with forms, approvals and fulfilment steps built in.

Problem management

A problem is the underlying cause of one or more incidents. Incident management restores service; problem management finds out why it failed and stops it happening again. Teams log known errors (a documented cause with a workaround) so agents can resolve repeat incidents faster while a permanent fix is planned.

Change enablement

Change enablement (called change management in earlier ITIL versions) makes sure changes to systems are assessed for risk, approved by the right people and scheduled to avoid conflicts. Most teams use three types: standard changes (low risk, pre-approved), normal changes (assessed and approved, sometimes by a change advisory board) and emergency changes (fast-tracked to fix an urgent issue). Modern practice pushes approvals towards automation for low-risk changes so the process does not slow delivery.

Knowledge management

A maintained knowledge base lets agents resolve tickets consistently and lets users help themselves. The hard part is not the tool but the habit: writing articles as part of closing tickets and reviewing them regularly.

IT asset and configuration management

IT asset management tracks hardware and software across their lifecycle: purchase, assignment, maintenance, licences and disposal. Configuration management goes a step further, recording configuration items (servers, applications, network devices, cloud resources) and the relationships between them in a CMDB. That map lets you see which business services an incident affects and what a change might break. For tools, see our guide to IT asset management software.

What is ITIL, and how does it relate to ITSM?

ITIL is a framework of best practice for IT service management. ITSM is the discipline; ITIL is a widely used guide to doing it. ITIL describes processes (called “practices” in ITIL 4), roles and terminology, and many ITSM tools are built around its structure.

ITIL 4 moved the framework away from rigid, linear processes towards a flexible model. Its main ideas are:

• The service value system, which describes how all parts of an organisation work together to create value.
• The service value chain, six activities (plan, improve, engage, design and transition, obtain or build, deliver and support) that can be combined in different ways for different work.
• Guiding principles, such as focus on value, start where you are, progress iteratively with feedback, and keep it simple and practical.
• Practices, the set of capabilities such as incident management, change enablement and service desk that an organisation draws on.

You do not need to adopt all of ITIL. Most teams take the practices that solve their current problems, usually incident, request, knowledge and change, and add more as they mature. Other frameworks are used alongside or in place of ITIL, including COBIT for governance, ISO/IEC 20000 for certification, and DevOps and site reliability engineering practices for teams that ship software frequently.

ITSM vs help desk vs service desk

These terms overlap, which causes confusion:

• Help desk: a team and tool focused on fixing user issues. Often reactive and ticket-centric.
• Service desk: the single point of contact between IT and users, handling incidents and service requests and connected to wider ITSM processes such as change, problem and asset management.
• ITSM: the whole discipline of managing IT services, of which the service desk is one part.

We cover the differences, and when each makes sense, in help desk vs service desk. For the help desk definition on its own, see what is help desk software.

ITSM vs ITOM vs ESM

ITOM (IT operations management) covers running the infrastructure itself: monitoring, event management, discovery, automation and capacity. ITSM and ITOM meet when a monitoring alert creates an incident or when discovery feeds the CMDB. AI is increasingly used across both; see our overview of AIOps tools.

ESM (enterprise service management) applies ITSM ideas to other departments. HR onboarding, facilities requests and legal approvals can all use the same portal, catalog and workflow engine as IT.

What are ITSM tools?

ITSM tools are software platforms that run these processes. A typical ITSM tool includes a ticketing system, a self-service portal, a knowledge base, a service catalog, workflow and approval automation, SLA tracking, asset management or a CMDB, reporting, and integrations with identity, endpoint and monitoring systems. Many now include AI features for ticket triage, summaries and virtual agents.

Well-known examples include ServiceNow, Jira Service Management, Freshservice, HaloITSM, ManageEngine ServiceDesk Plus, SysAid, TOPdesk and Ivanti Neurons for ITSM. We compare them in our guide to the best IT service desk software, and you can browse more in the service desk software category.

Benefits of ITSM

• Faster, more predictable support. Clear priorities, routing and SLAs mean users know what to expect.
• Fewer repeat failures. Problem management fixes causes, not just symptoms.
• Safer changes. Assessed and recorded changes reduce outages caused by IT’s own work.
• Cost control. Asset and licence tracking exposes waste and supports renewals.
• Audit readiness. Records of who approved what, and when, support security and compliance reviews. For the security side, see application security essentials for ITSM teams.
• Better self-service. A catalog and knowledge base reduce ticket volume for routine asks.

How to implement ITSM: a practical starting plan

1. Start where you are. Document how tickets arrive today, who handles them and what gets measured.
2. Separate incidents from requests. This one change makes reporting and automation far easier.
3. Define priorities and SLAs that the business agrees with. Keep the matrix simple.
4. Build a small service catalog of the 10 to 20 most common requests, each with a form and fulfilment steps.
5. Stand up a knowledge base and make writing articles part of closing tickets.
6. Introduce change enablement for production systems, with a fast path for standard changes.
7. Add problem management once you have enough ticket data to spot patterns.
8. Grow the asset register towards a CMDB when change and incident impact analysis need it.
9. Review monthly and improve one thing at a time.

ITSM metrics worth tracking

• Mean time to acknowledge and to resolve, by priority
• First contact resolution rate
• SLA breach rate and backlog age
• Self-service resolution and knowledge article use
• Change success rate and number of emergency changes
• Repeat incidents linked to known problems
• User satisfaction after ticket closure

Frequently asked questions