What questions should I ask in a performance review? Get a question bank, scripts, and checklists built for African workplaces.
Marketing Lead
February 13, 2026
•
7 Mins read
What questions should I ask in a performance review — and how do you pick ones that actually lead to decisions? You have one final review meeting, a form open on your screen, WhatsApp pinging, and an employee waiting for clarity on their role, their rating, maybe their pay. This guide gives you a practical question bank, a simple preparation process, and copy-paste scripts built for African workplaces where KPIs are sometimes unclear, documentation is patchy, and culture can make honest feedback feel risky.
You have one last performance review meeting. The form is open. Your WhatsApp is pinging. Your employee is waiting for clarity, maybe money, maybe direction, maybe both.
And you’re thinking: What questions should I ask in a performance review that won’t waste both our time?
This article gives you employee review questions built for Africa — practical, direct, and designed for workplaces where KPIs are sometimes unclear, documentation is patchy, and honest feedback can feel culturally risky.
A performance review question is only “good” if it does one of these things:
If your questions do not end in clarity and actions, they will feel like a yearly ritual and nothing else.
CIPD’s evidence review on performance feedback repeatedly comes back to a boring truth: feedback works better when it is specific, actionable, and handled in a way that considers the recipient’s reaction.
A performance review is a structured conversation (and record) about:
When review questions are weak, you get predictable outcomes:
That “credibility” point isn’t fluffy. Research on feedback conversations shows recipients often doubt the accuracy of mixed or negative feedback, and they judge the person delivering it. The questions you ask can lower defensiveness by anchoring the conversation on evidence and improvement.
If you ask only feelings-based questions, you get vibes, not decisions.
Instead, you want prompts that force concrete examples:
When money is on the table, people edit themselves. That’s normal.
So separate the meeting into parts:
Even HBR’s work on performance reviews and motivation highlights how the design of reviews affects engagement and how people receive the message. If your questions feel like a trap, you’ll get safe answers.
A common reason review questions feel awkward is because goals were never clear.
Specific and challenging goals tend to outperform “do your best” goals, because “do your best” has no shared standard.
So some of your best review questions are actually goal-clarification questions.
Even competent managers fall into rater errors:
A practical mitigation is structured questions per dimension, so you rate less from memory and more from evidence.
In many African orgs (especially SMEs), the hidden constraint is documentation. People do work, but evidence is scattered across email, Slack, WhatsApp, shared drives, and someone’s laptop.
Your questions must end in written commitments:
You don’t need a perfect system. You need a repeatable one.
Pick one primary purpose:
If you try to do all three at full depth in 45 minutes, you’ll do none well.
Constraint acknowledgement #1: Time is limited. So choose your purpose and cut the rest.
Bring a one-page “evidence pack”:
If you have no KPIs, you can still use output evidence. The table below gives options.
Constraint acknowledgement #2: In many teams, KPIs are unclear or change mid-quarter. You can still review performance using deliverables, quality, and reliability signals.
Pick 12–18 questions total.
Use these buckets:
At the end, you want:
If you’re using a platform like Talstack’s Performance Reviews and Goals modules, the advantage is you can keep goals, feedback, and evidence in one place instead of hunting for it during review season. The process still works without the tool, but the admin load is lower when the workflow is structured.
Below are question sets. Use the ones that match your situation and seniority level.
Use these when you need clarity on contribution.
These are useful when output exists, but the team still feels friction.
These help when work is cross-functional and political.
CIPD emphasizes that reactions to feedback matter and suggests checking how the person feels about feedback and whether they see it as fair and actionable. These questions do that without turning the meeting into therapy.
These questions are the difference between “improve performance” and “fix the system.”
Constraint acknowledgement #3: Culture can make honest constraint talk hard. In high power-distance settings, employees may avoid saying “my manager is the blocker.” These prompts let them name systemic issues without attacking a person.
This is where structured learning helps. If you have recurring skill gaps, Talstack’s Learning Paths, Assign Courses, and Course Catalogue are designed for targeted upskilling rather than random training days.
If you’re the employee reading this, these are strong questions that keep the review grounded.
Self-assessments work best when they force evidence.
| Situation | Ask these questions | What you’re trying to learn | What to do next |
|---|---|---|---|
| KPIs are unclear or keep changing | “What were your top 3 outputs?” “What evidence shows impact?” “What changed midstream and why?” | Real contribution despite messy targets | Write 3 priorities for next cycle + monthly checkpoints |
| You feel output is fine but reliability is poor | “Where did rework happen?” “What made deadlines slip?” “What would make delivery predictable?” | Root causes: skill vs system vs workload | Agree on one process change + one skill focus |
| Collaboration complaints or politics | “Where did alignment break?” “Which stakeholder feedback do you accept?” “What’s unfair and what evidence would help?” | Whether it’s behavior, expectations, or context | Define 2 collaboration behaviors + get 360 input next cycle |
| Underperformance without clear incidents | “What were the committed deliverables?” “Which ones missed and why?” “What support was requested and when?” | Pattern, accountability, and support gaps | Document expectations + 30/60/90 plan |
| Evidence source | Examples | What it proves | Risk if you ignore it |
|---|---|---|---|
| Work artifacts | Decks, reports, commits, tickets, SOPs, customer emails | Actual output and quality | Ratings become memory contests |
| Reliability signals | On-time delivery, rework rate, escalations, error logs | Execution discipline | You reward “busy” over “reliable” |
| Stakeholder input | 2–4 short notes from peers, clients, internal partners | Collaboration and trust | Blind spots, politics later |
| Goal progress | Quarterly priorities, OKRs, scorecards | Alignment to what mattered | Work drifts from strategy |
If your org still runs reviews in spreadsheets, you can replicate this “evidence pack” logic by forcing links to artifacts and short stakeholder inputs. If you want less admin friction, Talstack’s Performance Reviews, Goals, and Analytics make that evidence easier to pull at review time.
For review quality, structure matters. SHRM’s guidance on conducting reviews emphasizes being specific about observed behavior and impact, then asking for the employee’s input. That’s what this checklist operationalizes.
“Thanks for making time. I want this to be practical. We’ll do three things: review evidence from the cycle, agree what should change next, and document a simple plan. If anything feels unclear or unfair, say it and we’ll go back to examples.”
“Walk me through the work you’re most proud of. If you can, point to the artifact or result. I’m trying to anchor this conversation on evidence, not memory.”
“I noticed [specific behavior or pattern]. The impact was [specific impact]. For next cycle, I want us to try [specific change]. What would make that doable for you?”
This aligns with evidence-based feedback practice: specific information tied to task and actionability tends to be more useful than vague evaluation.
“I know compensation matters. Today I want us to focus on performance evidence and the plan. I will confirm the compensation timeline by [date/process] and we’ll have a separate conversation if needed.”
“Given what changed this quarter, I don’t want to rate you against goals that no longer make sense. Let’s rewrite the next 3 priorities with clear measures and checkpoints.”
Goal clarity is not a nice-to-have. The evidence base on goal setting consistently favors specific, challenging goals over vague ones.
Use questions that force clarity:
Enough to cover the 5 buckets, not enough to derail the meeting.
A good range is 12–18 questions in a 45–60 minute review.
You can still run a good conversation.
Use the rating form as a record, but ask:
Also, be aware of rater errors like halo and leniency, especially when the rating is the only output.
Ask for specifics:
If the feedback feels like a verdict, not input, you’ll struggle to act on it. Research on feedback conversations shows perceived credibility and accuracy matters a lot.
You can, but be strategic.
If your company separates pay cycles from performance cycles, ask:
If pay is decided in the same meeting, keep it near the end and keep evidence-based.
Make it about work, not personality:
This reduces the social threat while still getting truth.
Avoid “weakness hunting.”
Use:
HBR’s reporting on performance reviews and motivation highlights how review design affects engagement and behavior. Your structure is part of that design.
Many orgs are shifting to more frequent check-ins and simpler performance management designs. Deloitte’s work is one widely cited example.
If you’re not ready for a full redesign, start with one change:
Pick one upcoming performance review and do this:
If you want the same structure without spreadsheet chaos, you can map this workflow into Talstack using Goals (to align priorities) and Performance Reviews (to capture evidence, feedback, and next actions in one place).
