The appraisal meeting
Present your year with evidence, and deliver a rating, even a tough one, with honesty.
Case study: Meera's thirty minute monologue
Meera, a QA engineer in Chennai, prepared for her appraisal by listing every task from January to December. In the meeting with her London manager, she read all forty items aloud. By item twelve, Oliver had stopped taking notes. The one thing that mattered, her automation suite that cut regression testing from three days to six hours, came at item thirty one. The next year she opened with three outcomes, each with a number, then asked, "Do you see it the same way?" Oliver used her exact words in the calibration meeting, and her rating went up a level.
Takeaway: An appraisal is not a list of tasks. Lead with your three biggest outcomes, then ask how your manager sees them.
Many of us treat the appraisal as a formality where the manager decides and we accept. In global companies, your self-review is evidence your manager carries into calibration, and a rating is a conversation you can question respectfully.
Presenting your review
Goal: Make your top outcomes memorable, align on the rating, and agree goals for next year.
Step by step
- Lead with three wins. Your three biggest outcomes, each with a number.
- Own a gap. Name one thing you'd do better. It builds credibility.
- Check alignment. Ask how your manager sees it before the rating is final.
- Look forward. Agree on next year's goals and what the next level needs.
Say this, not that
| Let me start with my three biggest outcomes this year. | In January I did this, then in February I did this. | A timeline buries your best work. |
| My automation suite cut regression testing from three days to six hours. | I did a lot of automation work. | Numbers are what your manager can repeat in calibration. |
| One area I want to improve is speaking up earlier when I see a risk. | Naming a gap yourself makes your wins more believable. | |
| Do you see the year the same way, or is there something I'm missing? | So, what rating am I getting? | |
| What would I need to show next year to reach the next level? |
Model conversation
- Oliver
- Thanks for sending your self-review, Meera. Want to walk me through it?
- You
- Sure. I'll keep it to my three biggest outcomes. First, the automation suite cut regression testing from three days to six hours.
- Oliver
- That one really helped the release team.
- You
- Second, I trained four testers in Kochi on the framework. Third, client-reported bugs dropped by thirty percent.
- Oliver
- Those are strong. Anything you'd do differently?
- You
- I'd flag risks earlier. On the billing release, I raised a concern too late in the sprint.
- Oliver
- I appreciate you saying that. I'll be putting you forward for an exceeds rating.
- You
- Thank you. Could we also agree on what the senior level would need from me next year?
Delivering the rating
Goal: Share the rating clearly and honestly, explain the reasons, and leave a concrete path forward.
Step by step
- Say the rating early. Don't make them wait twenty minutes for it.
- Explain why. Specific strengths and specific gaps, with examples.
- Let them react. Disappointment is normal. Listen without rushing to defend.
- Give the path. What would move the rating next year, and how you'll help.
Say this, not that
| I want to share your rating first, then talk through the reasons. | Let's see, overall it was a mixed kind of year. | People can't listen while they're waiting for the number. |
| Your rating this year is meets expectations. | Say it plainly. Hedging makes it feel worse. | |
| Your automation work was excellent. The gap was visibility: the release team didn't know about risks until late. | ||
| I can see you're disappointed. Tell me what's on your mind. | Everyone gets the same, don't take it personally. | Dismissing feelings makes people stop trusting the process. |
| Here's what would put you at exceeds next year, and I'll check in on it every quarter. | Better luck next year. | A path turns a disappointment into a plan. |
Model conversation
- You
- Thanks for coming, Meera. I'll share your rating first, then the reasons. This year it's meets expectations.
- Meera
- Oh. I was honestly expecting exceeds.
- You
- I understand, and I can see you're disappointed. Your automation suite was excellent work.
- Meera
- Then what was missing?
- You
- Mostly visibility. On two releases, risks you'd spotted reached the team very late. In calibration, that weighed against you.
- Meera
- I didn't know that was being judged so strongly.
- You
- That's fair, and I should have told you mid-year. Next year, if you lead the weekly risk review, I believe exceeds is very realistic.
- Meera
- Okay. Can we check on that every quarter?
Practice it out loud
Reading is half of it. Fluent listens to you say it and scores your clarity, free, in your browser.