Experience Management in ITSM: Background, Pillars, Impact

For years, IT has measured its performance using a single criterion: compliance with agreed technical parameters. Response times, availability percentages, tickets closed before the deadline. These are all useful indicators, but they only tell half the story: they show whether IT has followed its own rules, not whether the people using those services have been able to work effectively. Experience Management was born to bridge this gap, shifting the center of gravity of ITSM from process compliance to the real perception of those who use services every day. This is not about abandoning operational metrics, but about integrating them with what truly matters to the business: the productivity and satisfaction of people.

The watermelon effect: when everything is green but no one is satisfied

In the ITSM world, there is a phenomenon known by a curious name: the “watermelon effect.” A dashboard full of green indicators — all SLAs met, management satisfied — that nonetheless conceals a red interior, made up of frustrated users and lost productivity. As Phyllis Drucker observes on ITSM.tools, a service desk too focused on SLAs risks exactly this: measuring the wrong thing because it is chasing the wrong goals. Users, Drucker reminds us, do not want a problem resolved in eight hours — they want fewer problems.

This is a radical shift in perspective. Meeting an SLA does not guarantee that the person on the other end can actually accomplish what they rely on the service for—whether that’s writing a document, accessing a critical system, or completing an operation for a customer. Experience Management starts precisely here: from recognizing that the true goal of IT is not technical performance as an end in itself, but the effect that performance has on employees’ daily work.

What does Experience Management applied to IT consist of?

The concept is not entirely new: experience management has been an established practice for over a decade. What is new is its systematic application to IT operations, a field in which it goes by the name of IT Experience Management (ITXM).

As illustrated in the framework developed by HappySignals, the underlying idea is to transform the IT organization from a model centered on processes and technology to one centered on people, focusing on the outcomes of their work rather than on the internal mechanisms of the system.

This means shifting the focus of the conversation to how people perceive the tools and services they use and the type of support they receive. It is a subtle but decisive distinction: a company can have impeccable ITIL processes and high-performing infrastructure, and yet have no idea what the real effect of all this is on its own employees. Experience Management provides exactly that missing piece of the puzzle.

Experience Management does not replace ITSM — it completes it

One of the most common misconceptions is to regard Experience Management as a separate initiative, to be built alongside the existing ITSM. In reality, the two areas are closely connected, and the ITSM capabilities already present in the organization are often the natural starting point for improving the experience. The same operational improvements that ensure high service availability also produce, as a by-product, a better experience for employees, because they remove the obstacles that prevent them from working.

Incident Management is the most immediate example. Preventing an outage does not only mean ensuring operational continuity — it means giving time and focus back to a person by preventing their work from stopping or slowing down. The way an incident is managed therefore has a direct impact on productivity and on the perception of the service. The same applies to device management: the long wait associated with reporting a fault, diagnosing it, and carrying out repairs erodes the user experience far more than any single technical indicator can convey.

Even the design of the self-service portal suffers the negative effects of a logic centered on technical issues that underestimates the needs of those who actually have to use it. The result? The development of cumbersome interfaces that people avoid. The correct approach is therefore to understand why employees do not use the portal and to redesign it from their point of view, mapping the most frequent usage journeys.

XLAs: measuring value, not just performance

The instrument through which Experience Management concretely enters IT contracts and objectives is the XLA, an acronym for Experience Level Agreement. This is a reinterpretation of traditional SLAs: whereas the latter measure technical parameters such as availability or resolution times, XLAs measure the perceived quality of the service from the end user’s point of view. XLAs do not replace SLAs, but enhance them: where the SLA verifies compliance with a contractual obligation, the XLA places the experience at the center.

There is, however, an important caveat to keep in mind. The XLA is not the end goal, but a measurement tool: if it becomes an objective in its own right, it risks turning into a new “watermelon” — green on the outside and red on the inside. If, for example, operators were to solicit high ratings simply to reach the target score, the XLA would show excellent results while users’ real problems remained unresolved. Its value lies in verifying that the real objective — effective support for business activities — is actually being achieved.

The three operational pillars of Experience Management

For Experience Management to produce concrete results, and not remain a statement of intent, three operational elements are needed that work in a coordinated manner, each indispensable to the others.

1. Experience metrics and continuous feedback

The measurement of experience must be continuous, daily, and must happen at the right moment: while the person is living the experience, or immediately after it has concluded, and not months later. It must also be contextual — that is, tied to what the user is actually doing. Without this data, decisions about what to improve end up being based on subjective impressions, personal beliefs, or the issues raised most insistently, rather than on concrete evidence. It is continuous feedback that transforms perceptions into actionable information.

2. Data sharing and transparency

Measuring is not enough: experience data must be shared with all stakeholders — IT teams, external suppliers, and the rest of the organization. This transparency may initially generate discomfort, because data on user perception often tells a different story from the one conveyed by years of reports featuring purely technical indicators. That is precisely what makes it valuable: it confronts everyone with the same reality and creates a virtuous cycle. When users see that their feedback translates into concrete changes, they are more motivated to continue providing feedback, thereby making the measurement richer and more reliable.

3. Proactive support

The final operational element concerns the transition from an IT that reacts to problems to an IT that prevents them. By cross-referencing configuration data, device logs, and the automated processing of anomalies, it is possible to assign each device a health score — a synthetic index of its condition — and intervene before a fault reaches the user. This is where AI, applied to solid data and well-defined processes, shows its full potential: it anticipates anomalies, reduces interruptions, and frees up employees to focus on higher-value activities.

Impact on productivity and daily work

The quality of the digital experience has a direct effect on productivity: when technology works, people complete their work quicker and with less frustration. When it does not, every slowdown translates into lost time and a backlog of tasks. It is an intuitive connection, but one that is often invisible to an IT department accustomed to observing primarily technical parameters.

There is more: management expectations are changing. A growing share of digital initiatives now requires IT leaders to report results in terms of user experience success as well. This is a capability that IT must develop in order to engage with the rest of the organization in a shared language — that of value creation.

Measuring what truly matters

To understand whether the services delivered are genuinely helping people work better, it is necessary to follow a gradual path: measure the experience from the outset, share the results with all business functions, and address first the issues that weigh most heavily on people’s productivity. It is a cultural change that does not happen overnight, but is built over time. Organizations that embark on this journey will stop settling for technical KPIs — indicators that appear positive but conceal dissatisfied users — and will begin to measure what truly matters: the real impact of technology on their employees’ daily work.

FAQs

1. What is Experience Management in the context of ITSM?
   It is an approach that shifts IT’s focus from the technical performance of services to the real perception of users. Rather than measuring only response times and availability, it concentrates on how much IT services concretely help people work well, integrating operational metrics with experience metrics.
2. What is the difference between an SLA and an XLA?
   An SLA measures technical and contractual parameters, such as system availability or resolution times. An XLA (Experience Level Agreement), on the other hand, measures the perceived quality of the service from the user’s point of view. The two instruments are not mutually exclusive: the XLA enhances the SLA by adding the dimension of experience.
3. Where is it best to start?
   From a limited area, with a single team. The recommended approach is to measure the experience, share the data collected, and address the issues that weigh most heavily on people’s work: the first concrete improvements, even modest ones, serve to demonstrate in practice that the method works and to justify its application to other areas. It is an iterative journey that grows through progressive extensions.
4. What role does AI play in Experience Management?
   An enabling role, especially in proactive support: by analyzing configuration data, logs, and anomalies, AI makes it possible to identify and resolve problems before they reach the user, reducing the likelihood of interruptions. Its value also depends on the solidity of the data and processes on which it operates.