Learn how to combine competency ratings with outcomes so your performance ratings reflect both how employees work and what they deliver.
Marketing Lead
May 21, 2026
•
4 Mins Read
Combining competency ratings with outcomes is the only way to build a performance rating that is both accurate and actionable. A competency framework alone tells you what kind of employee someone is at work; outcome measurement alone tells you what happened but not why, or at what cost. The most credible rating integrates both — this employee demonstrated these capabilities and delivered these results. For African HR teams managing multiple functions with limited resources, this article provides a practical model for making that integration work.
The most credible performance rating is one that integrates both: the employee demonstrated these capabilities, and as a result, they delivered these outcomes. That performance rating integration is what allows ratings 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.
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.
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.
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.
For most African organisations, a five-step integration model produces a defensible, useful combined rating:
| Scenario | Outcome rating | Competency rating | Likely explanation | Action |
|---|---|---|---|---|
| High outcomes, low competency | Above expectations | Below expectations on collaboration | Results achieved at cost to team relationships or process quality | Acknowledge outcomes; address competency gap explicitly in development plan; flag sustainability risk |
| Low outcomes, high competency | Below expectations | Above expectations | External factors limited output despite strong capability; or goals were unrealistic | Investigate context before finalising; adjust outcome rating if external factors were material |
| Consistent alignment | Meets expectations | Meets expectations across most | Standard performance across both dimensions | Straightforward combined rating; development plan focuses on one or two targeted growth areas |
| Inconsistent competency profile | Meets expectations | Exceeds on some, below on others | Uneven capability profile; specific strengths and gaps | Note the profile in the review; development plan targets specific gaps rather than generic improvement |
A combined rating without narrative context is a number without a story. The narrative section of the review should explain:
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.
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.
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.
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.
