Understanding the Importance of Conducting Appraisals Well
A performance appraisal is only as effective as the thought and preparation that goes into it. The process of formally reviewing an employee’s performance has clear purposes: to communicate expectations and how well they have been met, to recognise contributions, to surface development needs, and to set a clear direction for the period ahead. When those purposes are achieved, the appraisal becomes a useful tool for both the employee and the organisation. When they are not, typically because the meeting is poorly prepared, the feedback is vague, or the conversation is one-sided, the process creates anxiety without producing value. Understanding how to run an appraisal effectively, from the preparation phase through to the follow-up, makes the difference between a meeting that changes nothing and one that genuinely supports performance improvement and employee development.
A Practical Guide to Conducting Performance Appraisals
The most common failure in performance appraisals is not an inadequate process; it is inadequate preparation. A manager who walks into an appraisal without specific examples, clear data, or a considered view of the employee’s development needs will find themselves either defaulting to vague generalities or focusing disproportionately on recent events. Both outcomes undermine the credibility and usefulness of the conversation.
Preparing well, structuring the meeting thoughtfully, and following through on what was agreed are the three factors that most consistently determine whether an appraisal produces a good outcome.
Preparation: The Week Before the Meeting
The groundwork for an effective appraisal should be laid over several days rather than the night before. The key inputs are objective performance data, behavioural observations from across the full review period, and the employee’s own self-assessment.
Objective data includes measurable outputs relevant to the role: targets met or missed, quality metrics, project completion rates, response times, and any KPIs specific to the position. These provide the factual foundation for the conversation and prevent assessments from being driven entirely by impression and memory.
Behavioural observations cover how the employee has approached their work: how they have managed relationships, handled pressure, and contributed to the team beyond their immediate responsibilities. These are harder to quantify but equally important, and they require specific examples rather than general impressions. Reviewing notes from one-to-one meetings, project feedback, and any other documented interactions across the full review period is the most reliable way to build a complete picture rather than one weighted toward recent events.
The employee’s self-assessment, requested in advance of the meeting, serves two purposes. It gives the employee a sense of ownership over the process and reveals the manager’s blind spots by highlighting how the employee views their performance relative to the manager’s assessment. A significant gap between the two views is itself important information and shapes how the conversation needs to be approached.
Requesting the self-assessment several days before the meeting gives time to review it and identify the specific areas where alignment and disagreement are most significant.
Avoiding Bias in the Assessment
Every performance assessment is subject to cognitive biases that distort the picture of how an employee has actually performed. Recognising and actively managing these biases is a prerequisite for a fair and credible appraisal.
Recency bias is the tendency to weight the most recent period disproportionately. An employee who had an excellent first three quarters of the year but made a visible error in the final month should not receive an assessment that reflects primarily that error. Using notes and data from across the full review period, rather than relying on memory, is the most effective counter to recency bias.
The halo and horns effect occurs when a single strong or weak quality shapes the overall assessment. An employee who excels at client relationships should not receive a uniformly positive assessment if their project management or attention to detail is genuinely lacking. Assessing each performance dimension separately, with specific examples, reduces the risk of a single attribute distorting the overall picture.
Affinity bias produces more favourable assessments of people whose working style or communication approach resembles the manager’s own. This is one of the reasons calibration sessions, in which managers review their ratings collectively, are valuable: they surface inconsistencies that individual managers cannot easily see in their own assessments.
The practical test before finalising any assessment is to ask whether the rating reflects actual, evidenced performance, whether the same standard would apply to another employee in an equivalent role, and whether the assessment covers the full review period.
Choosing the Right Appraisal Method
The choice of appraisal method should reflect the nature of the role and the employee’s working environment.
For roles where the manager has direct and continuous visibility into the employee’s work, a traditional top-down review drawing on the manager’s observations and available objective data is typically sufficient. The manager has the primary information needed to make a well-informed assessment.
For roles involving significant cross-functional collaboration, client-facing work, or remote arrangements where the manager’s direct observation is limited, gathering input from colleagues, internal clients, or other stakeholders provides a more complete picture. This multi-source approach, commonly known as 360-degree feedback, addresses the inevitable blind spots that arise when a single manager’s perspective is the only input.
The limitation of multi-source feedback is the risk of bias in peer or stakeholder input. Assessors who are not trained to give objective, behavioural feedback may produce ratings that reflect personal preferences or relationship quality rather than actual performance. The manager’s role in a 360 process is to review the input critically, identify patterns consistent across multiple sources, and filter out observations that appear to reflect subjective impressions rather than evidence-based performance.
For most organisations, a pragmatic combination is effective: direct manager assessment supplemented by structured input from key stakeholders for roles where that adds meaningful value, with the manager responsible for synthesising and presenting a coherent overall picture.
Structuring the Meeting
A sixty-minute appraisal has enough time to cover all the necessary ground if the structure is clear and the pacing is disciplined.
Opening the meeting with a collaborative, rather than evaluative, tone matters. The physical setup contributes to this: sitting adjacent rather than directly opposite the employee removes some of the unconscious formality of a formal assessment and signals that the conversation is intended to be two-way. A brief, informal exchange at the start reduces tension and signals that the meeting is about development rather than a verdict.
The employee’s perspective should come early. Asking the employee to speak to their own assessment before the manager presents theirs has several advantages. It gives the employee ownership of the conversation from the outset, surfaces the employee’s understanding of their performance, and reveals where alignment and divergence exist. If the employee already recognises a specific gap, dwelling on it in the manager’s section is unnecessary; the conversation can move directly to what would address it.
The manager’s feedback should be specific and structured. For each area of performance, connecting the observation to specific examples and to the business impact of the behaviour provides clarity and makes the feedback actionable. Feedback that is described in terms of concrete actions and their consequences is both easier to understand and harder to dismiss than feedback expressed in terms of character or personality.
The forward-looking portion of the meeting should receive adequate time, typically the final third of the conversation. This is where development goals are agreed, where support is identified, and where the employee leaves with a clear sense of what the next period needs to look like. If the forward-looking discussion is consistently crowded out by the retrospective assessment, the meeting produces less value and leaves employees feeling assessed rather than developed.
Closing with a summary of the key points agreed and the specific next steps, including when the follow-up will happen, ensures the conversation has a clear output and reduces the risk of misremembering what was agreed.
Giving Constructive Feedback
The most common weakness in appraisal feedback is vagueness. Telling someone they need to be more proactive, more professional, or more diligent does not give them anything specific to change. These are adjectives that describe a desired state without indicating what behaviour would constitute it or what behaviour is currently falling short of it.
Effective feedback is grounded in specific, observable actions and their consequences. Describing what the employee did, when it happened, and its effect on the team, the client, or the business provides the employee with information they can actually act on. Saying that a report submitted two days late delayed the finance team’s review cycle and required weekend working is not a personal criticism; it is a factual account of a cause and effect that the employee can engage with and respond to.
The same specificity applies to positive feedback. Acknowledging that detailed project notes saved the team an hour of catch-up time on a specific project tells the employee what to repeat and why it matters, whereas saying they did a great job provides validation without information.
Managing Defensiveness
Even well-framed feedback can produce a defensive response. This is not a signal that the feedback was wrong or that the approach has failed; it is a normal human reaction to being assessed. The manager’s role is not to prevent it but to manage it to keep the conversation productive.
When an employee challenges or disputes feedback, the most effective response involves three steps. The first is to listen without interrupting. The employee’s perspective may contain information the manager was not aware of, and in any case, feeling heard reduces the intensity of the defensive response. The second is to acknowledge the employee’s experience without necessarily agreeing with their interpretation. The third is to return the conversation to the specific, factual basis of the observation, moving away from a debate about who is right and toward a discussion of what would address the gap.
The question that most effectively bridges from a contested critique to a productive conversation is a forward-looking one: what support or change would prevent this from recurring? This shifts the dynamic from an argument about the past to a collaborative problem-solving exercise about the future.
Setting Development Goals
The most lasting impact of a well-conducted appraisal comes from the development goals agreed at the end of it. Goals that are specific, measurable, achievable, relevant to the role and the employee’s development, and tied to a clear timeframe are far more likely to drive real change than aspirational statements that sound meaningful but leave the employee unclear about what to actually do differently.
For each development goal, it is worth identifying not only what the employee will do but what support the manager will provide. Development is a shared responsibility, and the appraisal is an opportunity to make that explicit.
The development plan should connect the employee’s personal ambitions, where those are relevant, to the organisation’s needs. Employees who can see a clear line between their own development and their career trajectory within the organisation are more motivated to pursue that development. Making that connection explicit, rather than leaving it implicit, is part of the manager’s role in an effective appraisal.
Documentation
The appraisal record should be factual, specific, and objective. The principle for documenting performance observations is the same as for delivering them: describe what happened and its effect, rather than characterising the employee’s personality or intentions.
Comparing documentation across employees in equivalent roles reveals inconsistencies in assessment standards. A senior employee and a junior employee in different roles will have different performance expectations, but the basis for assessment should be consistent within their respective role levels. Using a standardised rating scale with clear descriptions for each level, applied consistently across the team, provides a defensible and equitable record.
The documentation should be completed promptly after the meeting while the details are clear, reviewed by the employee to confirm it accurately reflects what was discussed, and retained in the employee’s personnel file. This record serves as the reference point for the next review cycle and provides the evidentiary basis for any subsequent performance management decisions.
Continuous Feedback as the Foundation
An appraisal that synthesises twelve months of feedback in a single meeting is operating under a significant structural disadvantage. Much of the value that could have come from timely feedback has already been lost; the employee has been operating for months without clarity on whether what they are doing is working. The formal appraisal is most effective when it summarises and consolidates a year of ongoing feedback, rather than substituting for it.
Building regular, shorter feedback interactions into the management rhythm, whether through weekly one-to-ones, prompt acknowledgement of specific behaviours as they occur, or brief quarterly conversations about progress against goals, changes the appraisal dynamic fundamentally. There are no surprises because the relevant conversations have already happened. The annual meeting becomes a structured reflection on a year that has been actively managed, and the development plan for the next period is built on a genuine understanding of where the employee is rather than a rushed reconstruction of the past twelve months.
The follow-up after an appraisal matters as much as the meeting itself. A brief message within 48 hours summarising the key points agreed, confirming the development goals, and scheduling the next check-in converts the conversation into a concrete commitment that both parties can refer back to. Without that follow-up, the intentions discussed in the meeting are vulnerable to being crowded out by the demands of day-to-day work.
IRIS Software Group
Award winning software and solutions for the businesses of the future
Discover why more than 100,000 customers across 135 countries trust IRIS Software Group to manage core business operations