A competency framework without outcome measurement tells you what kind of person an employee is at work. An outcome measurement without competency assessment tells you what happened but not why, or at what cost.

The most credible performance rating is one that integrates both: the employee demonstrated these capabilities, and as a result, they delivered these outcomes. That integration is what allows a performance rating to drive development planning, talent decisions, and accurate calibration simultaneously.

This article explains how to combine competency ratings with outcome measures in a way that is practical for African HR teams with limited resources and multiple functions to manage.

The three ways competencies and outcomes relate

Competency as prerequisite for outcome

Some competencies are required to achieve the outcome consistently. A sales executive cannot sustain a high close rate without communication and negotiation competencies. A project manager cannot consistently deliver on time without planning and stakeholder management competencies.

In this relationship, the competency rating and the outcome rating should be broadly aligned. If they diverge significantly (strong outcome, weak competency), it suggests either the outcome was achieved through exceptional circumstances unlikely to repeat, or the competency was assessed too harshly.

Competency as quality indicator for outcome

Other competencies determine the quality of the outcome rather than whether it happened. Two employees might both deliver a project on time. One delivered it by overloading the team and creating a quality problem downstream. The other delivered it through effective coordination that reduced workload and improved quality.

Here the outcome rating is the same; the competency rating differentiates how the outcome was achieved. The employee who delivered through collaboration and quality thinking deserves a higher overall rating than the one who delivered by creating collateral damage.

Competency as development indicator beyond current outcomes

Some competencies predict future performance potential rather than explaining current results. An employee who is demonstrating strong analytical competency in a role that does not currently require it is signalling readiness for a more complex role.

In this relationship, the competency rating can be used in the development and talent review conversation even when it does not directly affect the current cycle's overall rating.

A practical integration model

For most African organisations, a five-step integration model produces a defensible, useful combined rating:

‍

1. Document the outcomes: list the key goals or KPIs and the level of achievement for each. Score them on the rating scale
2. Document the competency ratings: for each defined competency, what rating does the evidence support?
3. Flag significant divergences: where outcome rating and competency ratings diverge significantly, add a narrative note explaining the divergence. This is the most important step for calibration and dispute management
4. Apply the weighting appropriate to the role (see KPI/competency weighting table in the previous article)
5. Review the blended score for reasonableness: does it match the overall picture of this employee's contribution? If a manager looks at the score and thinks "this does not feel right," the narrative section is where they explain why and what context adjusts the interpretation

‍

Examples of divergence and how to handle it

What the narrative section should contain

A combined rating without narrative context is a number without a story. The narrative section of the review should explain:

• The context in which the outcomes were achieved: what conditions made them harder or easier?
• The specific competency evidence: which behaviours supported the competency ratings?
• Any divergences and why they exist
• The one or two development implications that flow from the combined picture

In Talstack's Performance Reviews module, the review form supports both structured ratings and narrative sections, with check-in notes and 360 feedback data accessible to the manager within the review workflow. The manager does not need to reconstruct the year from memory; they have the documented year already available when writing the narrative.

Frequently asked questions

How many competencies should be rated in a single review cycle?

Three to six core competencies is the right range for most roles. More than six creates review fatigue and produces generic ratings because managers cannot maintain specific attention across too many dimensions. Fewer than three is not enough to capture the behavioural picture of performance. For leadership roles, add two or three leadership-specific competencies to the core set.

Should self-assessed competency ratings be included in the blended score?

Self-assessed ratings should inform the conversation but typically should not be mechanically averaged into the blended score. Self-assessments are useful for identifying perception gaps: where the employee rates themselves significantly higher or lower than the manager, that divergence is worth exploring in the review conversation. Using self-assessment as a direct input into the score creates gaming incentives that undermine the honesty the self-assessment is designed to produce.

The bottom line

A combined rating that integrates both what was delivered and how it was delivered produces a performance record that reflects the whole picture of an employee's contribution. It prevents the two most common rating distortions in isolation: the outcome-only rating that rewards results regardless of collateral damage, and the competency-only rating that rewards professional style regardless of whether it produced anything.