Performance Review Meeting Guide: Preparation and Flow for Managers and Employees

The most critical moment of a performance review is not when the forms are filled in but when manager and employee sit down together. The same scores can become a motivating roadmap in a well-run meeting, or a defensive argument in a poorly run one. The difference comes largely from preparation and the flow of the conversation.

This article is a guide for both managers and employees: how to prepare, what order the meeting should follow, how to handle difficult moments and what to do afterwards.

The purpose of the review meeting

A performance review meeting is not a score announcement. It serves three purposes:

• Looking back: What was achieved during the period, and where were the struggles?
• Agreeing: How do both sides interpret the results?
• Looking ahead: What are the goals and development areas for the next period?

Devoting at least half the meeting to the future stops it from becoming a reckoning. In teams that give regular feedback during the year these meetings are much easier; see our article on a culture of continuous feedback.

Preparation for the manager

A good meeting needs preparation that starts at least a few days earlier. The manager's checklist:

1. Read the results as a whole. In HibritİK Performance Management, the success score is a weighted combination of responsibility, competency and target results. Look at each component, not just the total.
2. Follow target actuals through the period. Because employees enter monthly actuals themselves, targets and actuals appear side by side. Think in advance about which months deviated and why.
3. Watch for gaps in competency results. A clear difference between how managers, direct reports and peers rated the same competency is a valuable topic for the meeting.
4. Read the comments on low scores. In the responsibility evaluation, a comment is mandatory when a score of 1 is given; these comments are a ready source of concrete examples.
5. Prepare concrete examples. For each important point, note at least one event, date or piece of output.
6. Think about development. The areas in the training needs report are a good starting point for the forward-looking part of the meeting.

If rater names are hidden, never attribute a comment to a person in the meeting and do not try to guess who said what. Anonymity produces honest feedback only as long as it is protected.

Preparation for the employee

A review meeting is not only the manager's meeting. An employee who comes prepared helps set the agenda:

• Write your own summary of the period: your three most important achievements and two areas where you struggled.
• Review your targets: look at the actuals you entered each month and be ready to explain deviations.
• Read your responsibilities: do the items in the department responsibilities list still fit your role? Note any work that has changed.
• Identify the support you need: which training, resources or authority would help you do your job better?
• Consider your career expectations: which responsibilities would you like to take on next period?

The flow of the meeting

Every meeting is different, but the following flow gives a good skeleton in most cases:

1. Opening and purpose

State the purpose and length of the meeting briefly. Choose a comfortable, uninterrupted setting. Silencing phones and notifications shows the employee that this time is for them.

2. The employee's own assessment

Letting the employee speak first stops the meeting from being a one-way announcement. "How do you see this period?" also helps the manager understand the employee's perspective. If your organisation wants employees to assess themselves, you can set this up as a job analysis question set and discuss the answers here.

3. Sharing the results

Go through responsibility, competency and target results in turn. Start with strengths, but not merely as a cushion; strengths should be discussed with concrete examples too. Express development areas in terms of behaviour and results rather than personality: instead of "you are careless", say "the last three reports needed corrections after the deadline".

4. Discussing differing views

If the employee disagrees with a result, treat it as information, not a threat. Listen to their reasoning and note any new information. The disagreement need not be fully resolved; what matters is that both sides understand each other's view.

5. Looking ahead and the development plan

This is the most valuable part of the meeting. Agree on next period's targets and no more than two or three development areas. For each area, write a concrete action (training, mentoring, a new responsibility) and a time frame.

6. Closing

Summarise what was discussed, repeat the agreed actions and ask whether the employee has anything to add.

Practical tip: aim to leave most of the talking to the employee. The less the manager talks and the more questions they ask, the more the employee owns the results.

Handling difficult moments

• If the employee becomes defensive: do not try to win the argument. Return to the concrete example and ask how they see that event.
• If results are well below expectations: allow room for an emotional reaction; if needed, take a short break and continue with the forward-looking part.
• If the employee compares themselves with someone else: bring the conversation back to their own results and development; do not discuss other employees' reviews.
• If pay or promotion comes up: explain honestly how your organisation makes these decisions, and make no promises you cannot keep. Our article on linking performance results to promotion, pay and training can help.

After the meeting

A meeting's value is measured by what happens next:

1. Define the agreed targets in the system as next period's targets, with clear scale, direction and frequency.
2. Put development actions on the calendar and assign an owner.
3. Share organisation-wide development areas with HR, together with the training needs report.
4. Follow progress with short check-ins during the period, so the next review holds no surprises.

In HibritİK you can copy the previous period's responsibility and competency definitions when opening a new period, and track targets monthly or yearly. What was agreed in the meeting becomes the measurable starting point of the next period.

Common mistakes

• Going into the meeting unprepared and reading out only the total score.
• Judging the whole period by the last few weeks.
• Trying to guess who wrote anonymous comments.
• Ending the meeting without a development plan.
• Treating the meeting as the only point of contact in the year.

Preparing for review meetings with HibritİK

In HibritİK, the components of the success score, targets and actuals, multi-rater competency results and the training needs report sit in one place while you prepare; you can export reports to Excel and use them alongside your meeting notes. To set up your own process, start a 14-day free trial or see the pricing page.