Most leadership development plans I see inside MSPs are built for a company that doesn't exist. They copy a generic corporate template, bolt on a training budget, and hope. Then they wonder why nothing changed on the service desk.
Here is my actual position. An MSP doesn't have a leadership problem — it has a scaling problem that shows up as a leadership problem. You hired brilliant engineers. You promoted the best of them. And then you asked people who were rewarded for fixing tickets alone to suddenly lead the people fixing the tickets. That's the whole game. Get that transition right and everything downstream — churn, margin, on-call sanity — gets easier.
So a leadership development plan for an MSP is not a syllabus. It's a system for turning technical excellence into leadership capability without losing the technical excellence. Those are two different skills. Nobody tells your best engineer that on the day you promote them.
I'm Stuart Andrews, The Leadership Capability Architect. I've spent years building these plans for service businesses where the product IS the people and every hour is either billable or a liability. That constraint changes everything about how you develop leaders — you can't pull your best people off the floor for a fortnight and you can't afford a leader who freezes under client pressure. Below is how I'd build one for you — the specific version, not the LinkedIn version.
My Lens: The MSP Leadership Capability Stack
When I build a leadership development plan for an MSP specifically, I work through five layers in order. Skip a layer and the ones above it wobble. This is the lens I apply before I write a single training objective.
- Technical-to-leader transition: Name the exact moment an engineer stops being paid to solve and starts being paid to enable. Most MSP leadership plans never address this — they assume the promotion did the work. It didn't. This is where I start.
- Client-facing judgement: In an MSP the leader IS the service. Escalations, scope fights, the 2am 'is this a P1' call. Develop the judgement to hold a client relationship under pressure, not just the technical answer.
- Delegation without abandonment: MSP leaders either hoard the hard tickets or dump everything and disappear. The capability I build here is handing work over in a way that grows the person receiving it — the single biggest lever on your bench depth.
- Systems thinking over hero-fixing: A great engineer fixes the outage. A leader fixes why the outage class keeps happening. Shift the reward from the heroic save to the boring prevention, and you shift the culture.
- Bench and succession depth: An MSP that depends on three irreplaceable people is fragile, not lean. The top layer is deliberately building leaders below your leaders so growth doesn't break your delivery.
Start by Naming What Leadership Actually Does in an MSP
Before you plan anything, get honest about what leadership does inside your specific business. Not the poster version — the operational one. In an MSP, leadership shows up in four places every single week, and if you can't point to them you're planning in the abstract:
- Effective decision-making under incomplete information — the P1 that might be a P3, the client who wants scope you can't afford to give.
- Employee engagement and retention — in a market where a good engineer can leave on Friday and start elsewhere on Monday, leadership is your best retention tool.
- Client relationships and service delivery — your leaders carry the relationships that keep contracts renewed, not just the SLAs.
- Strategic vision — someone has to decide which capabilities you build next and which clients you're actually built to serve.
Write down who owns each of those in your business today. The gaps in that list are the first draft of your development plan. Not a competency framework you downloaded — the real holes in your real org.
Determine Leadership Development Needs — Specifically, Not Generically
Every MSP has different leadership requirements based on its size, structure and where it's trying to go. A ten-person shop trying to break past founder-dependency needs something completely different from a hundred-person MSP integrating an acquisition. Tailor ruthlessly. Here's how I diagnose the real needs:
- Evaluate leadership skill gaps with evidence, not vibes — Run self-evaluations, performance reviews and honest 360 feedback to find where communication, delegation and strategic thinking actually break down. In an MSP, watch delegation hardest — it's the skill technical promotions destroy.
- Anchor the plan to a real organisational challenge — If client retention is your issue, prioritise leadership capability in client relationship management. If your on-call rota is burning people out, prioritise the delegation and systems-thinking layers. Let the pain choose the priority.
- Define what each leadership role is actually for — A team lead, a service delivery manager and a technical director need different things. Make the responsibilities explicit, then develop against them. Vague roles produce vague leaders.
- Separate the two skill tracks on purpose — Decide, per person, how much technical depth they keep and how much leadership capability they build. Pretending someone can be fully both, forever, is how you burn out your best people.
The MSP-specific trap: promoting your strongest engineer removes your strongest engineer from the bench AND creates an untrained leader. You lose twice unless the development plan is ready on day one of the promotion — not six months after they've already struggled.
Put the Development Strategies Into Practice
Once you know the real needs, build the mechanisms. A plan that lives in a document changes nothing. These are the levers that actually move capability in a service business:
- Coaching and mentoring, weighted toward the transition — Pair newly-promoted engineers with experienced leaders specifically to navigate the shift from solving to enabling. This is the highest-leverage intervention in an MSP and the one most plans underfund.
- Cross-training across the delivery lines — Expose leaders to service desk, projects and account management so they understand the whole delivery machine, not just the tower they came from. Adaptable leaders come from broad exposure.
- Real feedback loops, not annual theatre — Regular, specific feedback keeps development honest. In a fast-moving MSP, a once-a-year review is far too slow to correct a leadership habit before it hardens.
- Emotional intelligence as a delivery skill — Empathy, self-awareness and composure aren't soft extras in an MSP — they're what let a leader hold a furious client and a stretched team in the same hour. Train it deliberately.
- Clear, measurable leadership goals tied to the business — Set goals that connect to retention, delivery quality and margin — not abstract 'be a better leader' aspirations. What you can measure, you can develop.
- Measure results and adjust — Track the plan against real outcomes — engagement, turnover, escalation rates — and change it when the data tells you to. A development plan is a living system, not a launch event.
Continuous education has its place — training, books, conferences, staying current on tooling. But treat it as fuel, not the engine. The engine is the coaching and the feedback that turns learning into changed behaviour on Monday morning.
The Distinction I Want You to Steal
I'd leave you with one line, and I mean it as a working principle, not a slogan: in an MSP, you're not developing leaders — you're de-risking your delivery. Every leader you build is a single point of failure you've removed. That reframe changes what you fund and what you measure.
Because when leadership is treated as a de-risking exercise, you stop asking 'did they enjoy the training' and start asking 'can this person now hold a client, grow a team and survive a bad week without me.' That's the only question that matters in a business where the people are the product.
I've watched MSPs pour money into leadership programmes and see nothing move, and I've watched others change their whole trajectory with a far smaller spend aimed at the transition moment. The difference was never budget. It was whether the plan was built for an MSP's real physics — technical people, client pressure, thin benches — or built for a company that doesn't exist.
So build the specific version. Name the transition, develop the judgement, protect the bench, and measure the risk you've removed. Do that and your MSP doesn't just get better leaders. It gets harder to break. That, to me, is what a leadership development plan is actually for.
What This Looks Like Over Twelve Months
People ask me what the plan looks like on a calendar. Honestly, it starts unglamorous. The first ninety days are diagnostic: you map who leads what, you find the promotion-shaped holes, and you pick one organisational pain — retention, escalations, founder-dependency — to anchor everything to. Resist the urge to launch a big programme in week one. You'll aim it at the wrong target.
The middle stretch is where capability actually gets built, and it's built in the work, not away from it. Coaching cadences on the transition. Cross-exposure across your delivery lines. Feedback that lands in weeks, not once a year. This is the part most MSPs skip because it's slow and it doesn't photograph well for a board slide. It's also the only part that changes behaviour.
By the back third of the year you should be measuring the thing that matters — has your delivery got harder to break. Fewer heroic saves because the systems improved. Escalations handled a level down because you built the judgement there. A bench that could survive losing a key person. If you can't see movement on those, the plan was training, not development, and I'd tear it up and rebuild it around the transition moment.
Frequently Asked Questions
Q1: How long before a leadership development plan shows results in an MSP?
A: Expect six months to a year for measurable shifts in leadership effectiveness, depending on the skills involved and how consistently you run the plan. But you'll usually see earlier movement in team engagement, communication and decision-making — especially if you invest first in the technical-to-leader transition, where the returns come fastest.
Q2: How do I keep leadership development aligned with business goals?
A: Involve senior leadership in the planning and tie every leadership goal to a real business outcome — retention, delivery quality, client satisfaction. Then review progress regularly and adjust as strategy shifts. In an MSP, the tightest alignment is usually to churn and margin.
Q3: How does leadership development relate to emotional intelligence?
A: In a service business, emotional intelligence is a delivery skill. It lets leaders make sound calls under pressure, manage stress and hold relationships with both clients and their own teams. EI training improves conflict resolution, decision-making and engagement — all of which show up directly in an MSP's service quality.
Q4: Can leadership development apply at every level of an MSP?
A: Yes, and it should. Team leads, service delivery managers and aspiring leaders all need it, not just the top team. A multi-tiered approach builds bench depth and a growth culture — which is exactly the fragility fix most MSPs need.
Q5: How do you measure the success of a leadership development plan?
A: Track outcomes, not attendance — team performance, engagement, turnover, escalation rates and progress against business goals. Regular feedback and goal tracking tell you whether capability is actually changing, or whether you've just run some training.
Q6: Can the plan be customised for different types of leaders?
A: Absolutely. Senior leaders need strategic thinking and vision-setting; middle managers need delegation and operational judgement; new team leads need the transition support most of all. Tailor the plan to the level, or you'll over-serve some leaders and abandon others.