Same ticket category reopening beside a root-cause board with a named owner and a closed loop

RCA That Actually Cuts Recurrence

The ticket that came back with a new number It’s Tuesday, 11:40. The major-incident bridge closed yesterday with a clean timeline, a polite “thanks everyone” and a promise that root cause would follow. Today the same symptom is back, under a different ticket number but in the same category, reported by the same annoyed colleague who has already told the story once. Your queue looks busy in the right way. Your problem record looks complete in the wrong way. There’s a five-whys slide, a parking-lot action reading “engage vendor”, and nobody has an owner and a date for when this failure stops happening on Monday mornings. ...

October 5, 2026 · 4 min · 816 words · Chido Dike
A stack of loose papers beside a navy folder with one sheet pulled out.

The Week the Auditors Arrive

Most of the year, the service desk is judged on speed. How fast the queue moves, whether the SLA is green, whether the person on the other end felt looked after. Then an audit shows up and the question changes. SOC 2, ISO 27001 and Cyber Essentials are different certificates, but they all want the same thing from the people who run the desk: proof of who joined, who left, and who can still sign in. ...

October 4, 2026 · 4 min · 793 words · Chido Dike
Named VIP path in an ITSM queue beside a side-channel Teams DM that never became a ticket

VIP Support Without Creating a Shadow Helpdesk

The ping that never became a ticket It’s Thursday, 18:22. An executive’s laptop won’t join the board pack on a hotel Wi-Fi network that has been hostile all week. Intune shows the device as healthy and the meeting starts in thirty-eight minutes. They do what busy people do when the portal feels slow and the stakes feel high: they message the Team Lead who “always sorts it”. You’re in the middle of a handoff to APAC, but you answer anyway. You reset, rejoin and reassure. The board pack opens. Nobody files a ticket, so there’s no RCA, no knowledge article and no SLA clock. All that exists is a quiet win in a private chat and an analyst who will have to be reachable at 22:00 again next time. ...

September 28, 2026 · 5 min · 924 words · Chido Dike
Green SLA dashboard beside a frustrated colleague on a Monday morning

When Green SLAs Still Mean Angry Users

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. ...

September 21, 2026 · 4 min · 762 words · Chido Dike
Global follow-the-sun support handoff across timezones

Follow-the-Sun Without Dropping the Baton

The ticket that travelled the world It’s 16:47 in London. A regional operations lead is in the middle of an incident: a line-of-business tool has gone quiet for a group of colleagues in the Middle East. She has already spoken to the Service Desk twice. The analyst has the logs, the timeline and a workaround that almost worked. Shift change is in thirteen minutes. The ticket goes to the overnight queue. The notes say “escalated, see comments”. The comments say “user will test in the morning”. ...

September 14, 2026 · 4 min · 743 words · Chido Dike