Somewhere in your org right now, there's someone excellent who's about to get "meets expectations" while a louder colleague gets the promotion.
The manager isn't corrupt. They're not playing favourites. They just can't describe, in specific terms, what the quiet one actually did this year. And you can't reward what you can't describe.
Most people experience performance reviews as something done to them. A form shows up, you fill it in the night before it's due, you wait, and then you find out what someone else decided about your year.
That's backwards. A review should never contain a surprise, for you or your manager. If it does, something broke months earlier.
This module covers both sides of feedback: how to understand and influence the review process, how to take feedback well, and how to give it, including to your peers and your own manager.
The short version
- Ratings are usually decided before the conversation, often in a meeting where managers compare notes. Your manager needs evidence to argue for you.
- Know what "good" looks like for your role in writing, early in the year, not at the end.
- Keep an impact log. Your self-review is only as good as what you tracked.
- Receive feedback with Listen, Reflect, Act, Iterate. Defending kills the flow of feedback.
- Give feedback with SBI: Situation, Behaviour, Impact. Specific, not personal.
How ratings actually get decided
Every company does this differently, so ask how yours works. But at many companies the process looks something like this:
Calibration is the step most early-career people have never heard of. It means a group of managers sit together, often with their own boss, and compare ratings across teams so they're consistent. Your manager walks in with a draft rating for you and has to defend it against everyone else's.
Think about what that means. In that room, your manager is your lawyer. They have a few minutes to make your case. If all they can say is "they're a hard worker, really solid," and the next manager says "she cut returns by 30% and trained two new hires," you know how that goes.
Your job all year is to make your manager's argument easy. Three ways to do that:
- Get expectations in writing early. Ask: "What would a great year look like in this role? What would make it 'exceeds' versus 'meets'?" Write down the answer and confirm it.
- Make your outcomes visible as you go. Short written updates, wins in your 1:1 doc, numbers attached. Not bragging. Information transfer.
- Ask where you stand mid-year. "If reviews were today, where would I land, and what would move me up?" This is the single best question for avoiding surprises.
Key idea: You can't backfill a reputation in Q4 for a year you spent silent.
Writing a self-review that works
Your self-review is often the raw material your manager uses in calibration. Sometimes they paste from it directly. Write it for that purpose.
Start from your impact log. If you haven't kept one, spend 30 minutes reconstructing the year from your sent emails, calendar and project files. You'll be surprised how much you've forgotten.
Map your work to the expectations. For each goal or expectation, write what you did and the result. Use the format: I did X, which resulted in Y, measured by Z.
- Weak: "Worked on improving the scheduling process."
- Strong: "Rebuilt the weekly staff schedule template, cutting the time to build it from 4 hours to 1 and reducing last-minute shift gaps from about six a month to two."
Tie results to what leadership counts. Revenue, cost, time saved, risk reduced, customer experience. If you can connect your work to one of those, it reads as more important, because it is.
Be honest about a miss. One clear sentence on what didn't go well and what you learned shows judgement. Your manager already knows about it. Owning it first builds credibility.
Keep it tight. Bullets, numbers, plain language. Your manager may be writing reviews for eight people this week.
Receiving feedback without flinching
Hard feedback stings. That's normal. What happens next is what separates people who grow from people who stall.
When you defend, explain or argue, the person giving feedback learns that it's expensive to be honest with you. They stop. And once your leader stops giving you feedback, your development slows or stalls.
Use Listen, Reflect, Act, Iterate:
- Listen without defending. Your only job in the moment is to understand. Ask: "Can you give me an example?" and "What would good have looked like?"
- Reflect on what's true. You don't have to agree with all of it. Find the part that's useful. Say thank you, and mean it: they took a risk.
- Act quickly. Pick one change and make it visible within days.
- Iterate. Go back and ask: "I've been working on what you mentioned. Is it landing? What's the next refinement?"
If you get a surprise in your review, stay calm in the room. Say: "This is new to me. I want to understand it. Can we set up time next week to go through specific examples and agree what I need to do?" Then take the specifics and build a plan. A rating is a snapshot. Your response to it is what people remember.
A note on performance improvement plans (PIPs, a formal plan with goals and a deadline for improving): if you're put on one, take it seriously, get every expectation in writing, and check progress weekly. Some people turn them around. Either way, you'll want a clear record.
Giving feedback: peers and upward
Feedback isn't only something managers give. You'll be asked for peer feedback in reviews, and you'll often need to tell a teammate, or your own manager, that something isn't working.
The simplest reliable structure is SBI: Situation, Behaviour, Impact, a model developed by the Center for Creative Leadership.
Situation: when and where, specifically. Behaviour: what the person actually did, something a camera could record, not a judgement about their character. Impact: what happened as a result, for you, the team or the customer.
Then, usually, a question: "What was going on from your side?" You may be missing context.
SBI works for praise too, and specific praise is far more useful than "great job." It tells people exactly what to keep doing.
Upward feedback (to your manager) needs a bit more care, but the same rules apply. Ask permission, keep it specific, and connect it to the work: "Can I share something that would help me do better work? In the last two project kickoffs, I got the brief the day before. It meant I couldn't flag the data gaps until we were already behind. Could I get briefs a few days earlier?"
That's not complaining. That's helping your manager help you.
What it looks like in practice
A hypothetical example.
Amira is a customer success associate, a year and a half into her role. Last year her review said "meets expectations" and she didn't understand why. She thought she'd had a strong year.
This year she does three things differently. In January she asks her manager what "exceeds" would look like and writes it down: renewal rate above target, plus taking on one improvement project. She keeps a running list of wins in her 1:1 doc. In June she asks, "If reviews were today, where would I land?" Her manager says the renewal numbers are great but nobody outside the team knows about the onboarding guide she built.
So Amira presents the guide at a team meeting and shares the before-and-after numbers. In her self-review, every point maps to the expectations they agreed in January.
When calibration comes, her manager has a page of specific evidence. The review conversation has no surprises. That's the whole point.
Common traps
- Writing the self-review the night before. You'll forget most of your year. Fix: keep an impact log all year, five minutes a week.
- Assuming your manager knows what you did. They see a fraction. Fix: make outcomes visible in writing as they happen.
- Arguing the rating in the room. It rarely changes the result and costs trust. Fix: ask for examples and a follow-up conversation.
- Feedback about personality. "You're negative" can't be acted on. Fix: use SBI and describe the behaviour.
- Only giving critical feedback. People stop listening. Fix: give specific praise at least as often.
Do this this week
Close the surprise gap.
- Write down what you believe "great" looks like in your role this year. If you're not sure, that's your answer.
- In your next 1:1, ask: "If reviews were today, where would I land, and what would move me up?"
- Start an impact log with five wins from the last three months, each in the X, Y, Z format.
- Give one teammate specific SBI praise for something they did this week.
Your tool
SELF-REVIEW WORKSHEET
ROLE EXPECTATIONS (confirmed with manager on ________)
"Meets" looks like: _________________________________________
"Exceeds" looks like: _________________________________________
IMPACT LOG (add one line a week)
| Date | What I did (X) | Result (Y) | Measured by (Z) | Links to goal |
|------|----------------|------------|-----------------|---------------|
| | | | | |
SELF-REVIEW DRAFT
For each goal/expectation:
Goal: ______________________________________________________
I did ______________, which resulted in ______________,
measured by ______________.
One miss and what I learned: _________________________________
What I want to grow into next: _______________________________
MID-YEAR CHECK QUESTION
"If reviews were today, where would I land,
and what would move me up?"
-----------------------------------------------------------------
RECEIVING FEEDBACK SCRIPT
In the moment: "Thanks. Can you give me an example?"
"What would good have looked like?"
If it's a surprise: "This is new to me. Can we find time to go
through examples and agree what I need to do?"
Follow-up (within 2 weeks): "I've been working on ____.
Is it landing? What's the next refinement?"
-----------------------------------------------------------------
GIVING FEEDBACK (SBI)
Situation: "In / On / During ____________________________,"
Behaviour: "you ________________________________________."
(what a camera would see, not a judgement)
Impact: "The result was ______________________________."
Question: "What was going on from your side?"
UPWARD VERSION
"Can I share something that would help me do better work?"
+ SBI + "Could we try ____________________?"
Talk about it
- Have you ever been surprised by a review or a piece of feedback? Looking back, what signals were there earlier?
- What does your manager actually need from you to argue your case in calibration, and are you giving it to them?
- Who's one person you owe specific feedback, positive or critical, and what's stopping you from giving it?
— Evan