Assessing Yearly Performance When the Bell Curve Is Fixed

A rating curve is not an assessment

When an organisation requires a bell curve, managers may feel they have to decide who belongs in each rating category before they have reviewed the evidence. That reverses the order. A distribution rule can shape how ratings are allocated; it cannot tell a manager what an individual achieved or learned.

A more useful process starts with clear goals, follows progress during the year and reviews evidence before calibration. Employees should know what is being assessed and how the final rating will be decided.

Set business and development goals separately

Business goals describe the results a person is responsible for: for example, delivery against an agreed plan, quality, customer outcomes or reliable execution. Each goal needs a clear measure, timeframe, evidence source and an agreed account of what is within the employee’s control.

Development goals describe capabilities the person is building and how those capabilities should show up at work. A goal such as “improve coaching” is too broad on its own. Make it observable: practise regular coaching conversations, ask questions before giving advice, and use feedback to adjust the next conversation. Course attendance can support development, but it is not proof that behaviour changed.

Keep the two goal types visible as separate lines of evidence. Results answer what was delivered; development evidence helps explain how capability is changing and what support is needed next.

Use the mid-year review to adjust

A mid-year conversation should not be a surprise rating exercise. Review progress against each business goal and development goal, examine examples, and discuss changes in priorities, resources or responsibilities. If a target is no longer realistic or relevant, agree what replaces it and record why.

• What evidence shows progress against the business outcome?
• Where has the employee used the capability they set out to develop?
• What is blocking progress, and what support can the manager provide?
• What should stay, change or stop for the remainder of the year?

Review evidence before calibration

At year-end, assess business outcomes and development progress separately before discussing the organisation’s rating distribution. Compare results with the goals and context agreed during the year, not with a story constructed to justify a predetermined category.

Consider the quality and consistency of evidence: agreed measures, work examples, customer or stakeholder feedback, observations and the employee’s own reflection. Account for changed conditions and opportunities. Do not treat someone’s development need as evidence that their business results were poor—or treat one strong result as proof that every capability is strong.

If a forced distribution changes how ratings are allocated, explain that calibration is a separate step. Preserve the evidence-based assessment, apply the organisation’s policy consistently and avoid presenting relative placement as a complete description of a person’s contribution.

Compare evidence, not personality

Consider this fictional example. Asha and Rohan have the same role and agreed business goal: deliver their project commitments to the agreed quality and flag risks early. Each also has a development goal to strengthen stakeholder communication.

Asha meets the delivery commitments and raises a risk early enough for the team to adjust. Her stakeholder updates are clearer by mid-year, and colleagues can point to examples of her checking understanding before agreeing next steps. Her evidence supports strong business results and visible progress on her development goal.

Rohan misses several milestones. The manager checks whether scope, resources or dependencies changed and invites Rohan to explain. In this example, the conditions were comparable, support was available, and project notes show that risks were not raised despite agreed check-ins. His updates also remain inconsistent after feedback and practice. That evidence points to missed business expectations and a development goal that still needs focused support.

The difference is not that Asha is naturally more committed or that Rohan has a worse attitude. It is the evidence against shared expectations, alongside the context and opportunity each person had. If their situations were not comparable, the manager would need to account for that before drawing a conclusion.

If a bell curve places Asha in a higher category and Rohan in a lower one, the manager should be able to explain the distinction using documented outcomes and behaviours. If the evidence is similar, do not invent a performance gap just to fill the curve; clarify how the organisation expects calibration to work and explain any constraint honestly.

Make the year-end discussion clear

A useful discussion makes room for both people. The manager shares the evidence and explains the rating; the employee can add context, question gaps and describe what support would help. Close by agreeing the next business priorities, development goals, measures and review dates.

The bell curve may be fixed. Clarity about goals, evidence and decisions is still within the manager’s control. Use the downloadable checklist to review your goal setting, mid-year conversation and year-end discussion.