Performance Review Guide for Tech Leads: Write Better Reviews and Develop Your Team

Performance reviews are one of the most dreaded activities in management. Engineers hate receiving vague, unhelpful reviews. Managers hate writing them. HR hates chasing overdue submissions. And yet, when done well, performance reviews are one of the most powerful tools a tech lead has for developing talent, building trust, and driving team performance.

The problem is not the concept of performance evaluation — it is the execution. Most organizations have built systems that optimize for administrative compliance rather than genuine development. This guide shows you how to do performance reviews that actually help your people grow, based on approaches I have refined over 22 years of engineering leadership.

Why Performance Reviews Still Matter

There is a trendy argument that formal performance reviews are outdated and should be replaced entirely by continuous feedback. I disagree. While continuous feedback is essential (and I will discuss it next), formal reviews serve purposes that informal feedback cannot:

• They create a forcing function for reflection. Without the structure of a review cycle, many conversations about growth and performance simply do not happen. The deadline creates accountability.
• They provide documentation. For promotions, compensation adjustments, and (if necessary) performance improvement plans, you need written records of performance assessments.
• They enable calibration. When managers across the organization write reviews using similar frameworks, you can calibrate ratings to ensure fairness across teams.
• They give the big picture. Daily feedback is tactical. A quarterly or semi-annual review zooms out to assess trends, trajectory, and overall impact in a way that individual conversations cannot.

The key is to make reviews a natural summary of ongoing conversations, not a surprise. If your team member learns something significant in their review that they did not already know from your 1-on-1 conversations, you have failed as a manager.

Continuous Feedback: The Foundation

Formal reviews work best when they are built on a foundation of continuous feedback. This means providing specific, timely feedback throughout the review period, not saving it all for review time.

The 3-Day Rule

When you observe something that warrants feedback — positive or negative — deliver it within three days. Feedback loses impact exponentially with time. "Great job on the API redesign you finished this morning" is powerful. "Remember that API redesign you did two months ago? Good job." is meaningless.

The Feedback Journal

Keep a running document for each team member where you record specific observations throughout the review period. When review time comes, you will have a rich set of examples to draw from instead of relying on recency bias (overweighting the most recent events). Include:

• Specific accomplishments with dates and impact
• Examples of behaviors you want to reinforce
• Areas where you observed struggles or growth opportunities
• Feedback from peers and stakeholders
• Key projects and the person's contribution

Peer Feedback Collection

Your perspective as a manager is limited. You do not see how your team members interact with peers, how they collaborate in code reviews, or how they handle technical disagreements. Collect structured feedback from 3-5 peers for each review. Ask specific questions:

• "What is this person's most significant contribution to the team?"
• "What is one thing this person could improve?"
• "How effectively does this person collaborate with you?"
• "Would you want to work with this person again on a future project?"

Writing Effective Performance Reviews

A good performance review is specific, balanced, and forward-looking. Here is the anatomy of an effective review:

Start with Impact

Lead with the person's most significant accomplishments during the review period. Be specific about the outcome and the person's contribution:

Weak: "Carlos did a good job this quarter."

Strong: "Carlos led the migration from PostgreSQL 12 to 16 with zero downtime, affecting 2M daily active users. He proactively identified a connection pooling issue during testing that would have caused a 30-minute outage, and his runbook enabled the on-call team to handle the cutover without his direct involvement."

Be Specific About Strengths

Generic praise is useless. "Great team player" tells the person nothing about what to continue doing. Instead: "Your habit of documenting design decisions in ADRs has significantly improved the team's ability to onboard new members. The three ADRs you wrote for the payment system saved approximately 20 hours of explanation time during Maria's onboarding."

Be Equally Specific About Growth Areas

This is where most managers struggle. The temptation is to soften growth areas into compliments: "You are so thorough that sometimes it takes longer than necessary." This is not helpful. Be direct: "Your code reviews are thorough, but they often take 48+ hours, which blocks other engineers. I need you to reduce your average review time to under 24 hours, even if that means fewer comments per review."

Include Forward-Looking Goals

Every review should end with 2-3 specific development goals for the next period. Make them SMART: Specific, Measurable, Achievable, Relevant, and Time-bound.

The 5 Evaluation Dimensions for Engineers

When evaluating engineering performance, I use five dimensions that cover the full scope of an engineer's contribution:

Not every dimension carries equal weight at every level. Junior engineers are evaluated primarily on technical execution and growth. Senior engineers are evaluated more heavily on collaboration, communication, and the quality of their architectural decisions. Staff and principal engineers are evaluated primarily on their influence, strategic contributions, and ability to multiply the team's output.

Calibration: Ensuring Fairness

Calibration is the process of comparing evaluations across managers to ensure consistency. Without calibration, one manager's "exceeds expectations" might be another's "meets expectations."

How to Run a Calibration Session

1. Managers submit initial ratings independently. This prevents anchoring bias.
2. Group by level. Compare all senior engineers across teams, all juniors across teams, etc.
3. Each manager presents their rationale. For each person, explain why they received their rating with specific evidence.
4. Challenge and adjust. Other managers ask questions and push back where ratings seem inconsistent. "You rated Alex as exceeding expectations, but the accomplishments you described sound similar to what Sara did, and you rated her as meeting expectations. What differentiates them?"
5. Document final ratings and rationale. This creates accountability and a reference for future calibrations.

Common Calibration Pitfalls

