Urgent.News

What's breaking now, across thousands of outlets.

Tech

The end of SLAs: why experience is the new measure of IT success

SLAs can't capture the full picture — here's why experience is becoming IT's true success metric.

The end of SLAs: why experience is the new measure of IT success

In ten years, the distinction between Service Level Agreements (SLAs) and Experience Level Agreements (XLAs) will feel like a significant fifty-year gap. While SLAs have been around since the 1980s, XLAs are only now gaining traction. The upcoming ISO 20000-18 standard will further push the adoption of XLAs.

To comply with this new standard, organizations must now manage the digital experiences of both customers and users, incorporating Experience Management (XM) into their existing governance, management, and implementation processes. Demonstrating good digital experiences is no longer just a nice-to-have, but a critical factor in winning new contracts.

Though the concept of XLAs has been around, most organizations lack the knowledge to practically implement these changes. So, why bother with XLAs? The answer lies in the fact that SLAs and user experience are not the same. Even if a cloud application is technically available, if the user experience is poor, it won't be used. SLAs still matter, but they are no longer sufficient. Understanding whether a system is functioning is crucial, but knowing if the application is unresponsive for the user is equally important.

Measuring 'experience' can be challenging, as it's a broad term and difficult to measure if not defined. There are hundreds of metrics for experience measurement, generally falling into three categories: Technical Data (T-Data), Operational Data (O-Data), and Sentiment Data (X-Data). For ISO compliance, organizations need data from all three categories.

Technical Data, obtained from platforms like Nexthink DEX, provides complete visibility across every endpoint and interaction. This data helps in faster diagnostics and identifying root causes of issues, enabling preemptive and preventative IT.

However, a common mistake when implementing Digital Employee Experience (DEX) platforms is focusing on the platform's capabilities rather than understanding the immediate concerns and frustrations of individual business units. IT leaders should ask other business units about their top priorities, areas of friction, and what success looks like for them. By focusing on these aspects, IT can help eliminate root causes of digital friction, rather than solely focusing on technical capabilities.

XLAs represent both an opportunity and a challenge. Initially, many businesses view new regulations as a burden, but ISO 20000-18 and the growing role of XLAs also offer an opportunity to accelerate the shift from infrastructure to experience. This change requires a significant realignment across traditional roles, responsibilities, and metrics. Businesses that see the new standard as an opportunity to gain a competitive advantage will have a significant head start on those still relying on outdated IT models.

Written by urgent.news from TechRadar's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at techradar.com →

More in Tech

I built a real NTFS-level file locker in Python — no password needed to protect, and even I can't brute-force it

Most "file lock" apps on the market do one of two things: rename your file extension, or hide it in a folder. Both take about ten seconds to bypass with Windows Explorer's search bar.

  • ATLOCK v4.0 is Python-based file locker app for Windows
  • Manipulates NTFS ACL to block access, no password needed
  • Creator is 13-year-old developer, company aims for everyday software security

I Built Kafka From Scratch to Understand how it actually works

But Why?? I had used Kafka enough to know the terminology: topics, partitions, producers, consumers, replication. But knowing the pieces is different from understanding why they fit together the way…

  • Author builds Kafka-like message broker named kafka-lite from scratch
  • Development process broken into five stages focusing on log storage layer
  • Emphasizes importance of understanding storage layer implementation

More from Tuesday 1 September →