How should IT professionals prepare for their performance review?
IT professionals should prepare for performance reviews by documenting their accomplishments from the full review period (not just recent months) with specific metrics and project outcomes, reviewing their job description and any goals set at the start of the period to assess and demonstrate achievement, gathering any peer feedback and manager praise they have received throughout the year, and preparing a specific compensation discussion if they are seeking a raise. The most common performance review mistake is waiting until review week to recall accomplishments -- a year of work is difficult to reconstruct from memory. Keep a running accomplishment document throughout the year (updated at least monthly) so that review preparation involves compiling and organizing evidence rather than trying to remember it. Arriving at a performance review with documented evidence of your contributions is significantly more effective than relying on your manager's memory of your work.
Performance reviews are high-stakes conversations for IT professionals. They influence compensation decisions, promotion eligibility, and management perceptions of your trajectory. Yet most IT professionals spend little time preparing for them, treating review meetings as passive assessments of work that "speaks for itself."
Work does not speak for itself. Managers have dozens of employees and hundreds of projects to track. They make review decisions based on a combination of direct experience, peer feedback, and the impressions that have accumulated over the review period. IT professionals who actively shape those impressions through preparation and documentation systematically perform better in review processes.
The Year-Round Accomplishment Document
The foundation of performance review preparation is a running accomplishment document maintained throughout the year. This is a private document (stored on personal, not company, systems) that captures:
Projects and deliverables:
- Project name and scope
- Your specific role and contribution
- Outcome achieved (with metrics where possible)
- Date completed
Certifications and professional development:
- Certifications earned with dates
- Courses or training completed
- Conferences or technical events attended
Feedback received:
- Direct quotes from positive feedback from managers, peers, or stakeholders
- Email praise, Slack messages, or documented acknowledgments
- Survey results or retrospective feedback
Responsibilities added:
- New responsibilities taken on during the review period
- Projects outside your original job description
- Mentorship or training of junior colleagues
Metrics tracked:
- Uptime percentages or improvements
- Response time reductions
- Cost savings or efficiency improvements
- Ticket resolution volumes and times
- Any quantifiable operational metrics relevant to your role
Update this document monthly, not annually. Accomplishments from 10 months ago are difficult to recall without documentation.
Mapping Accomplishments to Review Criteria
Most IT organizations use one of several performance frameworks for evaluating employees:
Goal-based reviews: Evaluate performance against goals set at the start of the review period. Your preparation: review your documented goals, map your accomplishments to each goal, and assess your performance honestly before your manager does.
Competency-based reviews: Evaluate performance against defined competency frameworks (technical skills, communication, collaboration, leadership). Your preparation: assess yourself against each competency with specific evidence for each rating.
OKR-based reviews: Evaluate Objective and Key Result achievement. Your preparation: calculate your KR achievement percentages and document contributing work.
360 reviews: Include peer feedback alongside manager assessment. Your preparation: consider which peers are submitting feedback, ensure your contributions to their work are visible to them, and consider providing proactive context about projects they observed.
Writing Your Self-Assessment
Most IT performance review processes include a self-assessment that the manager reads before the review meeting. The self-assessment is your most direct opportunity to shape the manager's perception of your performance.
Effective self-assessment structure:
- Summary of your biggest contributions (2-3 achievements with metrics)
- Progress on each formal goal or competency area
- Areas where you developed new skills or expanded scope
- Honest self-assessment of development areas (not a list of failures, but acknowledgment of areas you are working on)
- Goals for the next review period
Tone guidance: Self-assessments should be professional and confident without being arrogant. Quantify contributions where possible. Avoid excessive self-criticism (development areas should be framed as growth areas with action plans, not as performance failures) and avoid excessive self-promotion (claim accomplishments accurately, not exaggeratedly).
"I review self-assessments for 15 engineers before writing each performance review. The quality difference is enormous. Some engineers give me three paragraphs that actively help me write an accurate and favorable review. Others give me one sentence. The correlation between self-assessment quality and review outcome is not perfect, but it is real." -- Engineering Manager, cloud infrastructure team
Performance Review Tables and Frameworks
Self-Rating Calibration:
| Rating Level | What It Means | Evidence Required |
|---|---|---|
| Exceeds Expectations | Performs at next level, strong business impact | Specific projects above scope, quantified impact |
| Meets Expectations | Reliably delivers assigned work | Completed goals, consistent quality output |
| Partially Meets | Areas of concern, inconsistent delivery | Accurate assessment of gaps |
| Does Not Meet | Performance issues requiring a plan | Honest assessment, improvement plan discussion |
Most organizations use a 3-5 point scale with different labels but equivalent meaning. Understanding where you genuinely fall before the review allows you to provide evidence for higher ratings or engage honestly with areas of concern.
The Compensation Conversation in Performance Reviews
Many organizations tie compensation decisions to performance review ratings -- a "Meets Expectations" rating may yield a 3-4% cost-of-living increase, while "Exceeds Expectations" yields 6-10% or qualifies for a promotion.
If you are seeking a meaningful raise (above the standard annual adjustment):
Prepare the business case in advance. Do not wait for the review meeting to raise compensation. Request a separate conversation before the review: "I would like to discuss my compensation before the formal review. I have done some market research and would like to share it. When is a good time?"
Link compensation to documented accomplishments. "Based on my accomplishments this year -- specifically [X, Y, Z] -- and market data showing the range for my role is $A-$B, I would like to discuss moving my compensation to $[specific number]."
Understand the decision timeline. At most organizations, compensation decisions for the annual review cycle are finalized weeks before the review meeting. By the review meeting, the decision is often already made. Effective compensation advocacy happens before the decision cycle closes.
Managing a Difficult Performance Review
If you receive a rating lower than you expected:
Do not argue emotionally in the moment. Request time to review the feedback and schedule a follow-up conversation: "I appreciate the feedback. I want to take time to review this fully before we discuss it further. Can we schedule 30 minutes next week?"
Seek specific evidence. "Can you help me understand specifically which projects or behaviors led to this rating? I want to make sure I understand what to address."
Document your objection if you believe the review is inaccurate. In some organizations, employees can submit a written response to a formal performance review. If you believe your performance has been assessed inaccurately, a factual, professional written response can be appropriate.
Consider the pattern. A single low rating in an otherwise positive review history may reflect a difficult review period. A pattern of low ratings despite your best efforts may indicate a poor fit with the manager's assessment style, the organization's culture, or the role itself.
Goal-Setting for the Next Review Period
End of performance review meetings are when goals for the next period are often set. Approach this part of the conversation strategically:
Set goals that are achievable and visible. Goals should be specific enough to demonstrate clear achievement: "Complete AWS SAP certification by Q2" is demonstrable. "Improve cloud skills" is not.
Include at least one goal that reflects next-level work. If you are seeking a promotion, include at least one goal that would demonstrate performance at the next level. This creates a documented path: "My goal is to lead the infrastructure migration project end-to-end. Completing that successfully would demonstrate senior-level ownership."
Negotiate goals when they are unrealistic. Managers sometimes set aspirational goals without adequate consideration of workload and resource constraints. It is appropriate to note when goals are unrealistic at the time they are set: "I want to make sure these goals are achievable given current team size and the other projects I am running in parallel. Can we discuss priority?"
Frequently Asked Questions
Should I document peer feedback that contradicts my manager's assessment of my performance? Yes, but handle it carefully. If multiple peers have documented positive feedback that contradicts a negative manager assessment, that information is relevant to HR if you are challenging the review. Share it professionally: "I have received feedback from [specific peers] that suggests [specific point]. I wanted to make sure that perspective is part of the complete picture."
How do I handle a manager who is not present throughout the year and does not have context for my contributions? Make your work visible proactively throughout the year -- do not wait for review season. Send brief weekly or biweekly updates summarizing what you are working on and any notable accomplishments. These updates serve as a running record that your manager can reference when writing your review. If your manager has limited context despite your efforts, the self-assessment becomes even more critical as the primary source of information about your contributions.
What if my performance review rating does not match my raise? It is worth clarifying the discrepancy: "I received an Exceeds Expectations rating but my raise was at the standard cost-of-living percentage. Can you help me understand how the rating connects to the compensation outcome?" Sometimes this is a budget constraint (all raises were capped regardless of rating), sometimes it reflects a disconnect in the process. Understanding which it is helps you decide whether to accept it, negotiate further, or evaluate external options.
References
- SHRM. (2024). Performance Review Best Practices. shrm.org
- Gartner. (2024). Performance Management Research for Technology Teams. gartner.com/en/human-resources
- Harvard Business Review. (2024). How to Ace Your Performance Review. hbr.org/topic/performance
- LinkedIn. (2024). Career Advancement and Performance Management Data. linkedin.com/pulse
- Dice. (2024). IT Performance Review and Compensation Trends. dice.com/career-advice
- McKinsey. (2024). Talent Management in Technology Organizations. mckinsey.com
- CompTIA. (2024). IT Professional Development and Career Survey. comptia.org/content/research