Performance Review Meeting · Appraisal Meeting
Performance Review Meeting
What is a performance review meeting?
- Not a rating announcement, but a review of the evidence and agreement on next year
- Hear the self-assessment first; split the time between past and future
- If the meeting holds a surprise, it has failed
If you treat a performance review meeting as a place to announce results, it ends in 10 minutes and the employee remembers only the rating. In practice, a performance review meeting is a conversation to review the year’s evidence together and agree on next year. The rating is only one of its outcomes. The meeting has done its job if the employee leaves the room able to explain, in their own words, 'why I got this rating' and 'what should change next year.' The quality of the meeting is decided not by eloquence on the day but by preparation.
Preparation has three parts. First, consolidate the year’s goals, results, and quarterly observation notes onto one page. Second, collect the employee’s self-assessment 3 to 5 days before the meeting and mark the items where your views differ most. Third, check that you can support the rating with 2 to 3 specific facts. Plan for 40 to 60 minutes, and open by hearing the employee’s self-assessment first. If the manager opens with the rating, the rest of the conversation turns into defending and explaining.
A good rule of thumb for splitting the time is half on the past, half on the future. In the first half, point to what went well and what fell short using specific moments; in the second half, set out the direction of next year’s goals, the capabilities to build, and the support the leader will provide. If the rating and compensation discussion looks likely to run long, it is better to split the development conversation into a separate meeting. At the end of the meeting, write down three lines of what you agreed so both sides can confirm them.
The most common failure in practice is the surprise: 'I never heard this before.' When a leader raises a problem in the review meeting that was never mentioned all year, the employee feels the unfairness of the process before they even take in the content. Another is blaming the rating on someone else. Saying "I wanted to raise it, but upper management cut it" is convenient in the moment, but it erodes both the appraisal system and the leader’s own credibility. Even when the result came out of a calibration meeting, the leader bears accountability for explaining the basis for that rating in their own words.
Seungbin JeonAn instructor who draws on psychology expertise to support communication and leadership growth in organizations
John KimInstructor John Kim, author of B2B Marketing Design and CEO of Nanum ConsultingThe practice of setting goals and having a manager and employee review the results together at the end of the period became a step in the appraisal process as management by objectives (MBO) spread through companies. It has no single founder; it hardened into a standard procedure through appraisal practice. More recently, many companies have split the once-a-year meeting into quarterly and ongoing conversations.
Consider a hypothetical case. Company A, a software developer with 260 employees, received 31 appeals after its year-end appraisals. More than half cited 'I was only told my rating in the meeting,' and the 22 team leaders averaged 12 minutes per meeting.
- The HR head distributes a one-page meeting prep sheet to 22 team leaders. It is a form with blank fields for goals, results, and observation notes, plus a field for 'three facts supporting the rating'.
- Five days before the meetings, the leader of Development Team 2 collects self-assessments from all 8 team members. One member rated themselves an A while the leader’s judgment is a B, so the leader puts a star next to that item.
- On the day, the leader asks, "Start by telling me what you think was your best work this year," and listens for 15 minutes. The rating comes only after the three supporting facts have been explained one by one.
- When a team member asks, "Why wasn't my Q3 incident response reflected?", the manager opens the observation log and answers by separating what was reflected from what was missed, then adds the missing items to the record.
- The remaining 25 minutes go to next year. They agree the employee will take the code review lead role, and the manager writes the three agreed points on the meeting record sheet for both to confirm.
- In the next appraisal cycle, appeals fall from 31 to 9, and the average meeting length rises from 12 to 47 minutes. In the follow-up survey, agreement with 'I understood the reason for my rating' goes from 48% to 81%.