Your performance review is next week. You’ve got a vague sense that you’ve done good work this year, but when you try to write it down, everything feels either too small to mention or too hard to quantify.

Meanwhile, your coworker always seems to walk out of reviews with raises and promotions. They don’t necessarily work harder than you. They just know how to talk about their work differently.

Here’s the uncomfortable truth: your performance review isn’t primarily about performance. It’s about perception, positioning, and playing a game most technical people were never taught. The good news is that it’s a learnable skill, and mastering it doesn’t require becoming someone you’re not.

Why IT Performance Reviews Feel Broken

Let’s address the elephant in the room: most IT professionals hate performance reviews. They feel arbitrary, political, and disconnected from actual work.

There’s a reason for this. Performance reviews were designed for roles with easily measurable outputs. Sales made quota or didn’t. Manufacturing produced X units with Y defect rate. IT work rarely fits this mold.

How do you measure “keeping systems running”? The absence of catastrophe isn’t sexy on a review form. How do you quantify “being the person everyone asks questions”? Or “preventing a security incident by catching something weird in the logs”?

This measurement problem creates two failure modes for IT professionals:

Underselling: You kept everything running smoothly, so there’s nothing dramatic to report. You default to listing tasks instead of achievements.

Speaking the wrong language: You talk about technical accomplishments that mean nothing to your manager or HR. “Optimized database queries” doesn’t translate to business impact.

Both modes lead to the same outcome: other people get the raises and promotions while you wonder what you’re doing wrong.

The Self-Assessment Mistake Most IT Pros Make

If you’re writing your self-assessment the week before it’s due, you’ve already lost half the battle.

The recency effect is brutal in performance reviews. Whatever happened in the last few weeks overshadows the rest of the year. That major project you shipped in February? Forgotten. The fire you put out in April that saved the company embarrassment? Barely remembered.

Your manager probably reviews dozens of people. They can’t remember everything you did, and honestly, neither can you. Not accurately.

Here’s what actually works: keep a running document throughout the year. Every time you ship something, help someone, learn something new, or get positive feedback, write it down. Takes 30 seconds. Saves you hours of reconstruction later.

If you haven’t been doing this, don’t panic. Start now. Check your email, Slack messages, ticket history, and Git commits. Look for patterns. What problems did you solve? What did people thank you for? What would have gone wrong if you weren’t there?

Translating Technical Work Into Business Impact

This is where most IT professionals stumble. You know the technical details of what you did. But reviews aren’t judged by technical people.

Bad self-assessment language:

  • “Migrated database to new server”
  • “Implemented monitoring solution”
  • “Wrote PowerShell scripts for automation”
  • “Resolved 347 tickets”

Better self-assessment language:

  • “Migrated production database with zero downtime, preventing potential $X revenue loss during transition”
  • “Implemented monitoring that caught 3 issues before they became outages, reducing after-hours calls by 40%”
  • “Automated account provisioning, reducing onboarding time from 4 hours to 15 minutes per new hire”
  • “Maintained 98% customer satisfaction rating while handling 30% more tickets than previous year”

See the difference? The second versions connect your technical work to outcomes someone outside IT can understand: money saved, time reduced, problems prevented, satisfaction improved.

You don’t need exact numbers for everything. Reasonable estimates work fine. “About 40%” is better than “some improvement.” But always tie your work to something the business cares about.

The Three Buckets Every IT Review Should Cover

Structure your self-assessment around three categories. This helps you avoid both underselling and rambling.

Technical Achievements

This is what you probably default to, so keep it tight. Focus on 3-5 major accomplishments, not a laundry list of every task.

For each achievement, answer these questions:

  • What was the situation or problem?
  • What did you specifically do?
  • What was the measurable outcome?

This is the STAR method (Situation, Task, Action, Result), and it works because it forces you to tell a complete story instead of just listing activities.

If you’ve earned any certifications or completed significant training, include that here. A CompTIA certification or AWS credential shows initiative beyond your daily responsibilities.

Collaboration and Communication

IT professionals often undersell this, but it matters enormously for advancement. Technical skills get you the job. Communication skills get you promoted.

Think about:

  • Cross-team projects you contributed to
  • Times you helped colleagues solve problems
  • Knowledge sharing (documentation, training, mentoring)
  • Interactions with stakeholders outside IT
  • How you handled difficult situations or challenging users

The person who quietly helps everyone is often invisible at review time. Don’t be invisible.

Growth and Learning

What have you gotten better at? What new skills have you developed? This signals that you’re not just maintaining your current role but preparing for bigger responsibilities.

Include:

  • New technologies you’ve learned
  • Processes you’ve improved
  • Stretch assignments you’ve taken on
  • Professional development activities

If you’ve been building a home lab, learning Python scripting, or working through platforms like Shell Samurai to sharpen your command-line skills, mention it. Self-directed learning demonstrates initiative.

