There’s a term in service management for a dashboard that’s green on the outside and red on the inside: a watermelon SLA. Every ticket meets its resolution target, the monthly report looks excellent, and users still complain that IT is slow and that nothing ever really gets fixed. Both things are true at once, because the SLA is measuring the wrong thing.
When we take over service delivery, we look past the headline numbers to the signals that reveal how operations actually run.
A green SLA dashboard can hide a red user experience. Measure what users feel as well as what tickets do.
Signal 1: tickets that bounce
Look at how often a ticket is reassigned between teams before it’s resolved. Each handoff adds waiting time that resolution-time SLAs often don’t capture well, and each one tells the user nobody owns their problem. Ticket ping-pong is one of the clearest signs of unclear ownership and missing knowledge.
Signal 2: reopened and repeat tickets
A ticket closed to meet an SLA and reopened two days later is a failure counted as a success. Track reopen rates and repeat incidents for the same service. If they’re high, problem management isn’t happening; the team is treating symptoms on a loop.
Signal 3: time in queue versus time in work
Split resolution time into time a ticket sat waiting and time someone actively worked on it. In many environments the waiting dominates. That’s not a staffing problem as often as it’s a routing, triage or approval problem, and it’s fixable without hiring.
Signal 4: what never reaches the service desk
Mature operations push simple fixes closer to the user: self-service, a useful knowledge base, automated fulfillment for standard requests. If password resets and access requests still need a human to read a ticket, your most skilled people are doing your most repetitive work.
Signal 5: whether anyone trusts the CMDB
Ask an engineer where they look first during an outage. If the answer is a personal spreadsheet, the CMDB has failed. Start with the handful of services the business depends on most, map them properly and keep them current through discovery, rather than trying to model everything at once.
What changed things for a technology client
When we took on service delivery management for a technology company, the biggest gains didn’t come from new tooling. They came from making operations visible and owned: dashboards that gave leadership a real-time view of service health and backlog, regular service reviews that asked what was getting in users’ way, and automation of the repetitive work that was eating the team’s time. NPS and CSAT both rose as a result.
Measure experience alongside SLAs
- Reassignment count per ticket
- Reopen rate and repeat incidents per service
- Time waiting versus time worked
- Share of requests resolved through self-service or automation
- Satisfaction scores, reviewed alongside every SLA report
A mature ITSM practice isn’t the one with the greenest dashboard. It’s the one where users stop noticing IT, because things simply work.