Skip to content

GUIDE · 4 MIN READ

IT service management KPIs that leaders should actually report

Twelve measures worth putting in front of leadership — and how to set targets that lead to decisions rather than debates.

DIGITAL CHRYSALIS · OCTOBER 2026

THE PROBLEM WITH MOST IT DASHBOARDS

IT service management produces more data than almost any other function. Every ticket, change, outage and request is timestamped. The temptation is to report all of it, and most IT dashboards do — dozens of charts, most of them green, few of them telling leadership anything they can act on.

A good leadership report is short. It shows a small number of measures that reflect what the business experiences, each with a target, a red threshold and a trend, and it explains every result that needs attention. This guide sets out twelve measures that do that well, and how to make them useful.

FOUR RULES FOR A MEASURE WORTH REPORTING

  1. 01

    It reflects something the business feels

    Availability of the services people use, how fast problems are fixed, whether changes break things. Not internal activity counts.

  2. 02

    It has a target and a red threshold

    A number without a target is trivia. A target without a red line leaves every review arguing about whether a miss matters.

  3. 03

    It shows movement

    This period against the last three to six. Leaders decide on direction of travel, not on single data points.

  4. 04

    Someone owns it

    A named role answers for the result and explains it when it turns red.

TWELVE KPIs WORTH REPORTING

Grouped by what leadership is really asking.

ARE OUR SERVICES WORKING?

  1. 01

    Availability of critical services

    Percentage of agreed service hours each critical service was available. Report per service, not as one blended number that hides the worst performer.

  2. 02

    Major incidents

    Count of major incidents in the period, with total business hours affected. One line on each: cause, impact, and the action taken.

  3. 03

    Repeat incidents

    Share of incidents linked to a known problem that has already occurred. A high figure means the organisation is fixing symptoms rather than causes.

HOW QUICKLY DO WE FIX THINGS?

  1. 01

    Mean time to restore service

    Average time from a service failing to its being usable again, for priority one and two incidents.

  2. 02

    Incident resolution within target

    Percentage of incidents resolved within the agreed time for their priority.

  3. 03

    First-contact resolution

    Share of contacts resolved without being passed on. It drives both cost and user experience.

ARE CHANGES SAFE?

  1. 01

    Change success rate

    Percentage of changes implemented without causing an incident or needing to be backed out.

  2. 02

    Emergency change rate

    Share of changes made as emergencies. A rising rate usually signals weak planning or unstable services.

ARE WE IMPROVING?

  1. 01

    Problem backlog age

    How long known problems have been open, especially those linked to major incidents.

  2. 02

    Improvement actions delivered

    Share of agreed improvement actions delivered on time.

WHAT DOES IT COST, AND IS IT VALUED?

  1. 01

    Cost per service or per user

    Unit cost, tracked over time, so investment decisions have a baseline.

  2. 02

    User satisfaction

    Survey score after resolution, with response rate shown so the score can be trusted.

ADD EXPERIENCE MEASURES

Traditional KPIs can all be green while users are frustrated: tickets closed on time but reopened, services up but slow, satisfaction surveys answered by few. Experience level agreements, or XLAs, measure how technology feels to the people using it.

  • —

    Experience score for key journeys, such as onboarding a new starter or requesting access.

  • —

    Productive time lost to IT issues, estimated per user per month.

  • —

    Sentiment trend from comments, not only scores.

  • —

    Reopened tickets, as a signal that "resolved" did not mean fixed.

Report a handful of XLAs beside the KPIs. Where the two disagree, the disagreement is usually the most useful finding in the report.

A green dashboard and an unhappy business means the dashboard is measuring the wrong things.

SETTING TARGETS AND RED THRESHOLDS

Set targets from what the business needs, not from last year's performance. Then set a red threshold below the target that triggers action. The space between the two is amber: watch, but do not escalate.

  • —

    Write the threshold down before the period starts, so nobody negotiates it afterwards.

  • —

    Require a one-line explanation and an owner for every red result.

  • —

    Review thresholds annually, or when a service changes significantly.

MAKE THE REPORT ASK FOR DECISIONS

The point of reporting to leadership is to get decisions: investment, priority, acceptance of a risk. End every report with the decisions required, each with options and the cost of delay. A report that only describes what happened is a record, not a management tool.

The ITIL Leadership Toolkit includes 24 KPIs and 8 XLAs with targets, red thresholds, RAG status and trend calculated in its workbook, and a 24-slide executive deck that ends with the decisions required. It is independent guidance, not affiliated with or endorsed by PeopleCert.

EXPLORE FURTHER

Digital Chrysalis © 2026

BUILD • TRANSFORM • EMERGE