Case study / Service reliability and ownership
When recurring incidents kept coming back
In an earlier IT operations leadership role, I inherited an organization that restored services and closed tickets but kept encountering the same failures. The service desk struggled with incoming demand, and cross-team incidents routinely traveled through several management layers before the right specialists could work together. The organization was busy, but customers could not depend on the same problems staying resolved.
Give the business service an owner
Work was divided primarily by technology specialties. A team could own the servers, networks or applications involved in an incident while nobody owned the complete service experienced by the business. Difficult incidents crossed these boundaries and escalated through management because the operating structure did not support direct cross-functional resolution.
The incident process focused on getting systems working again. Recurrence prevention had weaker ownership. Root-cause findings did not reliably become assigned remediation, and queue rules, interruption criteria and work-in-progress limits differed between teams. Some tickets could close without the underlying condition being addressed.
I began with the actual work: recurring incidents, routine service demand, projects and dependencies competing for the same specialists. The intervention needed to make priorities, cross-team decisions and prevention work explicit in everyday operations.
Replace repeated escalation with a working service model
We identified roughly 60 services and established accountable owners. That gave incidents, requests, problems and changes a business-facing frame rather than relying only on technology towers. Teams agreed how work entered their queues, when an interruption was justified, and what remained open after service restoration.
Weekly problem reviews created a recurring decision point for preventing known failures. Root-cause recommendations had owners and follow-through. Peers from different technical teams worked together without requiring executives to relay routine decisions up and down management chains. Service owners had the responsibility to assemble the right people and keep preventive work visible until completion.
The service catalog, configuration data and ServiceNow workflows supported the operating model. Service definitions and decision rights were developed alongside the system, so the platform represented the work rather than becoming a substitute for it.
Reliability improved while capacity was constrained
Within six months, the service-desk answered rate reached 99.6%, up from about 58%. Across the wider operating turnaround, major incidents were down 60% year over year and mean time to resolution across incidents, including non-major incidents, fell 79%.
Request-resolution time also fell 53%, and the concurrent ticket backlog declined from 999 to 206. These measures captured more than quicker incident closure: demand was getting assigned, resolved and prevented from repeatedly returning to the queue.
The organization also reduced staffing from roughly 65 to 42 during a broader restructuring. Improved service ownership, prioritization and recurring follow-through helped maintain better operating results despite the capacity constraint.
For a business dealing with recurring outages, extended queues and executive escalation, the diagnostic question is whether the right people can make and sustain service-level decisions. A reliable platform helps; the operating model determines whether the failures stay fixed.
Do you recognize this operating problem?
Start with the decision or result that is currently stuck.
