IT Service Management (ITSM)

What is IT Service Management (ITSM)?

IT service management (ITSM) is how an organization designs, delivers, supports and improves the IT services it provides, covering practices such as incident, request, problem and change management.

Updated November 2026 · 3 min read


IT service management (ITSM) is how an organization designs, delivers, supports and improves the IT services it provides to employees and customers. The focus is on services, such as email, a payroll system, laptops or a customer-facing application, rather than on technology components, and on the outcomes those services make possible. ITSM covers everything from answering a password reset request to restoring a failed system, approving changes and agreeing service levels with the business.

ITSM emerged as IT departments moved from running hardware to providing services that the rest of the organization depends on. Frameworks codified good practice, most notably ITIL, first published by the UK government in the late 1980s, and the international standard ISO/IEC 20000, first published in 2005. Today ITSM is supported by dedicated platforms such as ServiceNow, Jira Service Management, BMC Helix and Freshservice.

Core ITSM Practices

PracticePurpose
Service deskA single point of contact for users to report issues and make requests
Incident managementRestoring normal service as quickly as possible when something breaks
Service request managementHandling routine requests such as access, equipment or software
Problem managementFinding and removing the underlying causes of incidents
Change management (change enablement)Making changes safely, balancing speed against risk
Service level managementAgreeing targets with the business and reporting against them
Configuration managementRecording services, systems and their relationships, often in a configuration management database (CMDB)
Knowledge managementCapturing solutions so users and support staff can resolve issues faster
Service catalog managementPublishing the services available and how to request them

ITSM vs. ITIL

ITSM is the discipline; ITIL is the best-known framework for practicing it. An organization can do ITSM without using ITIL, drawing instead on ISO/IEC 20000, COBIT, VeriSM or its own practices, and many organizations combine elements of several. In practice the terms are often used interchangeably, but ITSM describes what is being done and ITIL describes one detailed way to do it.

ITSM, DevOps and Enterprise Service Management

Traditional ITSM was criticized for slow, ticket-heavy processes that clashed with DevOps. Modern ITSM has adapted: automated pipelines provide change evidence, low-risk changes are pre-approved, development teams handle incidents for the services they build and site reliability engineering brings an engineering approach to operations. The same service management approach is also being applied beyond IT, to HR, facilities, legal and finance requests. This is known as enterprise service management, and most ITSM platforms now support it.

Measuring ITSM

  • Mean time to resolve incidents and requests, and how it is trending.
  • First contact resolution: the share of issues resolved without escalation.
  • SLA attainment against agreed service levels.
  • Change success rate: the share of changes that do not cause incidents.
  • Repeat incidents, a sign of weak problem management.
  • User satisfaction, often measured with a short survey after each ticket.

An Example

Consider a hypothetical company of 3,000 employees whose IT team receives about 4,000 tickets a month. Analysis shows that 35% are password resets and access requests, and 20% are repeat incidents from a handful of unstable systems. The team adds self-service password reset and a catalog of pre-approved access requests, which removes about 1,200 tickets a month. It also starts problem management on the five systems causing the most incidents. Within six months monthly tickets fall to about 2,500, first contact resolution rises from 55% to 70%, and agents spend more time on the issues that need them.

Common Pitfalls

  • Tool-first implementations that automate broken processes.
  • Measuring ticket volume and closure speed while ignoring whether users' problems are actually solved.
  • Treating every change as high-risk, slowing delivery without improving stability.
  • A CMDB nobody trusts because it is never kept up to date.

ITSM is how IT runs its services day to day. How those services are funded and costed is the subject of Technology Business Management.