Handling the “Areas for Improvement” Section

Nobody likes writing about their weaknesses. But this section is actually an opportunity if you handle it right.

What managers want to see:

  • Self-awareness (you can accurately assess your own gaps)
  • A growth mindset (you’re working on improving)
  • Professionalism (you don’t get defensive about feedback)

What kills your review:

  • Fake weaknesses (“I care too much about quality”)
  • Generic non-answers (“I need to keep learning”)
  • Blame-shifting (“I would improve if I had better tools”)

Here’s a framework that works: acknowledge a genuine area for growth, explain what you’re already doing about it, and state what you plan to do next.

Example: “I’ve recognized that my documentation habits could be stronger. I tend to solve problems quickly and move on without capturing the solution. This year I’ve started using our wiki more consistently, and I’m working toward documenting every significant troubleshooting session within 24 hours. I’ve also been studying documentation best practices to make my write-ups more useful for the team.”

This shows awareness, action, and initiative. Your manager now sees someone who improves themselves, not someone who needs to be fixed.

What to Do When You Disagree With Feedback

Sometimes you’ll get feedback you think is unfair. Maybe there’s context your manager doesn’t have. Maybe expectations weren’t clear. Maybe you genuinely dropped the ball but feel the criticism is disproportionate.

How you handle disagreement matters more than whether you “win” the argument.

Don’t:

  • Get visibly defensive or angry
  • Argue point by point in the meeting
  • Dismiss the feedback entirely
  • Bring up other people’s mistakes to deflect

Do:

  • Listen fully before responding
  • Ask clarifying questions to understand specifics
  • Take time to process before responding substantively
  • Provide context without making excuses
  • Focus on what you’ll do differently going forward

If you genuinely believe feedback is unfair or based on incorrect information, you can address it professionally. But frame it as providing additional context, not attacking the messenger.

“I appreciate that feedback. I want to make sure you have the full picture on the Project X timeline. The original deadline was extended twice due to requirements changes from the business side. Would it be helpful if I walked you through the change log?”

This gives your manager an opportunity to revise their assessment without making them defensive.

The Conversation Nobody Has: Asking for What You Want

Your performance review is one of the few times you have your manager’s undivided attention and an explicit invitation to discuss your career. Use it.

Many IT professionals walk into reviews hoping their work speaks for itself. They leave disappointed when it doesn’t translate into a raise or promotion.

Here’s the thing: your manager probably has more direct reports than they can closely track. They may not know you want to move into cybersecurity, that you’re interested in team lead responsibilities, or that you’re considering leaving if your salary doesn’t move.

You need to tell them.

Before the review, decide what you want. Not vaguely (“a raise would be nice”) but specifically:

  • What’s your target salary? What data supports it?
  • What role or responsibilities do you want next?
  • What resources or support do you need to get there?

If you want a raise, come prepared with market data. Sites like Glassdoor, levels.fyi, and Payscale can provide benchmarks. Our IT salary negotiation guide covers specific tactics that work.

If you want a promotion, understand what the next level requires. Ask directly: “What would I need to demonstrate to be considered for [senior/lead/whatever] in the next review cycle?”

If you’re thinking about leaving your job or feeling burned out, this is the time to signal that something needs to change.

The After-Review: What to Do Next

The review meeting is just the beginning. What happens next determines whether anything actually changes.

Get commitments in writing. If your manager promised to advocate for a raise, put you up for a promotion, or give you specific opportunities, follow up with an email summarizing what was discussed. This creates accountability and prevents “misunderstandings” later.

Set clear development goals. Based on your review, what specific things will you work on? What does success look like? When will you check in on progress?

Track everything. Start your running document for next year’s review immediately. Six months from now, you won’t remember what you committed to unless it’s written down.

Address unresolved issues. If you got feedback you disagree with, or didn’t get the outcome you wanted, don’t let it fester. Schedule follow-up conversations. Silence isn’t agreement; it’s just avoidance.

Common Performance Review Mistakes (and How to Avoid Them)

Waiting until the last minute: Your self-assessment reflects how much you value your own career. If you wrote it in 20 minutes the night before, that shows.

Focusing on tasks instead of impact: “I did X” matters less than “X resulted in Y.”

Being falsely modest: There’s a difference between arrogance and accurately stating what you accomplished. Err on the side of clarity, not humility.

Ignoring soft skills: Technical excellence is table stakes. What differentiates you is how you work with people, communicate, and contribute to the team beyond your individual tickets.

Not preparing for difficult conversations: If you know certain topics will come up, think through how you’ll address them ahead of time.

Treating it as an annual event: The best performance review is the culmination of year-round conversations. If this is the first time you and your manager have discussed your career, something’s wrong with your communication patterns. If you’re hoping to move from help desk to sysadmin or make a similar jump, you need to be having those conversations regularly.

Making Performance Reviews Work for Remote IT Professionals

