Written down and agreed out loud are not the same thing.
Your organisation has a chart showing who owns what. It was signed off, filed and possibly laminated. Nobody in the room has read it since. And when something breaks at an awkward hour, the first ten minutes are spent working out whose problem it is, not fixing it.
That gap is what service management accountability is really about. Not the document that says who owns a service, but whether the person named on it has agreed, out loud, that it’s theirs and knows exactly what happens next time it goes wrong.
Year-end planning is when organisations most often ask for help untangling who is accountable for something that has been “everyone’s responsibility” all year. The same conversation comes up every November, and it usually starts with a smoke alarm.
In this blog, we’ll explore:
- why accountability written down and accountability agreed out loud are two different things
- why automation and AI have made that gap more expensive, not more confusing
- the one question worth answering before next year’s plan gets signed off
The Smoke Alarm Nobody Owned
Every rented house seems to have exactly one smoke alarm that nobody wants to own. It’s fitted, it’s tested at the start of the tenancy, and after that everyone assumes it’s somebody else’s job. The landlord assumes the tenant will flag a problem. The tenant assumes the landlord has a maintenance schedule. The alarm sits on the ceiling quietly running down its battery until the day it starts chirping at 3am.
At which point everyone in the house suddenly has a very strong opinion about whose job it was.
Services work exactly the same way, and that’s where service management accountability quietly fails. They get launched with fanfare, handed over with a document, and then left on the ceiling. The battery runs down in the background: a certificate nobody renews, a supplier contract nobody reviews, an integration nobody monitors. Then something chirps.
Service Management Accountability: Written Down Isn’t the Same as Agreed
Most organisations can produce a document showing who is accountable for what. Responsibility matrices, service ownership lists, escalation paths: the paperwork usually exists, filed somewhere findable. What’s far rarer is a room full of the actual people named in that paperwork who have sat together and said, out loud, “yes, that’s mine, and I know what happens next time it fails.”
The difference matters because paperwork doesn’t answer a phone. When a request falls through the cracks, the chart doesn’t decide who picks it up. The person who has genuinely agreed, in a real conversation, that it’s theirs does. Everyone else finds a perfectly reasonable explanation for why it wasn’t quite their remit. That gap, between the name on the chart and the person who acts, is where service management accountability lives or dies.
Real service management accountability passes three tests: a named person is written down, that person knows they’re named, and they would act at 3am without being asked twice. Most organisations pass the first test comfortably and fail the other two without ever finding out.
If your most important service failed tonight, who, by name, would pick up the phone?
What Good Service Management Accountability Sounds Like
You can usually hear the difference within five minutes of a service review. Where service management accountability is real, people say “mine” without hesitating. They know which supplier to ring, which customer to warn first, and which decision they can make without asking anyone. When something goes wrong, the conversation starts with what happened, not with whose fault it was.
Where it isn’t real, the language changes. You hear “the team”, “the business” and “IT” doing a lot of work as the subjects of sentences. Questions get answered with a reference to a document rather than a name. And every incident review ends with an action to “clarify ownership”, which is the polite way of saying nobody owned it.
Weak service management accountability rarely shows up on a dashboard. It shows up in the minutes between the alert and the first person doing something about it.
Automation Has Made the Gap More Expensive, Not More Confusing
AI and automation haven’t made service management accountability harder to understand. They’ve made the cost of getting it wrong land faster and further away from where the decision was actually made.
A misconfigured automation rule can touch several hundred tickets before a human notices, in the time it used to take one person to make one mistake. A chatbot can give the same wrong answer to every customer who asks before lunch. The decision that caused it was made weeks earlier, by somebody configuring a rule, and the people dealing with the fallout often have no idea who that was.
That’s not a reason to slow down. The productivity case for automating service work is real and worth having. It is a reason to sort out service management accountability before go-live rather than during the first incident review, because the first incident review is a miserable place to discover that three departments each assumed somebody else owned the decision.
Which automated decision in your services has nobody’s name next to it?
The One Question Worth Asking Before Year-End Sign-Off
Planning conversations go better when they open with a single, deliberately uncomfortable question: when something breaks next year, who, by name and not by department, picks up the phone at 3am? Not who’s listed on the chart. Who would actually take the call.
Most rooms go quiet for a moment. That silence is the useful part, because it’s service management accountability being tested honestly for the first time. It’s the gap between what’s written down and what’s actually been agreed, made visible before it costs anyone anything.
What to do with the answer, in order of impact:
✓ Ask the question directly, by name, in the room, rather than as a hypothetical in a workshop exercise. People commit to things they say out loud in front of colleagues.
✓ Write down the answer people actually give, not the answer the organisation chart implies. Where those differ, you’ve found a risk.
✓ Put a renewal date on every “yes, that’s mine”. Service management accountability agreed once in 2024 has a battery too.
✓ Revisit it wherever automation or AI has been added to a decision path in the last twelve months, because that’s where the gap has moved fastest and where nobody has updated the chart.
None of this needs new governance software or a fresh framework rollout. It needs one honest conversation, ideally before the year starts rather than in the retrospective that follows the incident nobody quite owned. Teams that have the conversation find that service management accountability stops being a document and starts being a habit.
The Easy Way or the 3am Way
The smoke alarm in that rented house did eventually get fixed, at 3am, by whichever housemate was still awake and could reach the ceiling. Nobody enjoyed finding out that way whose job it had been all along. That’s service management accountability learned the hard way.
Run the sum on one gap: if an expired certificate nobody owned takes a 200-user service down for four hours, that’s 800 hours of lost work before anyone has opened the incident review.
Your plan for next year gets to find out the easy way, if the question gets asked before January rather than after the first outage. A Service Desk Assessment & Improvement starts in exactly this place, mapping who actually owns what against who the chart says owns it. If your team wants a common language for those roles afterwards, the ITIL Certifications cover service ownership in depth.
Whose battery is quietly running down in your organisation right now?
To find out more about PDCA Consulting’s expert consulting services either:
- Book 30-minute conversation directly: here
- Get in touch via the contact form here
- Connect with me on LinkedIn
Robert Pinnington
Turning struggling Service Desks & PMOs into high-performing ones
