Performance Reviews: Competencies, Evidence and Development

Define what the review is for

Decide which management questions the cycle should answer before choosing a form: who delivered the agreed work, who needs support and who may be ready for greater responsibility.

Keep performance, competencies and potential distinct. Performance describes period outcomes; competencies describe observable behavior; potential is a forward-looking judgment, not the score for work already done.

Select the review model deliberately

• Manager review: feedback from the person accountable for the employee’s work.
• Manager plus self-review: exposes differences in perception and starts a structured conversation.
• Multi-source or 360-degree review: adds peers and other relevant perspectives, requiring clear confidentiality rules and suitable participants.

Use observable competencies

Replace vague labels such as commitment or proactivity with behaviors described using a verb and context. Apply competencies relevant to the role, rather than asking every employee the same generic questions.

• Instead of “communicates well”: records meeting decisions and flags deadline risks early.
• Instead of “is organized”: maintains tasks and sales records without repeated reminders.
• Instead of “is a team player”: coordinates handoffs and helps resolve agreed team blockers.

Describe the rating scale and calibrate

A five-point scale allows a midpoint; a four-point scale asks the reviewer to choose a side. Neither prevents bias by itself. Describe the evidence expected at every level.

1. 1Write a behavioral description for each rating.
2. 2Ask for supporting examples, especially for extreme scores.
3. 3Compare interpretation across managers before sharing results.
4. 4Document calibration decisions and explain the final feedback.

Turn feedback into a development plan

A short plan with practical actions and a review date is more useful than a long list of intentions. Connect development to the work the employee can actually practice.

1. 1Choose one or two competencies to develop next.
2. 2Set a practical action, date and way to demonstrate progress.
3. 3Schedule a mid-period check-in with the manager.
4. 4Review the previous plan before starting the next formal cycle.

Avoid common biases and protect confidentiality

• Halo effect: one notable result influences unrelated ratings.
• Recency bias: the final month replaces evidence from the whole period.
• Inflated ratings to avoid difficult conversations.
• Collecting responses without returning useful feedback.
• Reviewers without enough knowledge of the employee’s work.
• Promises of anonymity that small groups or detailed comments cannot support.

Keep the cycle connected to development

Moove brings review cycles, an editable competency library, response consolidation and development plans into the management workspace. Configure access for the people who need to participate.

Define who can see individual responses and consolidated results before collecting feedback. Treat personnel data according to your organization’s policies and applicable local requirements.