A leadership development programme for managers works when it is built backwards from a business problem, delivered mostly on the job, and measured by what managers do differently six months later. Everything else is decoration. A well-designed programme moves people from doing the work to leading others who do it, and it ties that shift to organisational goals such as retention, engagement and execution.
Most organisations know this. Most still book a two-day workshop, hand out certificates, and wonder why nothing changed.
So let’s walk through how to design one that sticks.
What Is a Leadership Development Programme for Managers?
Core Purpose
Think of the best manager you ever had. Now think of the worst. The gap between them was rarely technical skill. It was feedback, judgement, how they handled a bad Monday.
A leadership development programme is a structured, ongoing set of learning experiences that builds those capabilities in people who already manage others. It is not a one-off course. It is not an induction either, and it is not a talent-spotting exercise for the C-suite.
Why bother? Because Gallup’s research suggests managers account for at least 70% of the variance in employee engagement across business units. Your managers are your culture, whether you planned it or not.
Link to Business Strategy
Here is where most programmes quietly die. They begin with a course catalogue instead of a business priority.
If the strategy says “grow into Ghana and Kenya within two years,” then your managers need to handle cross-border teams, complex delegation and escalation. If the strategy is cost control, they need to make tough trade-offs and still keep people motivated. The programme should name the exact behaviours that move the strategy forward. Not “leadership excellence”. Something you can actually observe.
Manager Versus Executive Programmes
Managers and executives are different animals. A frontline supervisor is learning to stop being the best individual contributor. An executive is learning to handle ambiguity, enterprise transformation and stakeholder pressure. Putting them in the same room is like teaching a driving test and a Formula 1 class together.
Why Do Leadership Development Programmes Fail?
Because the training works and the environment doesn’t.
Someone returns from a brilliant workshop, buzzing, ready to give proper feedback. Then their own boss ignores it, the team is under pressure, and old habits win by Wednesday. Call it the great training robbery: motivation gets bought, behaviour change never gets delivered.
There is a supply problem too. The Chartered Management Institute found that 82% of people stepping into management have had no formal training. Accidental managers everywhere. Many Nigerian firms will recognise this: the best sales rep gets promoted on Friday and is leading eight people on Monday.
And misdirection. McKinsey’s capability survey reports only 33% of companies focus training on the capability that adds the most value. Two-thirds are teaching what is comfortable, not what is needed. Frankly, that stings.
How Do You Assess Leadership Needs and Gaps?
Do not guess. Run a discovery phase before you design a single session.
Diagnostic Methods
You have a few honest tools. Pick a mix:
- 360-degree feedback for a view of how managers land with peers and direct reports
- Stakeholder focus groups to surface what senior leaders see coming
- Skills assessments or simulations that test decisions under pressure
- Short pulse surveys of teams about their managers’ day-to-day habits
Stakeholder Input
Talk to the CEO, yes. Also talk to the middle manager in Lagos who is quietly holding three departments together with WhatsApp groups. The two stories rarely match, and the distance between them is your design brief.
Data to Review
Look at turnover by manager, engagement scores, promotion pipelines, exit interview themes, customer complaints, safety records. Numbers betray what interviews politely hide. If one department loses people twice as fast as the others, that is a leadership gap wearing a spreadsheet costume.
Define Target Skills and Programme Goals
Now narrow it. Hard.
Pick a handful of competencies, not twenty. Korn Ferry’s developing leaders overview points to learning agility, self-awareness and authenticity as foundations, which is a fair starting point if your diagnostic does not say otherwise.
Then write goals as behaviour. “Managers hold a fortnightly one-to-one with every direct report and give specific feedback” beats “improve communication” every time. Add a business signal beside it: lower attrition in the pilot cohort, faster project delivery, better engagement. If you cannot say how you would notice success, you have not defined it yet.
Choose Participants and Map Learning Pathways
One-size-fits-all fails because the job changes at each level. Here is a rough map.
| Level | Core shift | Focus areas |
|---|---|---|
| Frontline managers | From doing to leading others | Delegation, feedback, running team routines |
| Mid-level managers | From leading people to leading managers | Cross-functional influence, breaking silos, coaching other managers |
| Senior managers | From function to enterprise | Systems thinking, ambiguity, long-term strategy and stakeholders |
Frontline Managers
They need the mindset shift first. Many still believe their value is output. Teach them that it is now team output, and give them safe room to practise hard conversations.
Mid-Level Managers
The squeezed middle. They translate strategy downward and carry pressure upward. Horizontal influence matters here more than any slide deck, so build cohorts across departments and let them fight over real shared problems.
Senior Managers
Fewer classrooms, more peer challenge and executive coaching. They learn from decisions with real stakes, not case studies about someone else’s company.
Design Content Using the 70-20-10 Learning Model
The 70-20-10 model is a rule of thumb, not a law of physics, but it holds up well in practice. Roughly 70% of development comes from on-the-job work, 20% from coaching and relationships, and 10% from formal training.
So the 70 is stretch assignments: leading a cross-team project, turning around an underperforming unit, presenting to the board. The 20 is mentoring, peer coaching circles and 360 feedback loops. The 10 is workshops, virtual or in person, used to introduce concepts and not to carry the whole load.
Notice what that does to your budget. Most organisations spend almost everything on the 10. Flip your thinking and the programme starts to feel like work, which is exactly the point.
For scale, Harvard Business Impact describes blended formats combining digital platforms with live sessions, which suits distributed teams where flying everyone to one venue is costly.
Secure Senior Leader Sponsorship and Participant Buy-In
No sponsor, no programme. Simple.
Senior leaders must do more than open the launch with a speech. They should sponsor a participant, review project outcomes, and, awkwardly, take part in their own feedback. When the managing director visibly practises the same behaviours, nobody asks whether it is optional.
Participants need a reason too. Korn Ferry’s pain points analysis says 94% of employees would stay longer at a company that invests in their development. Tell managers that. Show them the career path attached. And protect their time, because a programme squeezed into evenings after a full workload becomes resentment with a syllabus.
How Do You Measure Impact and Improve the Programme?
Stop counting completion rates. Someone can finish every module and change nothing.
Track three things instead:
- Behaviour: what managers do differently, seen through repeat 360s and manager observation
- Experience: whether direct reports and peers feel the difference
- Business signal: whether the original gap, say turnover or missed deadlines, is closing
Take a baseline before the programme starts, measure again at three and six months, and compare against a group that has not yet joined. Surveys remain the common method (Harvard Business Impact reports 62% of organisations lean on employee surveys), but pair them with hard numbers.
Then act on what you find. Drop modules nobody applied. Fix the managers’ own bosses if they are undoing the learning. Pilot with one cohort, adjust, then roll out to the wider organisation phase by phase.
FAQ
How long should a leadership development programme for managers run? Six to twelve months is typical. Shorter than that and habits do not form.
How many managers should be in a cohort? Between fifteen and twenty-five keeps discussion honest and coaching manageable.
Can small businesses do this? Yes. Skip the elaborate platform. Use a simple diagnostic, monthly peer circles, one real project each and a senior sponsor.
What is the biggest mistake? Treating training as the programme. It is only the 10%.
How do you scale it? Prove the pilot with data, train internal facilitators, and use blended digital delivery.
Conclusion
Designing this well is not complicated. It is just uncomfortable. You diagnose honestly, pick a few behaviours that matter, push learning into real work, get senior leaders in the ring, and measure what people do rather than what they attend.
Start small. One cohort, one business problem, one sponsor.
Then ask yourself the only question that counts: six months from now, will anyone’s team notice?
