10 · Capstone — Design an Org-Wide Leadership Development Program

Every project in this track has scaled up: a philosophy statement in Level 1, a coaching plan for one person in Level 2, a team development plan in Level 3. This capstone pulls the entire track together into its largest form — a real, implementable leadership development program for an organization, built on the same evidence-based discipline as every plan before it. The test of completion is not an elegant document. It is whether a real organization could hand this to HR and a budget owner and actually run it, and whether it would produce leaders whose teams are measurably better off, not just leaders who attended more training.

1. The brief

Design a full leadership development program for a real or realistic organization (your own, if you have one; a plausible one otherwise). Produce a written program with the eight sections below, drawing explicitly on the frameworks from across all four levels — this capstone should read as the synthesis of the entire track, not a fresh invention.

Program section	Draws on
Diagnostic: the actual gap this program closes	L3 Mod 9, L4 Mod 2
Target population and selection	L4 Mod 3 (succession), L4 Mod 5 (equity)
Curriculum spine	This track's own four-level structure
The embedding mechanism (survives beyond the program)	L4 Mod 2
Sponsorship and mentorship structure	L3 Mod 8
Measurement plan, with a control group or baseline	L3 Mod 9
Budget and resourcing reality	—
Failure conditions, decided in advance	L4 Mod 4

Three hard rules, escalated from the earlier projects' discipline. Diagnose before designing — the program must be built from a real or realistic gap-finding exercise, not from a generic list of leadership competencies. Name what would make you kill the program — a program with no stated failure condition is not a program, it's a permanent fixture nobody will ever have the evidence to end or fix. And show the equity check — who this program will and won't reach by default, and what you did about that gap specifically (Level 4, Module 5).

2. The program template

LEADERSHIP DEVELOPMENT PROGRAM
Organization (real or realistic): ______________  Size: ______

1. DIAGNOSTIC
   The specific gap (not "we need better leaders" — a named,
   evidenced gap): 
   Evidence (signals from L3 Mod 9, not opinion):
   Why a program, not a smaller structural fix (L4 Mod 2)?

2. TARGET POPULATION
   Who, and the selection method:
   Equity check — who would be excluded by the default
   selection method, and the specific fix:

