No more open-ended man-day invoices.Buy outcomes, not man-days.We offer Implement at a fixed price based on the validated scope.

ITSM · Solutions

What is ITSM? A guide to IT service management, ESM and employee experience

ITSM (IT Service Management) is the way a company delivers its IT services in a planned and measurable manner through request, incident, problem, change and asset processes. ITIL is the most widely used good-practice framework for this discipline. When the same approach is applied to departments such as HR, facilities and purchasing, it is called enterprise service management (ESM); its outcome is employee experience (EX).

IT service management, traceable.

Last updated: · MindDX

ITSM guide

From IT to the whole company: understanding and setting up service management

This guide explains what ITSM is, how it relates to ITIL, its core processes, the difference between a help desk and a service desk, how enterprise service management (ESM) and employee experience (EX) connect with ITSM, which metrics are tracked and how an ITSM tool is selected and put into use.

What is ITSM, and what is it for?

ITSM is the management, through defined processes, of the services IT provides to the company, that is, everything from user accounts to business applications and from hardware to network access. Requests do not get lost in email and phone traffic; each one is recorded, assigned to an owner and tracked against a target time.

The value of ITSM is visibility: how busy is IT and with what work, which faults recur, which change affected which system, which devices and licences does the company have? These questions are answered from records, not from guesswork.

  • Which requests are open, and which are about to exceed their target time?
  • Which faults recur, and what is their root cause?
  • Which systems and users will a planned change affect?
  • Which computers, devices and licences does the company have, and who has them?
  • Are users satisfied with the service they receive?

What is ITIL, and is it the same as ITSM?

No. ITSM is a discipline; ITIL is the most widely used good-practice framework written for this discipline. ITIL is neither software nor a mandatory standard: it offers a common language and a set of practices for how services are designed and delivered. A company starts not with the whole of ITIL but by choosing the practices it needs.

Current versions of ITIL take service management beyond IT: PeopleCert’s ITIL catalogue also includes topics such as experience and AI governance. This shows that service management is now concerned not only with time but also with experience and with the oversight of AI.

The core processes of ITSM: with manufacturing as an example

The core processes of ITSM rest on the same principles regardless of the sector; how they are applied depends on how the business is organised. In businesses with warehouses, branches or production plants they also reach the field. The table below shows the core processes, taking a manufacturing company as the example; the examples are illustrative.

Configuration management keeps the components that make up an IT service, and the links between them, in a configuration management database (CMDB); IT asset management (ITAM) looks at the same hardware and software from the angle of ownership, licences and life cycle. In short, the CMDB answers what a change will affect, ITAM who has an asset and when it is due for renewal.

IT operations management (ITOM) is concerned with keeping the infrastructure running: it continuously monitors servers, the network and applications (monitoring), turns incoming alerts into meaningful events (event management) and automates recurring interventions. When an alert points to an outage that affects users, an incident record is opened automatically, so incident management often starts before a user calls.

The core processes of ITSM, with examples from a manufacturing company
ProcessWhat it doesExample from manufacturing
Service requestFulfils a standard requestA user account for an operator starting on a shift
Incident managementRestores service after an interruption as quickly as possibleA label printer or handheld terminal on the line stopping
Problem managementFinds the root cause of recurring incidentsFrequent network outages on the same line
Change managementPlans a change with a risk assessmentAn ERP or MES version upgrade
IT asset management (ITAM)Records hardware, software and licences with their ownership and life cycleShop-floor computers, terminals and licences
Configuration management and the CMDB (configuration management database)Tracks the components that make up a service and the links between themWhich MES server, terminals and network switch a production line depends on, and which lines a server change will affect
Knowledge managementMakes solutions reusableA solution article for a common printer fault

CMDB: glossary entry

The difference between a help desk, a service desk and ITSM

These three concepts are often confused. A help desk focuses on solving the problem, a service desk on delivering the service; ITSM is the whole process and management system behind the service desk.

Help desk, service desk and ITSM compared
ConceptFocusScope
Help deskSolving the problemFault and question records
Service deskDelivering the service, being the single point of contactRequests, incidents and communication; the user-facing side
ITSMManaging the whole life cycle of the serviceRequest, incident, problem, change, asset, knowledge and measurement

Customer-facing support: the customer service and CX guide

ITSM, ESM and employee experience (EX): the differences and the link

Enterprise service management (ESM) is the application of methods proven in ITSM, that is, request logging, the service catalogue, approval workflows and target times, to departments outside IT. HR manages onboarding and leave requests, facilities management handles faults, purchasing handles approvals and legal handles contract requests with the same method; employees use a single portal for all of them.

