One of the most common assumptions in service management is that if a service is working properly, users will be happy. Unfortunately, reality is rarely that simple.
Organizations frequently encounter situations where services meet performance targets, satisfy service level agreements, and deliver the intended functionality, yet users remain frustrated, resistant, or disengaged.
- Provider’s perspective: Everything appears to be working.
- Consumer’s perspective: Something feels wrong.
Understanding this gap is one of the key themes explored in ITIL Experience and represents an important evolution in modern service management thinking.
The Difference Between Service Success and Experience Success
Consider a service desk that consistently resolves incidents within agreed service levels.
- Response times are excellent.
- Resolution targets are being met.
- Tickets are being closed efficiently.
- Management dashboards show green across the board.
Yet users continue to complain. How is that possible? The answer often lies outside the traditional metrics.
- Users may feel that updates are infrequent.
- They may not understand what is happening behind the scenes.
- They may feel their concerns are being dismissed.
- They may receive technically correct solutions that fail to address the underlying issue that prompted them to seek assistance in the first place.
Operationally, the service may be successful; experientially, it may be failing.
Every Service Is a Relationship
Many organizations unconsciously treat service management as a series of transactions:
- A request is submitted.
- A ticket is opened.
- An issue is resolved.
- A ticket is closed.
While these activities are important, they only tell part of the story. Behind every service interaction are people attempting to achieve outcomes. Those people develop expectations, perceptions, levels of trust, and opinions about the organizations supporting them.
- Every interaction contributes to the relationship between service provider and service consumer.
- A single interaction may be forgotten, but hundreds of interactions create an experience that shapes future behavior.
- Users who trust a service are more likely to adopt new capabilities, follow recommended processes, and engage constructively with service providers.
- Users who lack trust often create workarounds, bypass official channels, and resist change initiatives.
Functional Interactions Versus Relational Interactions
One of the most useful concepts introduced within ITIL Experience is the distinction between functional and relational interactions.
Functional interactions are the activities most organizations already track. Examples include:
- Submitting a service request
- Opening an incident
- Receiving a software update
- Requesting access to a system
- Completing onboarding activities
These interactions are generally measurable and visible, and organizations often maintain extensive reporting around them.
Relational interactions are different, as they involve the human elements surrounding the service relationship. Examples include:
- Building trust
- Managing expectations
- Reducing uncertainty
- Demonstrating competence
- Creating confidence
- Communicating effectively during disruption
These interactions are often more difficult to measure, yet they frequently have a greater influence on how services are perceived. A service provider may perform every functional interaction correctly while still damaging the overall relationship through poor communication or lack of transparency.
Why Organizations Get Blindsided
Many organizations focus heavily on operational metrics, tracking parameters such as:
- Availability
- Response time
- Resolution time
- Throughput
- Escalation rates
- SLA compliance
While these are valuable measurements that should absolutely be monitored, the challenge arises when organizations assume these metrics tell the entire story—they rarely do.
- Trust can decline long before operational metrics indicate a problem.
- Confidence can erode even while performance remains stable.
- Users can become frustrated despite excellent technical results.
By the time satisfaction surveys reveal an issue, the damage may already be significant, leaving organizations that monitor only technical performance surprised when users reject a service they believed was successful.
Understanding the Service Journey
Another important concept explored in ITIL Experience is the service journey. A service is not experienced as a single event, but as a sequence of interactions over time.
- A consumer’s experience begins long before they submit their first request—starting with marketing materials, onboarding activities, training sessions, or recommendations from colleagues.
- It continues through support interactions, change initiatives, incidents, upgrades, and everyday usage.
- Every stage influences the overall perception of the service.
Organizations that understand the complete journey are often better positioned to identify pain points, remove friction, and improve value realization by examining the entire experience from the stakeholder’s perspective rather than focusing on isolated transactions.
The Role of Communication
Few factors influence experience more than communication. Users generally tolerate problems better than uncertainty; an unexpected outage with clear communication is often less damaging than a minor issue accompanied by silence.
Effective communication helps stakeholders understand:
- What is happening
- Why it is happening
- What actions are being taken
- What outcomes can be expected
Poor communication creates anxiety, frustration, and distrust, meaning many experience failures can be traced not to the technical issue itself but to how information was shared throughout the situation.
AI, Automation, and Experience
As organizations increasingly adopt AI-enabled solutions, the relationship between automation and experience becomes even more important. The goal is not to automate everything, but to use the right tool for the right situation.
- Automation can improve consistency, reduce delays, and provide faster access to information.
- At the same time, poorly implemented automation can create frustration and damage trust.
Consider an AI chatbot that automatically closes incidents after a predetermined period of inactivity. From an efficiency perspective, ticket volumes decrease, resolution metrics improve, and workloads appear lower. However, if users feel their concerns are being dismissed or prematurely closed, confidence in the service may decline rapidly, meaning the organization improved operational metrics while simultaneously damaging the experience those metrics are intended to support.
Experience Is a Leading Indicator of Value
Ultimately, organizations do not invest in services simply to achieve operational targets; they invest in services to create value. Value is realized when consumers successfully achieve desired outcomes, which are influenced by trust, confidence, communication, and positive experiences.
- A technically excellent service that nobody wants to use delivers limited value.
- A service that users trust and embrace is far more likely to achieve its intended objectives.
This is why experience is becoming an increasingly important area of focus within modern service management.
Final Thoughts
Traditional service management has always emphasized reliability, availability, and performance as essential capabilities. However, organizations are increasingly recognizing that successful services require more than technical excellence alone:
- They require trust.
- They require effective communication.
- They require an understanding of stakeholder concerns, expectations, and experiences.
The organizations that excel in these areas are often able to identify issues earlier, improve adoption, strengthen relationships, and realize greater value from their services. These concepts form the foundation of the ITIL Experience qualification, which explores how organizations can better understand service relationships, stakeholder journeys, and the human factors that influence service success.
To learn more about ITIL training and certification pathways, visit our ITIL training page.