It’s that time of year. Your manager sends over the self-evaluation form, and suddenly you’re staring at a blank document trying to remember what you did for the last twelve months.

You fixed things. Lots of things. You kept systems running. You answered tickets. You probably saved the company from at least one disaster that nobody noticed because, well, you prevented it. But how do you write that in a way that matters to someone who doesn’t know the difference between a VLAN and a VPN?

This is the fundamental problem with IT performance reviews: your best work is invisible. When everything runs smoothly, it looks like you’re doing nothing. When something breaks and you fix it at 2 AM, you’re a hero for about 48 hours before everyone forgets.

Here’s how to document your technical impact in language that resonates with management—complete with phrases you can adapt for your own review.

Why IT Performance Reviews Feel So Painful

The Visibility Problem

Most IT work happens behind the scenes. You don’t close sales. You don’t ship products. You maintain the invisible infrastructure that allows everyone else to do those things.

When a network runs at 99.99% uptime, nobody congratulates you. When it goes down for fifteen minutes, you field complaints for weeks. This asymmetry makes self-evaluation maddening. You’re essentially trying to prove the value of prevention—something that, by definition, never happened because you stopped it.

The Metrics Translation Problem

You know what you accomplished. You migrated 47 servers to the cloud. You automated a deployment process that used to take three hours. You reduced ticket resolution time by 40%.

But does your manager understand why that matters? Technical metrics need translation. “Reduced average ticket resolution time from 4 hours to 2.4 hours” sounds better than “closed tickets faster,” but the real impact statement is: “Saved approximately 120 hours of employee wait time per quarter, reducing productivity losses across the organization.”

If you’re struggling with communicating technical value to business stakeholders, you’re not alone. It’s a skill that most technical training completely ignores.

The “But That’s Just My Job” Mindset

Technical people tend to undersell their contributions. You think, “Of course I patched the servers—that’s what I’m supposed to do.” But the difference between doing something adequately and doing it well deserves documentation.

There’s a difference between:

  • “Maintained server security” (vague, sounds like baseline competence)
  • “Implemented zero-day patch for CVE-2026-XXXX across 127 production servers within 6 hours of disclosure, preventing potential exploitation during active threat window” (specific, shows urgency and impact)

Both describe “patching servers.” One sounds like you showed up to work. The other sounds like you actively protected the organization.

How to Quantify IT Work (When Numbers Feel Impossible)

Not everything has obvious metrics. You can’t always point to revenue generated or costs saved. But you can almost always quantify something.

The Four Questions Framework

For any accomplishment, ask yourself:

  1. How many? (servers, users, systems, tickets, projects)
  2. How fast? (time saved, deployment speed, resolution time)
  3. How much? (cost avoided, budget managed, resources saved)
  4. How reliable? (uptime percentage, error reduction, SLA compliance)

Let’s apply this to common IT scenarios:

Scenario: You set up new user accounts

  • Weak: “Onboarded new employees”
  • Quantified: “Provisioned accounts for 43 new employees across Q2, completing 100% within the target 24-hour SLA”

Scenario: You answered help desk tickets

  • Weak: “Resolved user issues”
  • Quantified: “Resolved 847 support tickets with 94% user satisfaction rating, averaging 2.1-hour first response time against 4-hour SLA target”

Scenario: You kept systems running

  • Weak: “Maintained server infrastructure”
  • Quantified: “Maintained 99.97% uptime across 34 production servers, exceeding 99.9% SLA target while reducing unplanned downtime incidents by 62% year-over-year”

When You Genuinely Don’t Have Numbers

Sometimes you really don’t have metrics. Maybe you worked on a long-term project that hasn’t shipped yet. Maybe you spent months supporting other teams. Maybe you’re in a role where success isn’t easily measurable.

In these cases, focus on:

  • Scope and complexity: “Led migration of legacy CRM system affecting 400+ users across 6 departments”
  • Stakeholder feedback: “Received commendation from VP of Sales for rapid response during critical system outage”
  • Process improvement: “Documented 12 previously tribal-knowledge procedures, reducing onboarding time for new team members”
  • Risk mitigation: “Identified and addressed security vulnerability before it could be exploited, avoiding potential data breach”

The goal isn’t to invent numbers. It’s to provide context that demonstrates the significance of your work.

Performance Review Phrases by IT Role

Here are role-specific phrases you can adapt for your self-evaluation. Take what applies, modify the numbers to match your reality, and use them as starting points.

Help Desk & IT Support

Ticket Performance:

  • “Resolved [X] support tickets while maintaining [Y]% customer satisfaction rating”
  • “Achieved first-call resolution rate of [X]%, exceeding team average of [Y]%”
  • “Reduced average ticket escalation rate from [X]% to [Y]% through improved first-tier troubleshooting”
  • “Mentored [X] junior team members, resulting in [Y]% improvement in their resolution metrics”

