Learn how to write SMART goals for performance reviews with examples, templates, and a step-by-step process built for African HR teams.
Marketing Lead
February 20, 2026
•
5 Mins read
You open the performance review spreadsheet and see it again:
“Improve communication.”
“Be more proactive.”
“Support the team.”
You open the performance review spreadsheet and see it again: "Improve communication." "Be more proactive." "Support the team." If you want to know how to write SMART goals for performance reviews, this is exactly the problem you are solving — turning vague intentions into goals a manager can score fairly, with evidence, even when your team is moving fast and documentation is messy.
This is where the focus keyword matters: how to write SMART goals for performance reviews is really about one thing. Turning “good intentions” into goals you can score fairly, even when your documentation is messy and your team is moving fast.
SMART goals are Specific, Measurable, Achievable, Relevant, and Time-bound.
If you want a working definition you can use in HR and manager training:
When goals are vague, three predictable things happen.
If the goal is “Improve stakeholder management,” the rating depends on who is louder in the calibration meeting.
SMART goals reduce ambiguity. That does not remove bias completely, but it gives you something concrete to debate: evidence, not personality.
In many African companies, you are juggling:
When the goals are vague, your compensation decisions become harder to defend internally. If you’ve ever had to explain a raise decision to a founder who wants “numbers,” you know the pain.
One cycle of unclear expectations and surprise ratings can kill engagement for a whole year.
This is also consistent with what performance management bodies in Africa emphasize: goal setting and performance management need clarity, alignment, and shared expectations, not just forms.
Goal-setting research has repeatedly found that clear goals improve performance more than vague “do your best” intentions, especially when goals are specific and challenging. That’s the spine of goal-setting theory associated with Locke and Latham.
You do not need a PhD to use this. You just need goals that can be verified.
You can memorize SMART and still end up with weak goals. Here are the patterns that quietly wreck performance reviews.
Now the constraint acknowledgements, because this is real life:
Before SMART, write one sentence:
“This role exists to produce ______.”
Examples:
If you skip Step 0, you get busywork goals.
A good test:
If you read the goal to a stranger, can they tell what “done” looks like?
Bad: “Improve reporting.”
Better: “Deliver a weekly operations report that tracks OTIF, stockouts, and top 3 blockers for Lagos DC.”
In African orgs, measurement often fails because the data is not clean, not because people are lazy.
So use two measurement layers:
Example evidence artifacts:
This is where SMART becomes review-friendly.
Do a quick check:
If the employee is already carrying two roles, write that down. Achievable is not a moral judgment, it’s planning.
Tie each goal to one of:
If you cannot tie it, it might be personal development. That’s still valuable, but label it honestly.
A performance review cycle is long enough for reality to change.
Use:
This prevents relevance drift.
| Role example | Vague goal | SMART goal | Evidence for the review |
|---|---|---|---|
| Customer Support Lead | Improve customer support | Reduce first response time from baseline to under 30 minutes for priority tickets by end of Q2, while maintaining CSAT ≥ 4.3/5 | Ticketing export, CSAT report, 3 sample escalations documented |
| Operations Manager | Improve delivery | Increase on-time-in-full (OTIF) from baseline to 92% for Lagos routes by end of Q3 through 2 process changes and weekly blocker reviews | OTIF dashboard, weekly report, SOP update, route exception log |
| Finance Officer | Be more accurate | Close monthly books by the 5th business day for 6 consecutive months with zero high-risk reconciliation breaks | Close calendar, reconciliation sign-offs, audit notes if any |
These are written the way I’d want to see them in a real cycle: outcome, metric, timeframe, evidence.
If you want a simple way to digitize this without living in spreadsheets, this is where platforms like Talstack Performance Reviews and Goals help. You set goals, align them to company priorities, and keep evidence in one place so review meetings stop becoming memory contests. (That “one place” matters when documentation is scattered across tools.)
Use this structure:
By [date], I will [specific outcome] measured by [metric], from [baseline] to [target], by doing [key actions], verified by [evidence].
If you are missing baseline data, say it upfront:
That honesty saves you later.
If you want to operationalize this across a company, a big unlock is standardization: same template, same evidence rules, same checkpoints. That is the practical difference between “we do reviews” and “reviews actually improve performance.”
“Send me 2–4 draft goals for this review cycle using this format: outcome, metric, baseline, target, end date, evidence. I’ll edit with you. If you don’t have baseline data, write how you’ll get it in Month 1.”
“I’m hearing ‘improve communication.’ Let’s turn it into something we can score. What would success look like in behavior and evidence? For example: weekly stakeholder update, fewer escalations, faster approvals. Which one matters most for your role?”
“This cycle, we’re tightening goals to reduce surprises at review time. Every goal must have a measurable target or a clear evidence artifact. If your role has weak KPIs, use evidence artifacts. We’ll share examples by department and do a 30-minute manager clinic.”
Use a 4-point scale tied to evidence:
This works even when your KPI system is imperfect. It gives structure.
SHRM’s performance management content frequently emphasizes clarity of expectations and the value of measurable goals as part of fair evaluation.
No. Some roles lack clean KPIs.
Still make it measurable using evidence artifacts: an approved SOP, a signed reconciliation, a completed rollout with adoption proof, a ticket audit. The “M” is really “verifiable,” not “math-only.”
For most roles: 3–5 goals per quarter or 5–7 per half-year.
More than that usually means you are confusing goals with task lists. Time constraint is real.
Update the goals at a checkpoint. Document the change and why.
Otherwise you punish people for doing the work leadership asked for later. It is a trust killer.
Yes, but you must define the evidence carefully.
Example: “Improve cross-functional alignment” becomes “Run a monthly leadership operating review with a published decision log and reduce blocked initiatives from baseline to X.”
Then the review process will stay subjective.
If you cannot fix manager behavior immediately, reduce the blast radius:
This is where a tool can help. Even basic structured prompts reduce “I forgot.”
Not always.
SMART goals are great for individual performance review cycles. OKRs are great when you need alignment across teams and you want shared outcomes.
Many companies in Africa run a hybrid: OKRs at company or department level, SMART goals at individual level.
Start with one department for one quarter.
Collect examples, refine the template, then expand. You are building a muscle, not launching a policy.
Pick one employee this week and rewrite just two of their current goals using the SMART template and an evidence plan.
If you want to scale it across the org without drowning in spreadsheets, set up a single shared workflow where goals, checkpoints, and evidence live together. That is the part most teams underestimate until review season hits.
