Performance reviews only add value when they connect individual work to company goals. Here is how to build that alignment in African organisations of any size.
Marketing Lead
April 29, 2026
•
5 Mins Read
A performance review that measures what an employee did without asking whether it contributed to what the company needed to achieve is a very expensive progress report.
Strategy alignment is the bridge between individual performance and organisational impact. When it works, every rating conversation answers a more useful question than "did this person do their job?" It answers: "did this person's work move the company forward?"
This article explains how to build that alignment in practice: from setting company-level goals that cascade to individual OKRs, to designing review criteria that connect to strategic priorities, to communicating the link clearly enough that employees can see it in their own work.
The most common failure is that company strategy exists in a leadership document that no individual contributor has ever read, and review criteria exist in an HR form that was designed three years ago for a different version of the company.
The result: employees are rated on competencies that no longer match the company's actual priorities. Managers give feedback based on their own interpretation of what matters. High performers in the wrong strategic direction look like strong contributors on paper.
According to WTW's 2025 research, only 39% of organisations feel their performance management process effectively meets expectations around clear goals. That gap exists precisely because most review designs stop at the individual level rather than connecting to the organisational level.
The starting point is a clear set of company-level goals for the review period. These are not aspirational statements. They are specific, measurable outcomes the organisation is trying to achieve: revenue target, market expansion milestone, product delivery goal, cost efficiency target.
In a Nigerian fintech or Kenyan retail company where strategic priorities shift frequently, these goals should be set quarterly, not annually. An annual strategy document is not useful as a review anchor if it was written 10 months ago.
Each department's objectives should show explicitly how they contribute to one or more company goals. Marketing's goal to generate 500 qualified leads connects to the company's revenue target. Operations' goal to reduce process cycle time connects to the company's efficiency target.
If a department cannot state how its goals connect to company goals, that is a strategy communication problem that needs to be fixed before the review cycle opens, not during it.
Individual OKRs should trace back to department objectives. The objective and key results model from Google's playbook is the most practical framework: the objective is the direction, the key results are the measurable milestones. Key results at the individual level should be derivable from team or department key results.
Talstack's Goals module supports this architecture directly: OKRs can be set at company, department, team, and individual level, with visibility of how each level connects. When a manager wants to explain to an employee how their work connects to the company's direction, the answer is one screen away rather than a ten-minute verbal explanation.
The final alignment step is ensuring that the review criteria, including the competencies rated and the performance dimensions assessed, reflect what the company actually needs to succeed right now.
If the company's strategic priority is customer retention, a review form that rates employees on "new business development" without weighting customer success behaviours is misaligned. Review criteria should be audited against strategic priorities at least once a year.
Goal cascading fails when it becomes a top-down directive rather than a collaborative translation. When a department head takes a company goal and breaks it into individual targets without involving team members, those targets feel imposed and arbitrary.
A more effective approach: share company goals transparently at the start of each quarter, ask each team to discuss how their work connects to those goals, and have each individual write their own OKRs as a draft that the manager then reviews and connects to the team's direction.
This process takes more time upfront. It produces significantly higher goal commitment and, as a result, better review conversations because both parties genuinely believe the goals matter.
How review conversations are framed either reinforces or undermines strategic alignment. Two simple language changes make a significant difference:
If company strategy is genuinely unclear, individual performance cannot be fairly evaluated against it. The honest step is for HR to surface this problem to leadership before the review cycle opens, not to design around it. A company that cannot state its 90-day priorities cannot run a meaningful performance review. The review process can serve as the catalyst for forcing that clarity.
Different functions have different strategic contributions: a product team contributes through feature delivery, a finance team through cost management, a customer success team through retention. The alignment architecture must allow for different objectives at the function level while tying them all to the same company-level outcomes. One set of universal competencies plus function-specific performance dimensions is the most practical design.
Strategy alignment turns performance reviews from an HR administrative exercise into a tool for execution. When employees can see how their work connects to what the company is trying to achieve, they engage differently with the review conversation: they see it as relevant rather than bureaucratic, and they use the feedback to orient themselves rather than just to process a rating.
The investment is a working goal cascade, an audited review criteria set, and review language that connects individual contribution to business outcome. That is a one-time design effort that pays back in review quality every cycle.
%20(1).jpg)
%20(2).jpg)
%20(1).jpg)