User Impact:

  • “Supported [X] end users across [Y] departments with consistent [satisfaction score] feedback”
  • “Implemented self-service knowledge base articles that deflected approximately [X] tickets per month”
  • “Coordinated equipment refresh for [X] users with zero productivity disruption”

Process Improvement:

  • “Created [X] standard operating procedures that reduced average onboarding time by [Y] days”
  • “Identified recurring issue pattern affecting [X] users, implemented permanent fix that eliminated [Y] monthly tickets”

If you’re looking to transition from help desk to a sysadmin role, documentation like this shows you’re already thinking at a higher level.

System Administration

Infrastructure Management:

  • “Managed [X] servers across [production/development/test] environments with [Y]% uptime”
  • “Executed [X] patching cycles with zero unplanned downtime, maintaining compliance with security requirements”
  • “Reduced infrastructure costs by [X]% through resource optimization and decommissioning unused systems”

Automation & Efficiency:

  • “Automated [X] manual processes using [PowerShell/Bash/Ansible/Python], saving approximately [Y] hours per month”
  • “Implemented infrastructure-as-code for [X] deployment processes, reducing provisioning time from [Y hours] to [Z minutes]”
  • “Created monitoring dashboards that reduced mean-time-to-detection for critical issues by [X]%”

For scripting examples and approaches, check out our Python for system admins guide or Bash scripting tutorial.

Project Delivery:

  • “Led [migration/upgrade/implementation] project affecting [X] users, completing on schedule and under budget”
  • “Coordinated with [X] teams to execute datacenter migration with [Y]% planned downtime window”
  • “Implemented disaster recovery solution, achieving [X] RTO and [Y] RPO targets”

Network Engineering

Network Performance:

  • “Maintained network availability of [X]% across [campus/WAN/datacenter] infrastructure”
  • “Reduced network latency by [X]% through traffic optimization and QoS implementation”
  • “Supported [X] concurrent users across [Y] sites with zero unplanned network outages”

Security & Compliance:

  • “Implemented firewall changes supporting [X] business requests while maintaining security posture”
  • “Executed quarterly access reviews covering [X] network devices, achieving 100% compliance”
  • “Responded to [X] security incidents with average containment time of [Y] minutes”

Infrastructure Growth:

  • “Designed and deployed network infrastructure for [X] new locations, supporting [Y] users”
  • “Upgraded core switching infrastructure, increasing available bandwidth by [X]% while reducing hardware footprint”

Looking to formalize your network skills? Our CCNA study guide and Network+ vs CCNA comparison can help you plan your certification path.

Cybersecurity

Threat Management:

  • “Analyzed and responded to [X] security alerts, with [Y]% confirmed as true positives requiring action”
  • “Reduced mean-time-to-respond for critical security incidents from [X hours] to [Y hours]”
  • “Conducted [X] threat hunting exercises, identifying [Y] previously undetected indicators of compromise”

Vulnerability Management:

  • “Managed vulnerability remediation across [X] systems, reducing critical/high findings by [Y]% year-over-year”
  • “Coordinated patching for [X] zero-day vulnerabilities with average remediation time of [Y] hours”
  • “Implemented vulnerability scanning coverage across [X]% of infrastructure assets”

Security Program:

  • “Developed and delivered security awareness training to [X] employees, reducing phishing click-through rate by [Y]%”
  • “Authored [X] security policies/procedures, achieving compliance with [framework/regulation]”
  • “Led security assessment for [X] vendor relationships, identifying [Y] risk items requiring remediation”

If you’re building toward a security career, check out our cybersecurity career path guide and SOC analyst career guide.

DevOps & Cloud Engineering

Deployment & Reliability:

  • “Managed [X] production deployments with [Y]% success rate and zero rollbacks”
  • “Reduced deployment time from [X] to [Y] through CI/CD pipeline improvements”
  • “Maintained [X]% uptime for production services supporting [Y] daily active users”

Automation & Infrastructure:

  • “Implemented infrastructure-as-code using [Terraform/CloudFormation/Pulumi], managing [X] cloud resources”
  • “Created [X] automated runbooks that reduced incident response time by [Y]%”
  • “Containerized [X] applications, reducing resource utilization by [Y]% while improving scalability”

For automation skills development, our Ansible tutorial, Terraform for beginners guide, and Docker for beginners cover the fundamentals.

Cost Optimization:

  • “Identified and eliminated [X] in monthly cloud waste through resource right-sizing and reserved instance planning”
  • “Implemented auto-scaling policies that reduced compute costs by [Y]% while maintaining performance SLAs”
  • “Negotiated enterprise discount program, achieving [X]% savings on cloud spend”

Addressing Weaknesses (Without Self-Sabotage)

