Performance Management
There is a version of this problem that almost every organisation recognises. The appraisal window opens. Managers complete the forms in the last three days. Almost everyone lands between three and four out of five. The scores go to HR, HR aggregates them, and the output is a distribution that tells you nothing you could act on. Then someone asks who the top performers are and the honest answer is that the system cannot say.
Meanwhile the two people everyone privately agrees are carrying their teams got the same rating as the person nobody wants to be assigned to.
What is actually breaking
Ratings inflation is a rational response to a system with no consequences for inflating. If a manager gains nothing from an honest three and gains a difficult conversation, a possible grievance and a demotivated team member, the manager will write four. This is not a character problem in your managers. It is a design problem in your process.
The second failure is that objectives are written once and never referred to again. They are set in January in language vague enough to be defensible in December, and no one revisits them when the priorities change in March.
The third is the absence of calibration. Without a moderation step where managers sit together and defend their ratings against a common standard, every department is running its own private scale, and cross-department comparison is meaningless. Which means promotion and reward decisions made from the output are meaningless too.
The fourth is documentation. The conversation about underperformance happened, in a corridor, in April, and nothing was written down. Twelve months later that absence becomes a live legal problem.
What we build
We build the cycle end to end, sized to the organisation rather than imported whole from a template.
That starts with the objective architecture: how organisational priorities cascade into departmental and individual objectives, in language specific enough to be assessed, with a defined mid-cycle review point where objectives are formally revisited rather than quietly abandoned.
Alongside that sits the behavioural half. What competencies matter at each level, described as observable behaviour rather than adjectives, so that a rating conversation can point at something concrete. Where you already have a job architecture in place, we anchor these to it directly.
Then the machinery. Rating scale design and, importantly, the decision about whether to use a forced distribution and what that will cost you in trust. Calibration session structure and facilitation, including how to run the first one, which is always the hardest. Documentation standards. A performance improvement process with defined stages, timelines and evidentiary requirements. And the link to reward, which is where most systems either gain or lose their credibility permanently in the first cycle.
We usually run the first calibration cycle alongside your team rather than handing over a document and leaving. The design is not the difficult part. The first time a manager has to defend a rating in front of peers is the difficult part.
The record it leaves behind
One consequence of running the cycle properly is worth naming, because it is the part organisations tend to think about only once it is too late.
Performance management in Nigeria is no longer purely an internal matter. The National Industrial Court applies international best practice in labour and employment, and the older assumption that an employer may terminate for any reason or no reason, provided notice is given, has been steadily narrowed. The Court has been willing to examine whether a fair process was followed, and awards in individual matters have reached substantial sums.
The practical consequence is straightforward. If you separate from someone for performance, the file needs to show that the standard was communicated, that the shortfall was raised, that support and a reasonable period to improve were offered, and that the decision followed from evidence rather than preceding it. A system that produces that record as a by-product of running normally is worth considerably more than a policy document describing one, because the policy document is written in advance and the record is written as things happen.
There is a related risk at the other end, and it is the more common one. Where a manager has no legitimate route to address underperformance, they improvise: responsibilities are quietly removed, a reporting line is changed, a role is made untenable in the hope that the person resigns. That is constructive dismissal exposure, and the file will show exactly what happened. We design the improvement process so that managers have a real option and are not driven to invent one.
How engagements run
Design work typically runs six to ten weeks: current state review, framework design, documentation, manager briefing materials. Where you want us present for the first full cycle, add the cycle length, and expect our involvement to be concentrated at objective setting, mid-cycle review and calibration. Fees are quoted in NGN against an agreed scope.
Where this connects
Performance management is the operating system. Culture is the environment it runs in. If managers avoid difficult conversations because the organisation punishes candour, no framework will fix that on its own, and culture transformation is the more honest place to start.
The link between rating and reward is where most systems are judged, and it only works if the pay structure underneath it is coherent. Job architecture and pay progression covers levelling and progression, and learning and development covers what happens after a review identifies a capability gap that someone actually has to close.
To discuss your current cycle, email consulting@sahrpartners.com or use the enquiry form.
Culture transformation (ACTIVATE)