• Grade inflation: Everyone gets "exceeds expectations" to avoid difficult conversations. This devalues the rating system and hides real performance issues.
• Stack ranking pressure: Forced distribution curves can lead to unfair ratings in high-performing teams. Push back on rigid distribution requirements.
• Loudest voice wins: Managers who are better at advocacy get better ratings for their people. Structure the discussion to ensure all voices are heard.

Recognizing and Avoiding Bias

Cognitive biases affect every performance review. Awareness is the first step to mitigation. Here are the biases most relevant to engineering performance reviews:

• Recency bias: Overweighting events from the past few weeks. Mitigate by keeping the feedback journal throughout the review period.
• Halo/horn effect: Letting one strongly positive or negative trait influence the entire review. A brilliant architect who cannot communicate is not "exceeds expectations" overall — they excel in one dimension and need improvement in another.
• Similarity bias: Rating people who think and work like you more favorably. Be especially vigilant about this if your team is diverse in backgrounds and working styles.
• Attribution bias: Attributing success to circumstances for some people ("the project was easy") and to talent for others ("she is brilliant"). Look for consistent evidence across situations.
• Anchoring to previous reviews: Assuming someone's performance is similar to last review without fresh evidence. Evaluate each period independently.
• Visibility bias: Overweighting contributions that are visible (presentations, high-profile projects) and underweighting invisible work (mentoring, documentation, technical debt reduction). Actively seek out invisible contributions.

Delivering the Review Conversation

Writing the review is half the job. Delivering it effectively is the other half.

Before the Meeting

• Share the written review at least 24 hours before the conversation. Give people time to process and prepare questions.
• Book 60 minutes. Rush reviews feel dismissive.
• Prepare for questions and emotional reactions. Plan how you will respond if the person disagrees or becomes upset.

During the Meeting

1. Start with their self-assessment. "How do you feel about your performance this period?" This reveals gaps between your perception and theirs, which you can address directly.
2. Walk through the review together. Do not just read it aloud. Discuss each section. Ask for reactions. Provide additional context and examples.
3. Spend equal time on strengths and growth areas. Many managers rush through strengths to "get to the important part." Recognizing what people do well is just as important as identifying what they need to improve.
4. Discuss growth goals collaboratively. Goals imposed without input are less motivating than goals co-created. Ask what they want to work on, then align with what you observe.
5. End with a clear summary. "My overall assessment is that you are performing at a strong meeting-expectations level with clear trajectory toward exceeding in the areas we discussed. Your focus areas for next quarter are X and Y."

After the Meeting

• Follow up within a week on any action items or questions that came up.
• Integrate development goals into your regular 1-on-1 conversations.
• Start your feedback journal for the next review period immediately.

Addressing Underperformance

Addressing underperformance is the most challenging part of performance management. Here is a structured approach:

Step 1: Verify the Problem

Before concluding someone is underperforming, ask yourself: Are the expectations clear? Does the person have the resources and support they need? Is there an external factor (personal issues, team dysfunction, organizational change) affecting their performance?

Step 2: The Direct Conversation

Be clear, specific, and compassionate. "I have observed that your delivery has dropped significantly over the past two months. You have missed three sprint commitments, and two of your recent features required major rework after code review. This is below the expectations for your role, and we need to discuss what is happening and how to improve."

Step 3: The Performance Improvement Plan (PIP)

If informal feedback has not led to improvement, a formal PIP may be necessary. A good PIP includes:

• Specific, measurable performance expectations
• A defined timeline (typically 30-60 days)
• Concrete support you will provide (more frequent 1-on-1s, mentoring, training)
• Clear consequences if improvement does not occur
• Regular check-in milestones

Important: A PIP should be a genuine opportunity for improvement, not a paper trail for termination. If you have already decided to let someone go, a sham PIP is dishonest and unfair.

Step 4: Follow Through

Meet weekly during the PIP period. Acknowledge improvements. Be direct about continued shortfalls. At the end of the PIP period, make a clear decision: the person has improved sufficiently and exits the PIP, or they have not and you proceed with the consequences outlined.

Developing High Performers

High performers present their own challenges. They are often underserved by performance management systems that focus on identifying and addressing problems.

• Challenge them appropriately. High performers who are not challenged become bored and leave. Provide stretch assignments that push them into new areas.
• Give them visibility. Create opportunities for them to present to leadership, represent the team in cross-functional initiatives, and build their professional reputation.
• Be honest about growth areas. High performers often receive universally positive feedback, which deprives them of the specific input they need to reach the next level. Tell them what stands between them and promotion.
• Discuss their future explicitly. What are their career aspirations? Are those achievable within your team and organization? If not, help them find the right path — even if it means losing them. The worst outcome is a high performer who leaves because they felt stuck.
• Compensate fairly. High performers who feel under-compensated will leave for organizations that value them appropriately. Advocate fiercely for fair compensation.

Performance Review Templates

Quarterly Performance Summary Template

## Performance Review: [Name]
## Period: Q[X] [Year]
## Reviewer: [Your Name]

### Summary
[2-3 sentence overall assessment]

### Key Accomplishments
1. [Specific accomplishment with measurable impact]
2. [Specific accomplishment with measurable impact]
3. [Specific accomplishment with measurable impact]

### Strengths
- [Specific strength with example]
- [Specific strength with example]

### Growth Areas
- [Specific area with concrete improvement suggestion]
- [Specific area with concrete improvement suggestion]

### Goals for Next Quarter
1. [SMART goal]
2. [SMART goal]

### Overall Rating
[Rating with justification]

"A performance review should never contain a surprise. If you have been doing your job as a manager — giving timely feedback, having honest 1-on-1s, and addressing issues as they arise — the review is simply a formalization of conversations you have already had."