Most self-evaluations ask you to identify areas for improvement. This section trips people up. You don’t want to invent problems, but “none” makes you look arrogant or lacking self-awareness.

The Growth-Focused Framework

Frame weaknesses as growth opportunities with plans already in progress:

Instead of: “I need to improve my scripting skills”

Write: “Expanding automation capabilities through structured PowerShell/Python development. Currently enrolled in [course/certification] with goal of automating [specific process] by Q3.”

Instead of: “I struggle with presenting to non-technical audiences”

Write: “Developing executive communication skills to better translate technical metrics into business impact. Applied these skills during [specific presentation], receiving positive feedback on clarity of ROI explanation.”

Safe Categories for Improvement

These areas are universally acceptable to acknowledge:

  • Certifications you’re pursuing: “Working toward [cert] to deepen [skill area] expertise”
  • New technologies you’re learning: “Building proficiency in [cloud platform/tool] to support upcoming [project]”
  • Leadership skills as you grow: “Developing mentorship capabilities to support team growth” (especially relevant if you’re moving toward IT management)
  • Cross-functional collaboration: “Expanding partnerships with [team] to improve [process]”
  • Documentation practices: “Strengthening documentation for procedures to improve knowledge transfer”

The key is pairing every weakness with an action you’re taking to address it.

Goals for Next Review Period

Most performance reviews ask what you plan to accomplish in the coming year. This section matters for your career trajectory—it’s essentially your negotiating position for the next review cycle.

Make Goals SMART, But Also Strategic

You’ve probably heard of SMART goals (Specific, Measurable, Achievable, Relevant, Time-bound). That’s table stakes. The strategic layer is choosing goals that:

  1. Align with organizational priorities you’ve heard leadership mention
  2. Position you for your next role (whether that’s a promotion or lateral move)
  3. Involve visibility to people who make decisions about your career

Example weak goal: “Learn more about cloud technologies”

Example SMART + strategic goal: “Achieve AWS Solutions Architect Associate certification by Q3 to support organization’s cloud migration initiative, enabling me to take technical lead role on Phase 2 deployment”

This goal is measurable (certification), time-bound (Q3), and explicitly connects to organizational priorities (cloud migration) and your career growth (technical lead role).

Goals That Set Up Salary Conversations

If you want to negotiate a raise at your next review, your current goals should set up that conversation:

  • “Take on [specific expanded responsibility] to demonstrate readiness for senior-level position”
  • “Lead [project type] independently to demonstrate [leadership capability]”
  • “Reduce [measurable cost/time metric] by [amount] through [initiative]”

When you accomplish these and document them, you have concrete evidence for compensation discussions.

The “Brag Document” Approach

Here’s the real solution to the annual review problem: don’t wait until review season to remember what you did.

Keep a running “brag document” throughout the year. Every time you:

  • Complete something significant
  • Receive positive feedback
  • Solve a difficult problem
  • Help a colleague
  • Learn something new
  • Avoid a potential disaster

…add a quick note to your document with the date and relevant details.

When review time comes, you’re not reconstructing your year from memory. You’re selecting highlights from a documented record.

What to Track

Your brag document should capture:

  • Completed projects with scope and outcome
  • Problems solved with complexity and impact
  • Positive feedback (copy/paste actual quotes)
  • Metrics (screenshot dashboards when you hit milestones)
  • Training completed (courses, certifications, conferences)
  • Mentorship activities (who you helped, what they accomplished)
  • Process improvements (before/after comparison)

This practice is especially valuable if you work remotely, where your accomplishments are less visible to colleagues and management.

Tools That Work

You don’t need anything fancy:

  • A simple text file in your personal folder
  • A private document (not on your work computer, in case you switch jobs)
  • An email folder where you forward yourself accomplishments
  • A notes app like Obsidian, Notion, or even Apple Notes

The tool matters less than the habit. One line per accomplishment, updated weekly.

Sample Complete Self-Evaluation

Here’s a condensed example pulling the approaches together. Adapt the role, numbers, and specifics to your situation:

Key Accomplishments This Review Period:

Managed 34 production servers across three environments with 99.97% uptime, exceeding our 99.9% SLA target. Reduced unplanned downtime incidents by 62% year-over-year through proactive monitoring improvements and predictive maintenance.

Automated backup verification process using PowerShell, reducing manual verification time from 4 hours weekly to 15 minutes. This freed approximately 200 hours annually for higher-priority work.

Led migration of file services to SharePoint Online for 280 users across 4 departments. Completed two weeks ahead of schedule with zero data loss and positive feedback from department heads regarding minimal disruption.

Served as technical lead for security incident response in March, coordinating remediation across infrastructure team within 4-hour window. Post-incident review identified no process gaps.

Mentored two junior team members on Active Directory administration and documentation practices. Both achieved independent proficiency within 3 months, enabling better coverage rotation.

