In a performance review, you as a manager provide a well-founded reflection on an employee's functioning over an agreed period, followed by concrete agreements for the future. The conversation is effective when it does not come as a surprise, but as a logical conclusion to earlier discussions. In this article, we answer the most frequently asked questions about preparation, content, and follow-up.<\/p>\n
Good preparation starts with gathering concrete examples from the review period. Think about results achieved, specific situations in which the employee performed well or less well, and previously made agreements. Both the manager and the employee prepare in advance; this turns the conversation into a two-way exchange rather than a one-sided judgment.<\/p>\n
In practical terms, it helps to work through the following steps:<\/p>\n
A common mistake is basing the conversation on impressions from the past few weeks rather than the entire period. Make sure you have a complete picture, not just a recent snapshot.<\/p>\n
A performance review typically covers three main themes: the results achieved relative to set goals, the behaviour and competencies the employee has demonstrated, and their development and ambitions for the coming period. Together, these themes provide a complete picture of both what someone has done and how they have done it.<\/p>\n
Concretely, you can think of:<\/p>\n
Keep the conversation focused. Do not try to cover everything at once; choose the topics that matter most to this particular employee at this particular moment.<\/p>\n
Honest feedback is specific, behaviour-focused, and always linked to a concrete example. Do not say \"you don't communicate well,\" but instead describe what you observed: \"During last month's meeting, I noticed that your colleagues were not given space to respond.\" This keeps the feedback recognisable and discussable, without it feeling personal.<\/p>\n
A helpful structure is the SBI method: describe the Situation<\/strong>, the Behaviour<\/strong> you observed, and the Impact<\/strong> it had. This prevents feedback from being experienced as an attack and makes clear why something is relevant.<\/p>\n Positive feedback deserves just as much attention as points for improvement. Explicitly name what is going well and why it is valuable for the team or the organisation. This creates balance and keeps the employee receptive to the points that could still be improved.<\/p>\n As an employee, you have the right to share your own perspective if you disagree with a review. Do this calmly and factually: identify which part you experience differently and support that with concrete examples. Avoid a defensive or emotional reaction, as this makes it harder to be heard.<\/p>\n Practical tips for this moment in the conversation:<\/p>\n A difference of opinion does not have to disrupt the conversation. It only becomes a problem when it cannot be discussed openly. A manager who is open to pushback builds more trust than one who simply imposes a judgment.<\/p>\n Agreements only become valuable when they are specific, realistic, and measurable. Vague agreements such as \"you will take more initiative\" quickly disappear into a drawer. Instead, formulate: \"You will take the lead in the new project meeting before the end of the quarter.\" This makes it clear to both parties what is expected and when.<\/p>\n After the conversation, these are the steps that make the difference:<\/p>\n Follow-up is also the responsibility of the manager. If you do not monitor the agreements, you implicitly signal that they are less important. Make it a habit to look back at what was agreed at the start of every subsequent conversation.<\/p>\n A performance review is a formal, one-sided judgment by the manager about the employee's functioning over a past period, often linked to a salary step or employment-related consequence. A development conversation is a two-way discussion about current functioning, focused on growth and collaboration, without direct legal or financial consequences.<\/p>\n The practical difference lies in the goal and the tone. A development conversation centres on improvement and mutual expectations. A performance review is about a concluded judgment. Both conversations are valuable, but they require different preparation and a different attitude from both parties.<\/p>\n In practice, the two conversations regularly overlap. That is understandable, but it helps to consciously separate them. When employees know that a conversation is purely focused on development, with no direct review attached, they are generally more open and honest.<\/p>\n Performance reviews rarely stand alone. They are most effective when embedded in a culture of continuous listening, where employees are heard throughout the entire year, not only during a formal moment. That is precisely where CYS Group helps organisations.<\/p>\nWhat do you say as an employee if you disagree with your performance review?<\/h2>\n
\n
How do you make agreements that are actually followed up after the conversation?<\/h2>\n
\n
What is the difference between a performance review and a development conversation?<\/h2>\n
How CYS Group helps with employee engagement and follow-up<\/h2>\n