How to Build a Manager Development Program From Scratch (Without Waiting for “Perfect”)
- Staff Picks

- 3 hours ago
- 3 min read
Darktrace’s tiered blueprint shows how to train managers at scale, measure what matters, and keep the learning alive long after the workshop
Most companies don’t “fail at management” because they don’t care. They fail because growth moves faster than the shared language of leadership.
That’s the problem Sarah Bright (Head of Learning & Development at Darktrace) set out to solve. Darktrace scaled quickly, and like most fast-growing orgs, it promoted strong individual contributors into management before there was a consistent definition of what “good management” looked like.
The result was predictable: every new manager pulled from their personal history. Different role models, different assumptions, different defaults. In other words, a company full of well-meaning leaders… speaking different dialects of “manager.”
Step 1: Prove the need with signals that already exist
Bright didn’t start by pitching a fancy curriculum. She started by pointing at evidence: engagement surveys and direct demand for career clarity and development. When the org can already feel the gap, buy-in becomes less persuasion and more focus.
Step 2: Build a tiered curriculum, not a one-size bootcamp
Darktrace organized manager development into four tiers, each designed for a different moment in the leadership journey.
Manager Essentials: for aspiring managers or people exploring whether leadership is for them (12-week coaching format).
Manager Energize: practical best practices (feedback, coaching, motivation) in an in-person format that works for new managers and “refresher” learners.
Manager Excellence: the core foundation for managers without formal training, built to create shared standards across the business.
Manager Elite: for senior leaders, focused on strategic alignment, systems thinking, and building a leadership network that can steer together.
One deceptively smart design move: at the start of each cohort, participants write what they hope to get out of the program, and the team uses it as a fast “are we still solving the right problems?” check.
Step 3: Teach competencies that actually show up on Tuesdays
The program’s backbone isn’t trendy theory, it’s manager reality: self-awareness, change leadership, motivation, difficult conversations, and coaching.
That mix matters. You want managers who can inspire, but also managers who can run the hard conversations without turning them into a slow-motion car crash.
Step 4: Measure impact with numbers and stories
Darktrace used multiple measurement sources instead of betting everything on a single metric: post-program surveys, engagement survey signals, HRBP conversations, and anecdotal proof.
90% of participants reported feeling more prepared after completing a program.

The meta-lesson: don’t delay the program because measurement isn’t perfect. Start collecting signals early, then improve your measurement as you iterate.
Step 5: Don’t end the program, build the community
Bright’s team treated manager development as ongoing support, not a one-and-done event. So they created a Manager Community with two anchors: ongoing forums (Teams/intranet) and a quarterly “Manager Meetup” that combines exec context, an external mini-masterclass, and peer panels.
This is where programs stop being “training” and start becoming culture.
The core principle: ship the first “very good” version
Bright’s advice is blunt and useful: chase action over perfection, launch what’s solid, then iterate in the real world. That’s how the program snowballs instead of stalling in planning.
A simple starter blueprint you can steal
If you’re building from scratch, here’s the compressed version of the Darktrace playbook:
Define the business need (use survey data + manager pain points).
Choose 4–6 core competencies you’ll teach everywhere.
Pilot in-person and virtual, learn what scales.
Tier the program so different manager levels get what they actually need.
Measure with a mixed dashboard (surveys + engagement + HRBP input + stories).
Build community infrastructure (forums + recurring meetups).
Iterate every cohort, treat feedback as product signals.
.png)













Comments