SLAs or XLAs: What Serves Your Customer Best?

Introduction: Why Traditional Service Measurement Falls Short

For decades, Service Level Agreements (SLAs) have been the contractual backbone of IT and business services. They define targets such as system uptime, ticket resolution times, or average response speed. SLAs give providers and customers a clear framework for accountability, making them essential for risk management and operational reliability.

However, executives across industries have increasingly discovered that meeting SLA metrics doesn’t guarantee user satisfaction. The so-called “watermelon effect” often occurs: performance dashboards show all metrics in the green, yet end users feel frustrated, unproductive, or unsupported. This disconnect reveals a critical weakness: SLAs measure technical outputs, not real-world outcomes.

To address this, many organizations are now adopting Experience Level Agreements (XLAs). XLAs focus on the end-user’s perception and productivity. Instead of asking “Was the system available?” XLAs ask “Did the employee achieve their goal with minimal friction?” This shift reflects a broader trend: enterprises are moving from efficiency-driven metrics to experience-driven value indicators.

The rise of XLAs does not mean SLAs are obsolete. On the contrary, leading companies are combining the two. SLAs provide operational guardrails, while XLAs capture the business value of those operations. This article examines the evolution from SLAs to XLAs, comparing their frameworks, exploring global case studies, analyzing pros and cons, and outlining what truly serves customers best.

1 Understanding SLAs: Strengths and Limitations

SLAs (Service Level Agreements) codify the minimum acceptable performance of a service. They are contractual promises based on quantifiable measures:

Uptime and availability percentages.
Mean time to resolve (MTTR).
First response time.
Throughput or transaction rates.

The value of SLAs lies in their objectivity and enforceability. They provide binary accountability: either the service met the defined level or it did not. This clarity fosters trust, standardizes service quality, and ensures vendors deliver consistent outcomes. For industries like banking, telecom, and healthcare, SLAs remain vital to safeguard operations where failure can be costly.

Yet, the SLA framework is limited. It often promotes a checklist mentality: providers do just enough to hit targets, without addressing whether those targets deliver value to the customer. A helpdesk could close tickets within the agreed four hours, while employees still struggle with recurring disruptions. SLAs track what providers do, not how customers feel about it.

The result is that organizations meeting their SLAs can still see low employee productivity, customer dissatisfaction, and attrition. These gaps underscore why many leaders argue that SLAs are necessary but no longer sufficient in the digital era.

2. Understanding XLAs: A User-Centric Evolution

XLAs (Experience Level Agreements) shift the measurement lens from service outputs to customer and employee outcomes. Instead of measuring “time to resolution,” XLAs evaluate perceived ease, satisfaction, and business productivity impact.

Key elements of XLAs include:

Sentiment metrics: employee or customer satisfaction, NPS, or happiness index.
Productivity metrics: average lost work time per incident, ability to complete tasks without interruption.
Adoption metrics: whether new tools are being embraced or resisted.

Unlike SLAs, XLAs require continuous measurement. Feedback loops are built into daily interactions through pulse surveys, digital experience monitoring, or sentiment analytics. Rather than reporting quarterly on compliance, XLAs enable real-time visibility into how services are impacting users.

The cultural change is equally important. XLAs encourage collaboration and co-creation of success criteria with business stakeholders. They prioritize continuous improvement rather than mere penalty avoidance. In essence, XLAs ask: Are we delivering meaningful value and satisfaction, not just operational compliance?

3. SLA vs XLA: Quantitative Comparison

Aspect	SLA Focus	XLA Focus	Implication for Business Leaders
Primary Lens	Service provider performance	End-user experience and outcomes	Combines reliability with relevance.
Metrics Used	Uptime, MTTR, response time	Satisfaction scores, sentiment, productivity impact	Captures both efficiency and value.
Orientation	Inside-out (provider-driven)	Outside-in (user-driven)	Reflects customer-centricity.
Nature	Objective, binary, enforceable	Subjective, evolving, perception-based	Needs cultural alignment to succeed.
Goal	Meeting minimum contractual outputs	Driving continuous improvement in experience	Balances compliance with innovation.
Contract Style	Static, penalty-focused	Dynamic, reward-driven, collaborative	Encourages proactive partnerships.

Interpretation:
This table highlights the complementarity of SLAs and XLAs. SLAs provide a foundation of reliability – the minimum acceptable service performance. XLAs elevate the perspective to outcomes, ensuring those reliable services are experienced positively and productively. Organizations focusing only on SLAs risk blind spots in user sentiment. Those focusing only on XLAs risk overlooking operational rigor. The hybrid model – SLAs plus XLAs – ensures services are both dependable and valuable.

4. Why Enterprises Are Moving Toward XLAs

Several drivers explain why leading organizations supplement SLAs with XLAs:

