How to give your first performance review as a manager

Performance reviews terrify most first-time managers more than they terrify the people receiving them.

The anxiety usually comes from the same place: you've received feedback before, but you've never been trained to give it formally. You're aware that you're saying things that go on a record. You're worried about damaging a relationship. You don't know how direct to be.

Here's the structure that makes performance reviews useful — for you and for the person sitting across from you.

The goal of a performance review

Let's start here because it changes everything else.

A performance review is not a judgment. It's not a grading ceremony. It's a calibration conversation — an opportunity to give someone a clear, honest picture of where they stand, what they've done well, what they need to develop, and what you expect going forward.

The goal is not to make people feel good or bad. The goal is to give them information they can act on.

When you hold this frame, the tone of the review changes. You're not delivering a verdict. You're providing a signal.

Before the review: do your homework

The most common failure in performance reviews is not doing the preparation.

Spend real time before the conversation:

Review the full period, not just recent memory. What happened in January? March? Q3? Memory is recency-biased. Pull notes, emails, Slack messages, or whatever else gives you data from the whole review period.

Collect feedback from others. Your perspective is partial. Talk to the people your direct report works with most — colleagues, cross-functional partners, anyone who has real exposure to their work. This doesn't have to be formal; even two or three informal conversations give you a more complete picture.

Know the rating before the meeting. Managers who arrive at a review without having made a decision create bad reviews. You should have a clear assessment going in — the conversation can inform the next review, but it shouldn't change the current one in real time based on how the person reacts.

Prepare specific examples. "You've been really collaborative" is useless. "In the Q2 product launch, you pulled in three other teams and kept everyone aligned through three pivots" is useful. Specificity is what separates good feedback from flattering noise.

The structure of the conversation

A 60-minute performance review can follow this structure:

First 5 minutes: set the context. Explain what you're doing and how you're thinking about the conversation. Something like: "I want this to be a two-way conversation. I've prepared some specific feedback, and I want to leave time for your perspective. Nothing here should be a complete surprise — if it is, that's on me for not being clearer during the year."

Next 10 minutes: ask them to go first. Start with: "How would you assess your own performance over the last year?" This does several things. It gives you their self-perception, which often reveals how aligned or misaligned you are before you say anything. It also makes the conversation collaborative rather than evaluative.

Next 30 minutes: your assessment. Cover strengths first, then development areas, then the rating and what it means. Be specific in all three sections. For development areas, be direct: "The area where I think you have the most opportunity to grow is X, specifically in situations like Y" is more useful than "There are some areas where you could develop."

Last 15 minutes: forward-looking. What do they want to develop? What support do they need? What should they focus on in the next review period? This is where the review becomes a plan, not just a verdict.

How to give critical feedback without softening it into uselessness

Most first-time managers over-soften critical feedback to the point where the person doesn't actually understand it's critical.

This happens because of the "feedback sandwich" — leading with something positive, burying the hard feedback, ending on a positive. By the time you're done, the person has heard "good, okay, good" and didn't register the "okay" as a real problem.

Instead:

Say what you mean first, then explain it. "I want to talk about how you handle ambiguity. In several situations this year — I'll give you specific examples — you escalated to me before exhausting your own options. That's a pattern I need you to shift."

Be clear about the consequence. Not punitive, but real: "This matters because at the senior level I need you to move toward, you'll be operating with less direction, not more. If this doesn't shift, it limits what I can put you on."

Then invite the other side. "Tell me how you see it. Am I reading this situation correctly?"

Handling difficult reactions

People sometimes cry. People sometimes get defensive. People sometimes go quiet. Here's how to handle each:

If they cry: Don't panic. Give them a moment. "Take your time." Don't immediately walk back what you said. The feedback can still be right even if the delivery is painful. Once they're settled: "I want to make sure you hear this as coming from wanting to support your development, not as a judgment."

If they get defensive: Listen first. "Tell me more about how you see it." Sometimes they have information you don't — and you should update your view. Sometimes they're just reacting — and after they've said what they need to say, you can acknowledge it and come back to the feedback.

If they go quiet: Check in. "I'm not sure if that's landing well or if I'm missing something. What are you thinking?" Silence can mean many things — don't interpret it as acceptance.

The most important thing to get right

The most common failure in first performance reviews isn't the delivery. It's the avoidance of the hard things entirely.

Managers who want to be liked often give glowing reviews to people who have real development needs. This is a betrayal of the relationship, even though it doesn't feel like one. The person gets a good review, continues the same behaviors, gets passed over for promotion, and then feels blindsided — not by the outcome, but by the years of feedback that didn't prepare them for it.

If someone on your team has a real problem, the review is the moment to name it clearly. Not cruelly. Clearly. That's what they hired you to do.

Practice giving performance review feedback so you know how it sounds before the real thing.