3. CURRICULUM SPINE (map to this track's own four levels)
   Level 1 equivalent (foundational, individual-relationship skills):
   Level 2 equivalent (coaching, conflict, delegation):
   Level 3 equivalent (culture, systems, teams):
   Level 4 equivalent (org-wide, executive, legacy):
   Format per level (cohort, self-paced, coached, applied project):

4. EMBEDDING MECHANISM
   What changes in hiring/promotion/performance systems so
   this survives the program ending (L4 Mod 2):

5. SPONSORSHIP AND MENTORSHIP STRUCTURE (L3 Mod 8)
   Matching method:
   Exit ramp:

6. MEASUREMENT PLAN
   Baseline or control group:
   Signal(s) tracked (hard-to-fake, L3 Mod 9):
   Re-measurement date:

7. BUDGET AND RESOURCING
   Real cost estimate (facilitator time, participant time,
   materials, mentor time):
   What gets deprioritized to fund it:

8. FAILURE CONDITIONS (decided before launch)
   What result, by what date, means this program gets
   redesigned or killed rather than continued as-is:

3. Worked example (condensed — a full submission runs longer)

Organization. Halden Group, a 450-person logistics company. Three consecutive engineering director hires from outside have failed within 18 months; internal promotion to director has a 90% first-year retention rate by contrast. The diagnosis points at a specific gap: strong senior individual contributors are promoted to director with no structured transition support, while external director hires are onboarded with a formal 90-day plan the internal promotions never receive.

1. DIAGNOSTIC
   Gap: internal promotions to director have no structured
     transition, while external hires do — the reverse of what
     the retention data would suggest is needed.
   Evidence: exit interviews of 4 of 6 internal directors who
     left within 2 years cite "wasn't clear what changed about
     the job," a systems-level (L3 Mod 3) signal, not a
     competence one.
   Why a program: this is a repeated pattern across multiple
     people in the same role, not one individual's struggle —
     the L3 Mod 3 test for a structural cause, not a people one.

2. TARGET POPULATION
   Senior ICs identified via the Succession Matrix (L4 Mod 3)
     as "ready in 1-2 years" for a director role.
   Equity check: the current informal identification method
     surfaces mostly people already visible to VPs socially.
     Fix: every senior IC with 3+ years tenure gets a structured
     nomination review, not just VP-initiated nominations.

3. CURRICULUM SPINE
   L1 equivalent: foundational listening/feedback refresher —
     self-paced, 2 weeks, for ICs who've never formally managed.
   L2 equivalent: coaching and delegation — cohort-based, with
     a real coaching plan (L2 capstone) built for an actual
     direct report within the first 90 days in role.
   L3 equivalent: team diagnostic and culture audit, run on
     their own new team in months 3-6, with a mentor reviewing.
   L4 equivalent: only for those who progress toward VP —
     succession and systems thinking, cohort, year two.
   Format: months 1-2 self-paced + cohort sessions, months 3-6
     applied with a named mentor, ongoing mentor relationship
     through year one.

4. EMBEDDING MECHANISM
   Promotion rubric (L4 Mod 2) gets one added, scored line:
     "has a named 90-day transition plan and mentor" — required
     for the promotion to be finalized, not optional afterward.

5. SPONSORSHIP STRUCTURE
   Each new director matched with a director two years senior,
     not their own manager — six structured sessions in the
     first 90 days, explicit exit ramp if the match isn't
     working (L3 Mod 8) at the 6-week check.

6. MEASUREMENT PLAN
   Baseline: current 18-month retention rate for internally
     promoted directors (currently ~70%, below the 90%
     first-year figure once the second year is included).
   Signal: 18-month retention of program cohort vs. the prior
     three years' promoted cohort, plus exit interview theme
     tracking (L3 Mod 9).
   Re-measured: 18 months after each cohort's promotion date.

7. BUDGET
   Facilitator time: ~40 hours/cohort. Mentor time: ~12 hours
     per pairing over 90 days, unpaid but counted against
     mentor's own goals. Deprioritized to fund: one external
     leadership-training vendor contract not renewed.

8. FAILURE CONDITIONS
   If 18-month retention for the first two cohorts doesn't
     improve over the 70% baseline by at least 10 points, the
     program's curriculum gets redesigned, not just extended
     for more cohorts on faith.

4. Rubric — mark your own program

Criterion	Weak	Strong
Diagnostic	Generic "we need better leaders"	A specific, evidenced, structural gap
Equity check	Absent or symbolic	Names who's excluded by default, with a specific fix
Embedding	A program that ends when the budget does	A rubric or system change that survives it
Measurement	Satisfaction surveys only	A hard-to-fake signal against a real baseline
Failure condition	Absent	A specific number, by a specific date, decided before launch

How It Actually Works

Designing an org-wide leadership development program that itself embeds servant leadership requires applying nearly every mechanism this track has covered as one integrated system, and the integration itself is the hard part cognitive-expertise research points to: chunked, pattern-level judgment (as discussed in Level 3's capstone) rather than sequential application of individual techniques. A program that gets the individual pieces right in isolation — good coaching content, a fair promotion rubric, solid crisis communication training — can still fail as a system if the pieces send conflicting reinforcement signals to participants, the same contradiction-of-signals failure identified in the org-wide-culture module, just now designed into a formal curriculum rather than emerging accidentally from disconnected policies.

Why the program has to embed the same three systems (hiring, promotion, performance management) rather than existing as a standalone training track. A training program that teaches servant-leadership skills but isn't reflected in what actually gets rewarded is, mechanically, the value statement problem from Level 4 Module 2 at curriculum scale: training without a matching reinforcement pathway carries no consequence signal, so the actual reward-tracking mechanism people use to infer real priorities will discount it relative to whatever promotion and performance criteria remain unchanged. A capstone-quality program design has to specify how the training content connects to the reinforcement systems that make behavior actually persist after the training session ends.

Why the rubric-based self-review is even more load-bearing at capstone scale. With this many interacting components (curriculum design, hiring and promotion alignment, succession, measurement), the surface area for motivated reasoning to smooth over a genuine gap grows accordingly — a designer can convince themselves a program "covers" psychological safety by including a training module on it, without the rubric forcing the harder external question of whether the program's actual reinforcement systems (not just its stated curriculum) would produce the effect in practice.

Exercise

Build the full program using the template in section 2 for a real or realistic organization, running the diagnostic honestly before you design anything else. Pay particular attention to section 8 — write the actual number and date that would make you kill or redesign this program, not a vague aspiration, before you present it to anyone who might fund it.

Stretch goals

• Pilot one cohort with real people, even informally, before proposing the full program — the gap between a designed curriculum and what a real cohort actually needs is usually large.
• Have someone from the target population review the diagnostic and equity check before you finalize them — the people the program is meant to serve will catch gaps a designer working alone will miss.
• Design the version of this program that survives your own departure (Level 4, Module 8) — name who owns it if you leave next year, not just who runs it while you're there.
• Present the failure conditions to whoever funds the program before launch, out loud, and get their agreement in advance that hitting them means real change — a failure condition nobody agreed to in advance is not one that will actually be honored under pressure.
• Revisit your own Level 1 philosophy statement from the very start of this track, and write one paragraph on what changed in how you'd state it now, having built everything from an individual relationship up to an organization-wide program. That comparison is the real measure of what this track was for.