The scoreboard, honestly: the hard targets, how often each one is actually looked at,
and the quiet human signals that never make it onto a dashboard.
Mean Time to Resolution (MTTR) for P1/P2 Incidents
How quickly we get critical services back up and running after a major incident. This is a big one, as every minute counts when the business is impacted.
Target · Reduce MTTR for P1/P2 incidents by 15% quarter-on-quarter.If our average P1 resolution time was 60 minutes last quarter, you'd be aiming for 51 minutes this quarter. This comes from better processes, clearer runbooks, and tighter incident management.
Reduction in Recurring Incidents
The number of times the same or similar issue crops up again. Your job is to make sure we fix things properly, not just patch them up.
Target · Drive a 20% reduction in repeat incidents (defined as the same root cause leading to a new incident) year-on-year.If we had 10 incidents related to a specific database configuration last year, you'd be looking to get that down to 8 or fewer this year by fixing the underlying problem, not just the symptoms.
Knowledge Base Article (KBA) Contribution & Quality
How much you contribute to our shared knowledge and how good that knowledge is. Good KBAs mean faster resolution for everyone.
Target · Author or significantly update at least 5 impactful KBAs or runbooks per quarter, with a peer-review score of >90%.You've written a clear, step-by-step runbook for a common application restart, which has reduced resolution time for that issue by 30% for the frontline team. That's impactful.
Process Adherence Rate
How consistently our teams follow the incident, problem, and change management processes you've designed. It's no good having a great process if no one uses it.
Target · Maintain >90% adherence to critical process steps (e.g., post-mortem completion, change approval workflows).An audit shows 95% of P1 incidents had a post-mortem completed within 3 business days, and all changes went through the CAB. That means your processes are sticking.
Stakeholder Satisfaction with Incident Management
How happy our business stakeholders are with how we communicate and manage major incidents. It's about clear, calm, and timely updates.
- You'll be the first person key business leaders call during an outage, not because they're complaining, but because they trust you to provide the facts. They'll praise your clear, concise incident communications in feedback sessions. You're seen as the 'calm voice in the storm'.
Proactive Problem Identification & Resolution
Your ability to spot potential issues before they become major incidents and get them fixed. This is about being ahead of the curve.
- You're regularly bringing potential problems to the Problem Management team (or leading the charge yourself), backed by data. You'll have examples of 'near misses' that you prevented from becoming full-blown P1s because you saw the patterns emerging. You're not just reacting
- you're anticipating.
Mentorship and Team Development
How well you guide and develop the junior members of the service delivery team. You're not just doing the work; you're helping others do it better.
- Your direct reports will consistently talk about how much they've learned from you. You'll see them taking on more complex tasks confidently, and their ticket quality scores will improve. You're actively coaching, providing constructive feedback, and helping them navigate tricky situations.
Process Improvement Adoption
The extent to which your designed process improvements are actually adopted and valued by the teams using them. It's about practical, usable solutions.
- Teams will actively seek your input on how to improve their workflows. You'll see your new runbooks and procedures being consistently followed, and people will tell you they've made their lives easier. You're not just pushing out documents
- you're building solutions that stick.