Digital Transformation Demands – As companies digitize, productivity depends on seamless employee and customer experiences, not just system uptime.
Experience Economy – Customers increasingly judge brands by experiences, not just products. Employees expect consumer-grade IT at work.
Hidden Productivity Costs – SLAs mask downtime or frustration that erodes efficiency. XLAs expose these hidden losses.
Competitive Advantage – Experience becomes a differentiator when technical reliability is commoditized.
New Tools – Digital experience monitoring and sentiment analysis now make it possible to quantify experience continuously.

By focusing on outcomes rather than outputs, XLAs connect IT performance directly to business KPIs such as retention, engagement, and innovation capacity.

5. Case Study: Ahlstrom-Munksjö (Europe)

The European manufacturing firm Ahlstrom-Munksjö discovered that SLA compliance was not translating into happy employees. IT support dashboards were green, yet staff frequently lost hours to recurring issues. To address this, the company introduced XLAs targeting employee experience.

Within two years, the firm reported a 150% increase in employee happiness scores and a 57% reduction in lost productive time per employee. The initiative focused on identifying critical “moments that matter,” gathering continuous feedback, and closing the loop on dissatisfaction. IT agents began celebrating positive feedback alongside SLA compliance. By quantifying downtime reductions, the company could present XLAs as a business value driver rather than just a softer metric.

6. Case Study: Reckitt (North America/Europe)

Reckitt, a global consumer goods company, embedded XLAs into its IT service contracts. Alongside uptime targets, vendors were held accountable for employee satisfaction scores and experience metrics.

Results included a 52% rise in user satisfaction and the recovery of 250,000 hours of productivity annually. The company treated negative feedback as opportunities for improvement, redesigning processes such as VPN access and onboarding to directly target friction points. Reckitt demonstrated that aligning IT service metrics with business outcomes could transform IT from a cost center into a productivity enabler.

7. Case Study: Arcos Dorados (Latin America)

As the largest McDonald’s franchisee in Latin America, Arcos Dorados operates in over 20 countries with tens of thousands of employees. The company shifted to a self-service IT support model supported by XLAs that tracked “ease of help” and “speed to resolution.”

The result was a 20% reduction in IT service requests as employees increasingly solved issues via automated workflows and knowledge bases. User satisfaction rose as problems that once took hours were resolved in minutes. By centralizing service management across regions and emphasizing simplicity, Arcos Dorados improved operational efficiency and employee sentiment at the same time.

8. Case Study: Australian National University (APAC)

The Australian National University realized it was falling into the watermelon effect: SLA reports looked healthy, but user complaints remained high. By introducing XLAs and continuous feedback loops, the university transformed its IT culture.

Within a year, IT’s incident support NPS rose to 83, and average lost time per incident dropped from nearly 5 hours to just over 3. Initiatives such as clear communication, ticket ownership, and personal follow-ups on low scores reinforced trust. The shift signalled to staff and students that IT cared about their outcomes, not just its own metrics.

9. Pros and Cons of SLAs and XLAs

Advantages of SLAs:

Objectivity and contractual enforceability.
Clear operational accountability.
Protection in vendor agreements.

Disadvantages of SLAs:

Limited scope (outputs, not outcomes).
Potential for the watermelon effect.
Inflexibility in fast-changing environments.

Advantages of XLAs:

User-centric and outcome-driven.
Encourages continuous improvement.
Directly links IT performance to business value.

Disadvantages of XLAs:

Measurement complexity and subjectivity.
Lack of universal benchmarks.
Requires cultural change and executive sponsorship.

Conclusion: What Serves the Customer Best?

The debate is not SLAs versus XLAs – it is SLAs and XLAs together. SLAs remain essential for ensuring operational stability. XLAs ensure that stability translates into positive, productive, and valuable experiences for customers and employees.

Global case studies illustrate this duality: Ahlstrom-Munksjö, Reckitt, Arcos Dorados, and ANU all showed that adding XLAs produced measurable gains in satisfaction, productivity, and engagement. The organizations that thrive in the digital era will be those that combine technical reliability with human-centered outcomes.

For senior executives, the imperative is clear: embed XLAs alongside SLAs in contracts, dashboards, and IT governance. Make experience as important as uptime. Treat negative feedback as intelligence for improvement. Measure lost time as carefully as downtime. This approach not only protects performance but also fuels competitive differentiation, innovation, and loyalty.

In the end, what serves your customer best is not just that services are delivered, but that they are experienced as relevant, seamless, and empowering. The companies that recognize this balance will lead the next generation of digital transformation.

If this article resonated with you, feel free to share it — and let’s connect on LinkedIn for more insights and future posts: Ricardo Saltz Gulko

We invite you to subscribe to ECXO and be part of shaping our Global Business Network, now open for individual access: https://ecxo.org/individuals/

Ricardo Saltz Gulko, columns in several respected CX publications.