The SLA Was Met. The Service Failed.
The report is unambiguous. 99.7% against target. Green for the quarter, green for the year.
And yet the client is quietly furious, the team is exhausted, and two of your best people are updating their CVs.
Both things are true at once. The number was hit. The Service let everyone down.
How does an organisation hold both of those in the same hand and not notice the contradiction?
Because it measured the promise - and never looked at what was behind it.
An SLA Is Just a Promise
Strip away the acronym and the penalty clause, and a Service Level Agreement is a promise: we will respond within four hours, we will be available 99.9% of the time, we will resolve this by Friday.
So is an OLA. So is a pledge in a kickoff deck. So is the line a manager says in a steering meeting to make the tension go away.
They are all the same shape - a declaration, made by one party to another, about future behaviour. This is the useful lens from Promise Theory: a promise is voluntary, it is about your own conduct, and it only means something when someone is relying on it.
Once you see SLAs as promises rather than paperwork, the interesting question stops being “did we hit the number?” and becomes something far more revealing:
What, exactly, is keeping this promise?
Most organisations have never asked it.
The Unbacked Promise
Here is the failure almost nobody maps.
A promise lives in one place - a contract, a policy, a slide. What actually delivers the promise lives somewhere else entirely - a process, a Service, a person, a piece of infrastructure. And in most organisations, nothing connects the two.
The promise floats free. It has been made, it is being reported on, and if you go looking for the thing that keeps it, you find… a gap. Or worse, you find a single overworked person and a rota held together by goodwill.
Take a sanitised example. A client is promised Tier-1 response within four hours. The commitment is signed, tracked, and reported green every month. Ask the harder question - what delivers this? - and the answer is one experienced engineer who happens to check her phone on weekends. There is no second person. There is no documented path. There is a promise with nothing behind it, and the org has been quietly relying on luck and heroics to keep it.
A commitment with nothing delivering it is not a commitment. It is a hope with a deadline.
Why the Dashboard Can’t See It
The dashboard measures the promise. It cannot measure what backs it.
You can hit four hours for eighteen straight months on the strength of one person’s diligence, and every single month the report will say green. The metric is telling you the truth about the outcome and nothing at all about the exposure. The gap is invisible right up until the day she takes leave, or leaves, and then it is a catastrophe that “came from nowhere.”
It did not come from nowhere. It was an unbacked promise the whole time. The green just hid it - because green measures whether the promise was kept, never whether anything was keeping it.
This is the same illness as the watermelon metric: green on the outside, red in the middle. But the cure isn’t a better number. It’s making the promise itself into something you can inspect.
Make the Promise a Thing
The shift is small and it changes everything: stop treating a commitment as text buried in a document, and start treating it as a first-class object in your model of the organisation - something you can point at, question, and trace.
When a promise is a thing in its own right, four questions become answerable that were previously rhetorical:
- Who made it? (Not the logo on the contract - the actual accountable party.)
- Who is it made to?
- What Service or Outcome does it promise?
- What delivers it?
That last one is the whole game. When the commitment is connected to the thing that delivers it, an unbacked promise stops being invisible. It shows up as exactly what it is: a promise with a dangling end, pointing at nothing. You don’t discover it during the incident review. You see it the moment it’s made.
You don’t need a new tool to start thinking this way. You need to stop accepting a promise as delivered simply because it has been written down, and start asking - for every commitment that matters - show me what’s behind this. If the answer is a name and a hope, you have found a risk that no register captured, because no register knew the promise existed as a distinct thing.
Unbacked Promises Are Faith Debt
There is a human cost underneath the operational one.
Every promise your organisation makes is a small deposit or withdrawal on trust. A promise kept builds faith - the quiet confidence that lets people use the official path instead of routing around it. A promise broken withdraws it, and faith returns far more slowly than it leaves.
An unbacked promise is worse than a broken one, because it corrodes trust twice. First when it fails - suddenly, “inexplicably.” And again when everyone realises there was never anything holding it up, and starts to wonder what else is being reported green with nothing behind it.
A promise met by heroics is borrowed faith. A promise with nothing behind it is a debt you simply haven’t been billed for yet.
The Challenge
Your dashboard is telling you which promises were kept.
It is not telling you which ones are being kept by luck, by one person, or by nothing at all.
What is actually keeping your promises?
Go find one commitment that matters - an SLA, a pledge, a line in a plan - and trace it to the thing that delivers it. If you can’t, you haven’t found a reporting gap. You’ve found the next crisis, early enough to do something about it.
If this piece changed how you look at a green dashboard, I’d love to hear it - comment, follow, or share it with someone who owns an SLA they’ve never questioned.