As service and product management professionals, our role has always been to ensure that the services we deliver meet the quality standards our customers expect. For years, that quality has largely been described through Service Level Agreements (SLAs), availability targets, response times, and process maturity. These still matter, but they no longer tell the full story. Service quality today is just as much about how people experience our services as it is about whether the numbers look good on paper.
That is why experience management has become such an important part of modern service management. It encourages us to move beyond measuring activity and outputsand instead understand how people actually feel when they use our services. Are interactions clear and simple, and do people trust the service to work when they need it? Does the service genuinely help them achieve their goals? These questions sit right at the centre of value.
In ITIL v5, this thinking is built into the heart of the framework. The guiding principles, the four dimensions, the continual improvement model, and the 34 practices are there to help us design and operate services that create positive, consistent experiences, not just technically successful ones. More and more, this also means viewing services as products with clear ownership, lifecycle thinking, and a strong focus on user outcomes. A service might meet every other SLA and still feel poor to its users, and that gap between technical success and lived experience is something we can no longer ignore.
A simple example helps make the point. An incident may be resolved within the agreed four-hour SLA, so from a reporting perspective, everything looks fine. But if that user missed an important deadline during those four hours, their experience of the service is still negative. On paper, the service succeeded. In reality, it let them down. That is the difference between measuring outputs and understanding outcomes.
Recognising this, ITIL v5 places much greater importance on experience metrics. These are now a fundamental part of SLA design, ensuring we don’t just measure technical performance, but also user perception through tools such as Experience Level Agreements. When we listen to both operational and experience data together, we get a far clearer view of whether value is truly being delivered.
ITIL v5 also treats experience management as a capability in its own right, supported through learning and certification. This helps us continue the shift from measuring what IT does, to understanding what our users are able to achieve as a result. When service design, product ownership, operation, and continual improvement are shaped around the experiences people actually need, value becomes easier to see, explain, and protect.
Ultimately, service management has always been about partnership and trust. Experience management does not replace that purpose. It simply gives us the focus, language, and tools to pay closer attention to what really matters: the outcomes our services enable, and how people feel when they rely on them.