Areas for Development:

Expanding cloud infrastructure expertise to support organizational shift to hybrid environment. Currently completing AWS Solutions Architect certification with expected completion by Q3 2026.

Developing cross-functional communication skills to better present infrastructure metrics to business stakeholders. Applied improved approaches during quarterly business review presentation, receiving positive feedback on clarity.

Goals for Next Review Period:

Complete AWS Solutions Architect Associate certification to support Phase 2 cloud migration (Q3 2026).

Reduce infrastructure costs by 15% through resource right-sizing and reserved capacity planning (measurable quarterly).

Document remaining tribal-knowledge procedures (12 identified), reducing onboarding time for new team members by 25%.

Take technical lead role on disaster recovery test exercise, demonstrating readiness for expanded responsibilities.

Common Mistakes to Avoid

Being Too Vague

“Supported the team” doesn’t tell anyone anything. What did you support? How? What was the outcome?

“Helped reduce incidents” is better than nothing, but “Implemented monitoring alerts that identified 47 issues before user impact, reducing reported incidents by 31%” tells a story.

Underselling Major Accomplishments

That migration project that consumed three months of your life? It probably deserves more than one sentence. If something was complex, challenging, or high-stakes, explain why.

“Completed server migration project” vs. “Led migration of 47 legacy servers to cloud infrastructure across 6-month timeline. Coordinated with 4 vendor partners, maintained zero unplanned downtime during transition, and delivered project 3 weeks ahead of schedule. Migration reduced annual infrastructure costs by approximately $180K.”

Overselling Minor Tasks

The flip side: don’t pad your review with routine work presented as accomplishments. Answering emails is not an accomplishment. Attending meetings is not an accomplishment. These are baseline job functions.

Focus on what you did beyond showing up.

Ignoring Soft Skills

Technical metrics matter, but if you demonstrated communication skills, leadership, mentorship, or cross-team collaboration, document it.

“Served as primary point of contact for vendor relationship” demonstrates communication and ownership.

“Coordinated with development team to improve deployment process” demonstrates collaboration.

“Trained new team member to independent proficiency in 6 weeks” demonstrates mentorship.

Writing at the Last Minute

You’ll forget things. You’ll undersell yourself. You’ll rush through sections that matter for your career.

If nothing else, spend 15 minutes brainstorming accomplishments before you start writing. Better yet, keep that brag document current.

Using Your Review for Career Growth

The self-evaluation isn’t just paperwork. It’s documentation you can reference when:

  • Asking for a raise: “As documented in my performance review, I achieved X, Y, and Z…”
  • Interviewing for new roles: Your accomplishments are pre-written in quantified language
  • Updating your resume: Bullet points ready to go
  • Planning your career: Patterns emerge when you review years of documented work

If you feel like you’re stuck in your career, reviewing past accomplishments can help identify whether you’re growing or repeating the same year multiple times.

FAQ

How long should a self-evaluation be?

Match your organization’s culture. If they provide a word limit or form fields, fill them appropriately. If it’s open-ended, 1-2 pages is typically sufficient. Quality matters more than length—specific, quantified accomplishments beat generic paragraphs.

What if I genuinely don’t have metrics?

Focus on scope, complexity, and qualitative impact. “Supported 12-month ERP implementation affecting 400 users” provides context even without hard numbers. Describe what made the work challenging and what the outcome was.

Should I mention failures or mistakes?

Generally, no. Unless your manager specifically asks about challenges or lessons learned, focus on accomplishments and growth. If you must mention a setback, frame it as what you learned and how you applied that lesson to subsequent work.

How do I talk about achievements that were team efforts?

Use “contributed to” or “collaborated on” for team accomplishments, then specify your particular role: “Contributed to datacenter migration project, specifically owning networking configuration and cutover coordination.” Don’t claim sole credit, but do articulate your specific contribution.

My company doesn’t do formal reviews. Should I still document accomplishments?

Absolutely. Keep a brag document for yourself. When you want to discuss a raise, apply for internal positions, or update your resume for external opportunities, you’ll have specific examples ready. Documentation protects your career regardless of whether your employer requires it.

Moving Forward

The performance review shouldn’t be the only time you think about your career trajectory. Regular self-assessment—even quarterly—helps you spot patterns, identify skill gaps, and ensure you’re growing rather than just maintaining.

If you’re finding it hard to quantify accomplishments, that might signal something worth examining. Are you in a role where impact is genuinely hard to measure? Are you doing important work that isn’t valued? Are you ready for a change?

The metrics you struggle to produce for a review are often the same metrics that demonstrate your value to the organization. If you can’t articulate your impact, it’s worth asking whether the role is positioning you where you want to go.

For now, though: fill out that self-evaluation. Be specific. Use numbers. Document what you actually did. Future you will appreciate it.