The Monday that looked fine

It’s Monday, 09:12, and your weekly service review is in the diary. Volume is steady. Resolution time is inside target. First-contact resolution looks healthy. CSAT is “acceptable”. The Jira Service Management dashboards you send to senior IT leadership are a wall of green.

Then your phone lights up. A director has been waiting since Thursday for a laptop that “should have been easy”. A finance colleague has gone through the same password-reset path three times and still can’t get into a critical system before month-end. A regional manager is polite in the ticket and furious in Teams.

Nobody is wrong about the numbers. The numbers just don’t describe Monday morning.

What the queue can’t tell you

I spend a fair amount of time owning workflows and SLAs in Jira Service Management and reporting volume, resolution time, FCR and CSAT upwards. Those numbers matter. They tell you whether the queue is coping, whether clocks are respected, and whether the desk is closing loops at a sustainable pace.

They don’t tell you whether the person on the other end of the ticket had a usable Monday.

FCR can look strong when the first queue touched the issue, even if the colleague still can’t do their job. CSAT can limp along on a survey sent after a polite close, while the lived experience was three contacts, two workarounds and an apology. An SLA clock stops when the ticket is resolved, and the annoyance carries on after it.

If you read my piece on the Watermelon Effect, you’ll know the colour problem already. This is about the service contract that keeps painting over it, so SLA, FCR and CSAT look fine while the person is still stuck.

What green hides

A healthy desk is more than a scoreboard. It’s a system that makes the same Monday less likely to come round again.

That’s where root cause analysis earns its place, as part of how you lead the desk and more than a post-mortem ritual. Working with Network, Security and Engineering on root causes has reduced repeat incidents in the teams I’ve led. There are fewer people explaining the same failure and fewer green tickets that reopen as anger in another channel.

A few things help in practice:

  • Track experience next to the clock. Pair SLA with a short set of XLAs: time to useful work, reopens, “I had to explain this twice”, and a read on frustration in the channels people actually use.
  • Read FCR honestly. Count first contact that fixed it for the person, not the first queue that touched the record.
  • Treat volume as a story. A spike after a change, or a category that keeps recurring, is fuel for RCA. It isn’t a badge of how busy you are.
  • Listen where the anger is. If Teams and hallway conversations are hotter than the survey, your CSAT sample is missing the people who matter most.

XLAs don’t replace SLAs. They complete them. The contract still needs a clock, and leadership still needs a mirror.

When the desk optimises for the clock

You can staff the rota, publish the SLA and celebrate green weeks, and still build a culture that rewards stopping the clock more than restoring the person. Analysts learn to resolve against the timer. Managers learn to defend the dashboard. Senior leaders learn that green means calm.

Nobody is being cruel there. It’s optimisation without a human check, and it’s easy to miss because the reporting looks so good. Treat the assumption that a green SLA means a good Monday like any other claim, and ask for evidence.

The other mistake is treating anger as noise. Reporting that ignores reopen rates, escalation tone and “same issue, new ticket” will keep your slides tidy and your reputation thin. Users don’t experience your queue. They experience whether they can work.

Try this week

Take last week’s SLA pack, the same FCR, CSAT and volume view you’d send upstairs. Then pick ten tickets that closed on time and ask:

  1. Did the colleague get useful work back on the first real contact, or only on the ticket’s first touch?
  2. Would they still be angry in Teams even though the clock stopped?
  3. Is the issue likely to recur, and is there an RCA owner, or only a closed status?

If any answer makes you uneasy, that’s the gap. Then add one experience metric to next week’s leadership pack: one XLA, one reopen or “explained twice” count, and one sentence on what the anger in the channels is telling you that the dashboard isn’t.