A performance review without a development plan is an evaluation without a purpose. Here is how to connect the two in African organisations effectively.
Marketing Lead
April 30, 2026
•
5 Mins Read
Most performance reviews end with a rating and a signature. The employee leaves knowing where they stand on a scale. They do not leave knowing what to do next, who will help them, or what the organisation is prepared to invest in their growth.
That gap between evaluation and development is the most expensive design failure in performance management. It is also the most fixable.
This article explains how to design and run development planning as an integral part of the performance review cycle, including what belongs in a development plan, how to have the development conversation, and how to follow through in a way that produces actual skill change rather than a document filed and forgotten.
The most important structural principle is also the most counterintuitive: connect development planning to the performance review cycle, but do not conduct both conversations in the same meeting.
When the development conversation happens in the same session as the rating conversation, employees are mentally processing their rating rather than thinking about their growth. The development plan becomes something they agree to in order to end the meeting, not something they own.
Best practice: complete the rating conversation first. Schedule the development conversation within two weeks. In the development conversation, use the review data as a starting point: "Your review showed that X is a genuine strength this cycle. The gap I want to explore is Y. Let us talk about where you want to go and how we close that gap."
A development plan that actually changes behaviour contains six elements. A development plan that produces a document nobody looks at contains a list of generic training courses.
Employees who leave with five development goals achieve none of them. The goal is not to document all of someone's growth areas. It is to focus energy on the one or two gaps that matter most for the next six months.
The development goal should be explicitly connected to either what the current role requires the employee to do better, or where the employee wants to go next. A development goal that sits disconnected from both has no anchor. It will not be pursued.
Training courses are one development tool. They are often the default because they are easy to specify and easy to document. But research on development effectiveness consistently shows that 70% of meaningful learning happens through on-the-job experience, 20% through relationships (coaching, mentoring, peer learning), and 10% through formal training.
A useful development plan specifies the experience: the stretch assignment, the cross-functional project, the shadowing opportunity, the mentor relationship. The training course, if relevant, is a supporting element, not the whole plan.
Talstack's Learning Paths give employees structured, role-relevant learning sequences that can be assigned as a development plan action. They are one component of a good development plan, and the most practical one to assign in African companies where budget for external training is often limited.
The development plan is not just about what the employee will do. It includes at least one specific commitment from the manager: what they will do to support the development goal. This might be arranging a stretch assignment, making an introduction, providing coaching sessions, or removing an obstacle.
A development plan that only specifies employee actions and zero manager actions is not a partnership. It is homework.
"Work on your presentation skills" is not a development goal. "Deliver two team-wide presentations with prepared materials before the next quarterly review" is. The difference is specificity of action and evidence of progress.
Development plans should be reviewed mid-cycle, not only at the next formal review. A brief 20-minute check-in at the six-week mark asks: have you started the action? What is getting in the way? Do we need to adjust the plan?
Talstack's Performance Reviews module connects the review outcome to a development action in the same workflow: the manager completes the rating, identifies development areas, and assigns a Learning Path or sets a development goal in the Goals module. The employee sees the connection between their review and their development plan without needing a separate conversation to establish it.
The Analytics dashboard gives HR visibility into development plan completion rates across managers and teams, which surfaces the managers who are strong development partners and those who need support in this area.
The employee owns their development. The manager supports it. In practice, this means the employee drafts or co-creates the development goals, commits to the actions, and is accountable for progress. The manager removes obstacles, makes commitments, and provides the coaching conversations. HR provides structure, tracks completion, and can provide resources. Development plans fail when either the employee feels no ownership or the manager makes no visible commitment to support.
The most valuable development actions in most roles cost nothing: stretch assignments within the current role, cross-functional exposure, peer mentoring, internal knowledge-sharing sessions. External training budget is a useful supplement but not the prerequisite for meaningful development planning. In Kenyan SMEs and Nigerian startups where development budgets are often zero, the constraint forces more creative and often more effective development design than a training catalogue would produce.
A performance review that produces a rating but no development plan has documented where someone is and done nothing to help them get somewhere better. The development plan is not an appendix to the review. It is the reason the review matters.
One or two specific development goals, with learning actions that go beyond training courses, with manager commitments, with a follow-up date within six weeks: that combination produces more behaviour change than any amount of review documentation alone.
%20(1).jpg)
%20(2).jpg)
%20(1).jpg)
