Run lightweight quarterly growth conversations that employees actually find useful: the right questions, a simple structure, and how to make them Africa-relevant.
Marketing Lead
.png)
April 4, 2026
•
6 Mins Read
Most employees in Africa have never had a growth conversation with their manager. They have had performance conversations, which usually involve a rating, and status updates, which involve progress reports. Neither is a growth conversation.
A growth conversation is a dedicated discussion about where an employee wants to go and how the organisation can help them get there. It is not about this quarter's OKRs. It is not about a promotion decision. It is about development: skills, aspirations, and the specific support needed to move in a meaningful direction.
Done quarterly, these conversations take less than an hour each and produce more employee engagement than almost any other single HR intervention. This article gives you the lightweight version: a clear structure, the right questions, and the practical guidance to make them work in Nigerian, Kenyan, and Ghanaian company contexts.
A performance review answers: how did you do against your goals? A growth conversation answers: where do you want to go, and what would it take to get you there?
The two conversations require different conditions. Performance reviews carry stakes: ratings, pay, promotion decisions. That weight makes employees guarded. Growth conversations should feel exploratory and safe. The manager's job is not to evaluate but to listen, probe, and help the employee think clearly about their development.
In many African workplaces, especially in hierarchical environments in Lagos, Accra, and Nairobi, employees have been conditioned to tell managers what managers want to hear. A growth conversation only works if the employee believes the manager is genuinely interested in their answer and will not use it against them. That psychological safety needs to be established explicitly.
These four questions provide the backbone of a 45-minute growth conversation. The manager sends them to the employee three days before the meeting so they can reflect before arriving.
Part 1: Looking back (10 minutes)
Ask the employee to reflect on the past quarter from a development perspective, not a performance one. What did they learn? What challenged them? What felt like growth?
Resist the urge to shift into performance review mode here. If you start evaluating rather than listening, the employee will switch into defensive mode and the growth conversation is over.
Part 2: Looking forward (20 minutes)
Work through questions 1 and 3 from the four-question framework. Let the employee lead. Your job is to ask follow-up questions and help them get specific. "Be a better leader" is not a growth goal. "Get confident enough to run a team of five without checking with me on every decision" is a growth goal.
In this section, note the gap the employee identifies between their current capability and their aspiration. That gap is the development target.
Part 3: Support and commitments (10 minutes)
Ask question 4: what do you need? Make specific commitments. Not "I will look into that," but "I will find you two people to have a coffee conversation with in the next three weeks," or "I will enrol you on Talstack's Learning Path for people leadership by the end of this week."
Write down every commitment you make. Share the note with the employee after the meeting. If you make a commitment and do not follow through, you have taught the employee that growth conversations are theatre, not reality.
Part 4: Closing (5 minutes)
Agree on one development action the employee will take before the next quarterly conversation. One. If you agree on five, they will do none. Ask them to be specific about the action, the timeline, and how they will know it is complete.
One of the most common constraints in African companies is learning and development budget. The standard response to a growth conversation is "we can enrol you on a training course," but training budget is often frozen, and most training does not transfer to the job anyway.
There are better, lower-cost development options for most growth goals:
In most Western HR literature, employees are assumed to have clear career aspirations. In reality, especially in African companies where career ladders are often unclear or non-existent, many employees have never been asked where they want to go and have not developed a clear answer.
This is not a problem. It is a starting point.
When an employee says "I'm not sure" or "I just want to do my job well," do not interpret that as absence of ambition. Ask instead:
These questions bypass the abstract "career goals" frame and access the actual energies and interests underneath. Start there. The growth conversation does not need to produce a five-year plan; it needs to produce one specific next step.
A monthly check-in is work-focused: progress, blockers, priorities. It operates at the level of the current 30 days. A quarterly growth conversation is person-focused: aspirations, capabilities, development. It operates at the level of the next 12-18 months. Both are important; neither replaces the other.
Keep them separate. If the employee thinks their growth conversation will be used to evaluate their performance rating, they will manage the conversation rather than be honest in it. Growth conversations inform development planning. Performance reviews assess delivery against goals. The information flows from performance data to growth conversation, not the reverse.
This is one of the most useful things a growth conversation can surface. If a key employee wants to develop in a direction the organisation cannot support, you know this early enough to either find a creative solution (a new role, a different team, a hybrid path) or to begin managing the eventual departure well. Learning this in a growth conversation is infinitely better than learning it in a resignation letter.
A quarterly growth conversation is 45 minutes, four questions, one specific commitment, and one follow-up action. That is the entire cost.
The return is an employee who believes their manager cares about their future, not just their output. In markets like Lagos, Nairobi, and Accra where mobile talent is scarce and recruitment is expensive, that belief is not soft. It is a retention mechanism.
Talstack's Goals module supports the development action that comes out of growth conversations: setting a personal development OKR, assigning a Learning Path, and tracking progress quarter over quarter. The conversation creates the intention; the system keeps it alive.