Green Dashboards, Red Outcomes: How XLAs Fix The Gap Between SLA Compliance and Business Success

SLAs were built to measure whether a provider held up its end of the deal. By that standard, most providers are doing fine. The problem is that technical compliance and business success aren't the same thing, and the contract rarely accounts for the difference. When the metric is uptime but the pain is a broken workflow, the agreement becomes a watermelon: green on the outside, red on the inside. As enterprises shift to consumption-based models and layer AI into service delivery, the gap between technical metrics and business outcomes is getting harder to ignore. A service can be available, a model can respond, a platform can be running. But if the business process broke, the agreement didn't do its job.

Paul Neuman is the Founder and Head of Go-To-Market Services at IT Services Demystified. He spent more than two decades at HP, has authored two books on IT services contracts and AI governance, and created the Contractual Value Architecture (CVA), a framework for aligning commercial promises with measurable business outcomes. He has previously discussed how service agreements are evolving from technical checkboxes to business risk mitigation. On a recent episode of the The Data Wire: Beyond the IT Headlines podcast, SLAs, XLAs, and the Watermelon Dashboard: What Boards Must Ask Their IT Leaders, Neuman outlined why the metric enterprises rely on most tells them the least about whether the business actually succeeded.

The operational floor

SLAs aren't going anywhere, and Neuman is clear that they shouldn't. They remain essential for measuring response time, escalation paths, operational baselines, and supplier accountability. The problem is scope. "We usually use SLAs as proof of business value," Neuman said. "They are not designed for that." An SLA measures whether a provider delivered on a technical promise. It says nothing about whether the business outcome was achieved.

The distinction sharpens in the cloud. A hyperscaler can guarantee 99.99% availability, but that guarantee covers the infrastructure layer, not the application running on it. Recent cloud outages have demonstrated how a single provider failure can cascade across an entire ecosystem, costing enterprises billions even when individual component SLAs were technically met. Neuman pointed to a failure on his own assessment application as a practical example. "My website was working. The internet was working. But my customers were not able to run their assessment," he said. "That's where the difference really is important. Making the distinction between the SLA and the XLA."

The gap comes down to measurement vocabulary. Every organization tracks KPIs. Almost none track what Neuman calls KBIs, or key business indicators. "Everybody's talking about KPI, but nobody talks about KBI," he said. "That's probably what's missing. That's where the disconnect is." Without a metric that connects technical performance to business impact, the dashboard can stay green while the business bleeds.

When green means red

Experience level agreements are designed to close that gap. Where SLAs measure whether the provider met a technical threshold, XLAs measure whether the service actually mattered to the business. The concept originated as an internal counterpart to Net Promoter Scores: a way for IT to understand how users experience the service, rather than relying on operational metrics that can create the appearance of control without changing underlying behavior.

But Neuman draws a hard line between useful XLAs and surveys. "A useful XLA has to be tied to a real workflow. It must trigger governance action when it goes red. It must trigger investigation when it becomes yellow. If you can't act on an XLA, what you're doing is a survey." He used the Amazon purchase experience as an illustration. The XLA isn't whether the site is up. It's whether a customer can complete a purchase end to end, in a reasonable time, securely. That's the difference between measuring availability and measuring business function.

The end-to-end view introduces its own complexity. When multiple suppliers each handle a slice of the delivery chain, each one can report green while the total experience is red. A printer fulfills the order on time. A shipper delivers within their window. But the customer waited too long and the NPS is negative. "That's the perfect example of the watermelon dashboard," Neuman said. "It might be red end to end, even though some slices are green." The goal, he stressed, isn't to replace SLAs with XLAs. "Both have their own use and their own usage." The point is to connect them.

The partnership bible

Connecting them requires contractual architecture, and Neuman sees the contract itself as the most underused tool in the vendor-customer relationship. He calls it the partnership bible: the mechanism that aligns what the client expects with what the supplier can deliver. He developed his Contractual Value Architecture framework specifically to explain how a strong contract can still fail in execution when governance, accountability, and escalation paths aren't designed into the architecture from the start.

The failure mode he sees most often is absence. "You cannot imagine the number of customers who told me, 'I've been working with this supplier, and then I had an escalation and I didn't know how to handle it,'" Neuman said. "Why? Because it was not in the contract." Clear RACI assignments, defined swim lanes, and documented escalation procedures aren't optional governance overhead. They're the structural prerequisite for making accountability operational rather than aspirational.

The correction happens in the quarterly business review. Neuman sees the QBR as the point where the supplier's view and the customer's experience get reconciled. The supplier should ask whether they helped the client achieve their goals. The client should surface new needs and flag where perceived value has drifted from the original business case. "That's where you can realign," Neuman said. "The contract is a partnership bible, nothing else." Running a contract without these conversations, what he called operating on "free will," is the fastest path to failure.

The most successful contracts he's signed, out of close to 200 over his career, had one thing in common. "I was able to sit with my account execs in front of the customer, in front of the C-level, in front of IT, and say, 'What did we do right? Where did we fail? Having that open and honest conversation really helps both sides improve, make things better, run more smoothly, and at the end of the day, make the business achieve their goals more easily," said Neuman.