ITSM Metrics and KPIs: MTTR, First-Contact Resolution, SLA Compliance and Dashboards

“What gets measured gets managed”, but only if you measure the right things. ITSM generates plenty of data; the skill lies in choosing a small set of measures that show whether services are healthy, whether users are satisfied and where to improve. This lesson gives the main metrics, the formulas and the traps.

Metric, KPI and Target

  • A metric is anything you measure.
  • A KPI (key performance indicator) is a metric chosen because it shows progress toward an important goal.
  • A target is the level you want to achieve for a KPI.

Not every metric is a KPI. Tracking fifty numbers hides the five that matter.

Core ITSM Metrics

MetricFormulaWhat it tells you
MTTA (mean time to acknowledge)Total time from creation to first response ÷ number of incidentsHow quickly work starts
MTTR (mean time to restore or resolve)Total resolution time ÷ number of incidentsHow quickly service is restored
SLA complianceTickets resolved within target ÷ total tickets × 100Delivery against agreed times
First-contact resolution (FCR)Contacts resolved at first contact ÷ total contacts × 100Desk effectiveness and knowledge quality
Reopen rateTickets reopened ÷ tickets closed × 100Quality of fixes
Backlog and ageOpen tickets, and how long they have been openCapacity and hidden delays
Change success rateSuccessful changes ÷ total changes × 100Quality of change assessment (see Change Enablement)
Incidents caused by changeCount or share of incidents traced to a changeRisk of release practices
Repeat incidentsIncidents with a known cause that recurEffectiveness of problem management
CSAT (customer satisfaction)Positive responses ÷ total responses × 100How users feel about the support
Self-service resolutionIssues solved through portal or articles ÷ total issuesValue of knowledge and automation
Cost per ticketTotal desk cost ÷ tickets handledEfficiency, to be read with quality measures

A Worked Calculation

In a month, a desk records 240 incidents with a combined resolution time of 960 hours, of which 210 met their SLA targets and 12 were reopened. It receives 300 contacts, of which 132 are resolved at first contact. Of the 50 changes made, 46 succeeded.

MeasureCalculationResult
MTTR960 ÷ 2404 hours
SLA compliance210 ÷ 240 × 10087.5%
Reopen rate12 ÷ 240 × 1005%
FCR132 ÷ 300 × 10044%
Change success rate46 ÷ 50 × 10092%

Numbers like these only mean something against a target and a trend. An FCR of 44% may be low for a desk handling simple requests but healthy for one that supports complex engineering systems. Compare with your own history first.

Averages Can Mislead

If nine incidents take one hour and one takes ninety-one hours, the mean is ten hours, which describes none of them. Use the median and percentiles (for example, 90% of incidents resolved within six hours) alongside the average, and look at the longest-running tickets individually.

Balance the Scorecard

Any single measure can be gamed. Speed targets encourage closing tickets early; cost targets encourage cutting quality. Use a balanced set across four angles:

AngleExample measures
SpeedMTTA, MTTR, fulfilment time
QualityFCR, reopen rate, change success rate, repeat incidents
ExperienceCSAT, effort scores, complaints
EfficiencyCost per ticket, self-service share, automation rate

Dashboards That Work

  • Know the audience: executives want service health and trend; managers want queues and breaches; agents want their own work.
  • Show a few measures with trend lines and targets rather than dozens of tiles.
  • Use consistent definitions: write down when the clock starts and stops.
  • Pair every chart with a question: what will we do if this moves?
  • Review regularly and retire measures nobody uses.

Common Mistakes

  • Measuring activity (tickets closed) instead of outcomes (users able to work).
  • Rewarding a single metric, which invites gaming; remember that when a measure becomes a target it often stops being a good measure.
  • Comparing teams with different workloads using the same target.
  • Changing definitions mid-year, which breaks trends.
  • Reporting data and never acting on it.
Key takeaways
  • Choose a small number of KPIs linked to goals; not every metric is a KPI.
  • Know the formulas for MTTR, FCR, SLA compliance, reopen rate, change success rate and CSAT.
  • Use medians and percentiles as well as averages, and compare with your own trend.
  • Balance speed, quality, experience and efficiency to avoid gaming.

Related Lessons