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.
Average Ticket Resolution Time
The average time it takes from a user logging a ticket to you resolving it.
Target · Under 4 business hours for P3/P4 incidentsIf a user reports a printer issue (P3) at 9 AM, you'd aim to have it fixed or a workaround in place by 1 PM the same day. We're not talking about P1 outages here, those are different beasts.
First Contact Resolution Rate
The percentage of support tickets you resolve on the very first interaction, without needing to escalate or follow up multiple times.
Target · > 75%A user calls about a forgotten password, and you reset it and confirm access during that single call. That's a win. If you have to call them back three times, that's not first contact.
User Satisfaction (CSAT) Score
Feedback from users on your service after a ticket is closed, usually a simple 1-5 star rating.
Target · > 4.5/5.0 averageYou fix a slow laptop, and the user gives you 5 stars and a comment like 'Quick, friendly, and fixed it!'. That's what we're aiming for. Anything below 4 usually means there's something to learn.
SLA Adherence for Routine Tasks
The percentage of routine tasks (like new user setups, software installs) completed within their agreed-upon service level agreements.
Target · 95%+If new user accounts are meant to be ready within 24 hours of HR approval, you'll hit that target 95% of the time. We know things happen, but consistent misses are a problem.
System Health & Patch Compliance
Ensuring our endpoints and servers are patched and configured to security baselines, reducing vulnerabilities.
Target · 98% of managed devices compliant with latest security patchesMaking sure all Windows machines have the latest critical security updates applied within 7 days of release. A few stragglers are okay, but a big chunk means we're exposed.
Proactive Problem Identification
Your ability to spot potential issues before they become critical problems for users or systems.
- You'll be flagging recurring issues in team meetings, suggesting improvements to processes, or noticing unusual system behaviour in logs before a user even complains. For instance, you might notice a server's disk space is consistently low and proactively expand it, rather than waiting for it to crash.
Documentation Quality & Contribution
How well you document solutions, procedures, and system configurations, making it easier for others (and future you) to understand and troubleshoot.
- Your team members consistently refer to your documentation to solve problems. New starters can follow your guides without constant questions. You're regularly updating the knowledge base with new fixes or system changes. Honestly, good documentation is a lifesaver, especially at 3 AM.
Effective Communication & Collaboration
How clearly and patiently you communicate technical issues and solutions to non-technical colleagues, and how well you work with the wider IT team.
- Users tell your manager how helpful and clear you were. You're able to explain 'why the VPN is slow' in plain English, not technical jargon. You offer help to colleagues without being asked, and you're good at asking for help when you need it too.
Security-First Approach
Consistently considering security implications in all your work, from user access to system configurations.
- You question default permissions, suggest stronger MFA policies, or highlight potential vulnerabilities in new software. You're not just fixing the immediate problem, you're thinking about how to prevent the next security incident. This means you're always thinking about 'least privilege' and 'zero trust' in practice.
Ownership & Follow-Through
Taking full responsibility for your assigned tasks and projects, seeing them through to completion, even when they get tricky.
- You don't drop tickets just because they're hard. You follow up with users, chase vendors, and push internal teams until a problem is truly resolved. If you say you'll do something, you do it. This builds trust, both with users and with the rest of the IT team.