Employee experience (EX) is the whole of the contacts an employee has with the company, and these services are an important part of it. A search for «employee experience software» often brings up HR survey and engagement tools; this page describes the service side of the experience: how easily a request is raised, how transparently it is tracked and how well it is resolved.

Comparison of ITSM, ESM and employee experience
DimensionITSMESMEmployee experience (EX)
ScopeIT servicesInternal services outside ITAll of the employee’s contacts with the company
Who raises the requestThe employee, for an IT serviceThe employee, for an HR, facilities, purchasing or legal serviceThe employees themselves, at every moment of their journey
Typical exampleAccess, fault, software installationOnboarding, leave, facility fault, purchase approvalThe journey from joining to leaving
OwnerITThe department concernedHR and management, together with the departments
How it is measuredTarget times and service levelTarget times per departmentExperience and satisfaction indicators

What are SLA, OLA and XLA?

Service levels can be defined through three different agreements. An SLA targets the promise made to the person receiving the service, an OLA the commitment between internal teams needed to keep that promise, and an XLA the experience the user has rather than time. Each company sets the target values according to its own services.

Types of service level agreement
AgreementPartiesWhat it defines
SLA (service level agreement)Service provider and userService targets such as response and resolution time
OLA (operational level agreement)The internal teams that deliver the service togetherThe times each team commits to in order to keep the SLA
XLA (experience level agreement)Service provider and userTargets for how the user experiences the service

Which metrics are tracked in ITSM?

Metrics are chosen according to the purpose of the service; the ones below are the most common, and the company sets the target values itself:

  • first response time: the time until the request receives a first reply,
  • resolution time: the time from the opening of a request until it is resolved,
  • first-level resolution: requests resolved without being handed over to a specialist team,
  • service level compliance: requests resolved within the target times,
  • reopened requests: records marked as resolved and then reopened,
  • recurring incidents: interruptions arising from the same root cause,
  • user satisfaction: the rating given after the request is closed.

When is ITSM needed?

If several of the following signs are present, IT requests have outgrown what can be managed:

  • requests arrive by email, by phone and in the corridor, and nobody knows where each one stands,
  • the same fault happens again and again, but its root cause is not investigated,
  • a system change breaks something in an unexpected place,
  • there is no up-to-date list of the company’s devices and licences,
  • HR, facilities and purchasing requests also run by email and cannot be tracked.

What to look for when choosing ITSM software

Run a trial with your own request types and ask these questions:

  • Process coverage: is it a real ITSM tool, or an advanced help desk?
  • ITIL alignment: are the incident, problem, change and asset processes linked to one another?
  • ESM: can separate workspaces for HR, facilities and purchasing be opened from the same portal?
  • Integration: are there documented connections to the user directory, ERP and, where relevant, MES?
  • Asset management: can devices in offices, warehouses and on the shop floor be discovered and recorded?
  • Language and data: is there a Turkish interface, in which region is the data held, and how is it assessed under KVKK?
  • AI: do classification and reply suggestions work with human approval?

How is ITSM put into use?

Trying to set up everything at once is the most common mistake. A sound start is made with service request and incident management, that is, the processes users feel most; asset, change and problem management are added on top of them. ESM is rolled out department by department once the method has settled in IT.

The typical stages are: a service and request inventory, defining the service catalogue and target times, the portal and knowledge base, integration with the user directory and other systems, training and the start of measurement.

How Assess works

What does AI do in ITSM?

In ITSM, AI is used above all to classify requests and route them to the right team, to answer the user’s question from the knowledge base, and to offer the agent a summary and a draft reply. In risky steps such as approving a change or granting access, the decision must remain with a person.

AI agents: agentic AI

MindDX and Freshservice

MindDX implements Freshservice in companies where the need for ITSM has been proven. Freshservice is an AI-supported service management platform built on ITIL best practices; IT service management, asset management, operations management and enterprise service management work on a shared data layer.

The role of MindDX is not limited to installing the software: it runs the service inventory, the design of the catalogue and target times, the integrations and the rollout of ESM to the departments within a single scope.

Explore Freshservice

Frequently asked

Frequently asked questions about ITSM, ESM and employee experience

Sources

Relationship with MindDX Platform

The products in this category are not Platform modules. The Platform governs, with evidence, the selection and the implementation readiness; the products carry the work.

Explore MindDX Platform

Neighbouring categories

Assess · Implement · Transform entry points

Let us first make clear what needs to be done.

The road into this category does not start with the category. Which category and which product fit is proven in Assess.

Assess entry points

Checkup — Readiness and assessmentSoftware-independent
Discover Scope — New implementation · clarifying the scopeRoute A
Audit — Live system · analysisRoute B