Performance review conversations bring a defined period of work into one discussion: what was expected, what the evidence shows, what the employee sees differently and what happens next. They are not simply a longer version of feedback about one recent incident. This guide helps managers prepare for the conversation within their employer’s existing process; it does not supply a rating system or replace HR requirements.
MIT Human Resources’ performance-review guidance treats the review as a summary of ongoing conversations and recommends preparation by both manager and employee. That is one institution’s published practice, not a universal employment rule, an MIT endorsement of this guide or evidence that a particular conversation produces a business result.
Confirm the purpose and the decisions you may make
Before scheduling the discussion, check the review period, current role expectations, required forms and who may approve any rating, compensation or role change. Tell the employee what the meeting will cover and what they should prepare under your process. Do not turn a development discussion into an unannounced assessment, or promise a pay or promotion decision outside your authority.
A useful preparation question is: Which matters can we settle in this meeting, which are recommendations and which require another authorized decision-maker? Keep those categories visible in your notes. Where the organization requires a separate process for a concern, use it rather than improvising consequences in the review.
Build an evidence map across the review period
Start with the agreed expectations and any approved changes, then connect each important observation to a suitable work record. Include contributions and difficulties across the period, not only the most recent memorable event. Separate a delivered draft from an accepted output, a missed target from an explanation for it, and a repeated pattern from one observation.
Original preparation prompt: Expectation and applicable period: [ ]. Changes agreed during the period: [ ]. Work evidence and its limits: [ ]. Your interpretation: [ ]. Employee’s account or questions to invite: [ ]. Information still to verify and its owner: [ ]. Keep the actual record in approved systems. This prompt is not a personnel scoring tool and should not collect unnecessary private details.
Fictional example: the goal changed but the date did not
A project lead’s original objective was to prepare an internal onboarding guide by June. In May, the sponsor added three roles to its scope, but the recorded completion date stayed the same. At review, a draft exists but final acceptance is still pending. The manager’s first impression is that the employee missed the objective.
Before settling that interpretation, reconstruct the original scope, the approved change, what was submitted and when the necessary reviewers were available. Invite the employee’s account and check the relevant records. Added scope does not automatically explain every delay; an unfinished draft is not a completed guide either. The useful question is what the evidence supports under the organization’s actual expectations, not which person gives the more convincing account.
Record the disputed or missing facts and who will check them through the proper process. Do not invent a rating to make the example feel complete. This fictional case illustrates preparation for a review, not a client result, a recommended employment decision or a rule for resolving real personnel matters.
Make room for the employee’s account
Explain the observation, its connection to an agreed expectation and what remains uncertain. Ask what context is missing and which interpretation the employee questions. Use the manager feedback examples for wording grounded in work rather than personality labels; the review still needs the wider period and approved process.
Listening does not require treating every explanation as established fact. Equally, a manager’s first interpretation is not a substitute for evidence. Where accounts differ, distinguish a factual check from a disagreement about the standard or judgment. Follow the employer’s process for recording the employee’s comments, reviewing a disputed conclusion and communicating the authorized outcome.
Keep work expectations and development actions distinct
Close by identifying the expectations for the next period, matters still awaiting a decision and the support each owner will provide. A learning action is a separate agreement: what capability will be practised, in which suitable work and with what feedback? The individual development-plan example shows how to connect a learning goal with supported practice rather than a course-attendance target.
Name the follow-up owner and checkpoint for unresolved items. Do not assume an acknowledgment means agreement with every conclusion; use the meaning and procedures specified by the organization. Keep formal records in the appropriate system, rather than carrying personnel details into a shared leadership dashboard.
If you are buying review-conversation training
Ask the provider to work with an authorized, appropriately anonymized version of your review process. Useful practice should include incomplete evidence, a changed expectation and an employee who reasonably challenges the manager’s interpretation, not only a compliant scripted response. Ask how the facilitator will help managers distinguish a communication skill from an unresolved policy or authority question. Training can support preparation and practice; it does not authorize the provider to decide employees’ ratings or pay.
About this resource: Prepared with AI-assisted drafting and editorial review. The preparation prompt and case are original illustrative aids, not a validated assessment, reported client results, employment or legal advice, or a replacement for organizational policy and qualified HR support. Cover illustration: AI-generated.