If you work remotely, you face additional challenges. Your work is less visible. Casual interactions don’t happen organically. It’s easier to become just a name in Slack.

Combat this by:

Overcommunicating accomplishments. Send brief updates when you complete significant work. Your manager can’t see you working; they need to hear about it.

Being visible in meetings. Cameras on, voice heard. Silent presence doesn’t build reputation.

Creating documentation that showcases your thinking. Written communication is even more important for remote IT work. Clear, well-organized documentation of your projects and decisions creates a record of your contributions.

Building relationships beyond your immediate team. Cross-functional visibility matters more when you can’t rely on hallway conversations.

For more on advancing your IT career while working remotely, see our guide on getting promoted in remote IT roles.

The Performance Review as Career Strategy

If you’re strategic about performance reviews, they become more than annual administrative exercises. They become checkpoints in your career progression.

Every review should accomplish three things:

  1. Validate your current standing. Where do you stand relative to expectations? What perception does your manager have of your work?

  2. Clarify the path forward. What would it take to get to the next level? What gaps exist between where you are and where you want to be?

  3. Create accountability. What has your manager committed to? What have you committed to? Who’s responsible for what?

Approach reviews with this framework, and they stop being performance theater. They become actual tools for career development.

When Your Review Goes Wrong

Sometimes, despite preparation and good faith effort, reviews go badly. You get negative feedback you didn’t expect. You’re passed over for promotion. Your raise is less than you needed.

What then?

First, take time to process before responding substantively. Emotions in the moment rarely lead to good outcomes.

Second, separate the feedback from your feelings about it. Is there a kernel of truth, even if the delivery was poor? What can you learn, even if you disagree with the overall assessment?

Third, consider the source. Is this feedback consistent with what you’ve heard from others? Does your manager have visibility into your actual work? Are there organizational factors (budget, politics, timing) that might explain the outcome better than your performance does?

Finally, decide what you’re going to do about it. You have options:

  • Accept the feedback and change your approach
  • Provide additional context and request a reassessment
  • Start looking for a new role
  • Negotiate for specific conditions

The worst option is doing nothing and hoping things improve magically.

Your Pre-Review Checklist

Use this before your next performance review:

One month before:

  • Start gathering documentation of your accomplishments
  • Review previous review to check on committed goals
  • Identify 3-5 major achievements to highlight
  • Think through your development areas honestly

One week before:

  • Complete your self-assessment draft
  • Prepare talking points for each achievement
  • Decide what you want to ask for (raise, promotion, opportunities)
  • Gather market data if you’re discussing compensation
  • Review the salary negotiation strategies

Day of:

  • Review your notes
  • Come with questions prepared
  • Bring something to take notes with
  • Plan to listen more than you talk

After:

  • Send follow-up email summarizing key points and commitments
  • Start your tracking document for next year
  • Schedule any follow-up conversations needed

FAQ

How often should I be tracking accomplishments for my performance review?

At minimum, weekly. Some people do it daily at the end of work. The specific cadence matters less than the consistency. If you wait until review time to remember what you did, you’ll forget half of it and undersell the rest. Keep a simple running document, whether that’s a note on your phone, a text file, or an email to yourself.

What if my manager never gives feedback outside of the annual review?

That’s unfortunately common, but it’s not something you have to accept. Request regular check-ins, even brief ones. A monthly 15-minute conversation costs nothing but can prevent end-of-year surprises. You can also ask for feedback after specific projects: “Now that we’ve shipped X, I’d love to hear what went well and what I could do differently.”

Should I bring up salary in my performance review?

Yes, if you want one. Many companies separate “performance conversation” from “compensation conversation,” but you can still plant seeds. You can say something like, “I’d like to discuss compensation as part of this review cycle. Based on my contributions and market rates, I believe an adjustment is warranted. When’s the appropriate time to have that conversation in detail?”

How do I handle a review when I’ve genuinely underperformed?

Own it, but don’t wallow. Acknowledge what happened, demonstrate that you understand why it happened, and present a clear plan for improvement. Managers are generally forgiving of setbacks when people show self-awareness and initiative. What they don’t forgive is defensiveness, blame-shifting, or repetition of the same mistakes.

What’s the best way to ask for a promotion during a review?

Don’t ask for a promotion. Ask what you need to do to earn one. “I’m interested in moving into a senior role. Can you help me understand what distinguishes senior-level performance from where I am now? What would I need to demonstrate to be ready for that conversation in six months?” This approach shows ambition while putting the focus on concrete criteria.

Performance reviews are imperfect tools. They’re subject to bias, limited information, and organizational politics. But they’re also one of the few structured opportunities you get to advocate for yourself and shape your career trajectory.

The IT professionals who advance aren’t necessarily the ones who work the hardest or have the most technical skills. They’re the ones who know how to articulate their value in terms the organization understands.

That’s a skill, and like any skill, it improves with practice. Start with your next review.