Succession Readiness Model
SUCCESSION READINESS MODEL
(A+ Strategic Framework — Core System Anchor)
1. Executive Summary
Every institution depends on people.
Few institutions survive the sudden departure of the wrong person.
This is not a talent problem.
It is a structural vulnerability.
```txt
If one person leaves and the institution degrades,
the institution was never sound.
It was borrowing time from an individual.
```
The Succession Readiness Model measures:
```txt
Who holds irreplaceable knowledge?
What happens if they leave tomorrow?
How fast can the institution recover?
Is there a pipeline of capable successors?
```
The goal is not to replace people.
The goal is to ensure the institution does not depend on any single one of them.
2. Operating Logic
2.1 — Key Person Inventory
The first step is naming the risk.
A Key Person is anyone whose departure would cause:
```txt
Revenue loss exceeding 10%
Operational disruption exceeding 2 weeks
Regulatory non-compliance
Loss of critical relationships
Loss of undocumented institutional knowledge
```
The Key Person Inventory captures:
```txt
NAME — Individual identified
ROLE — Current position
CRITICALITY — HIGH / SEVERE / EXISTENTIAL
KNOWLEDGE_TYPE — Tacit / Documented / Hybrid
BACKUP_STATUS — None / Partial / Full
DEPARTURE_RISK — LOW / MEDIUM / HIGH / IMMINENT
RECOVERY_TIME — Estimated days to restore function after departure
```
Rules:
```txt
Every leadership role must be assessed
Every revenue-critical role must be assessed
Every regulatory-critical role must be assessed
Self-assessment is not accepted; peers and supervisors assess
The inventory is refreshed every 6 months
```
2.2 — Knowledge Audit
Knowledge is the hidden dependency.
Most institutional knowledge exists in three forms:
```txt
DOCUMENTED — Written, accessible, transferable
TACIT — In someone's head, not written down
RELATIONAL — Embedded in personal relationships and trust
```
The Knowledge Audit maps each Key Person's knowledge:
```txt
Step 1 — List all critical functions performed by Key Person
Step 2 — Classify each function: Documented / Tacit / Relational
Step 3 — Assess transferability: Easy / Moderate / Difficult / Impossible
Step 4 — Identify knowledge that exists nowhere else
Step 5 — Flag single-point-of-knowledge failures
```
Single-Point-of-Knowledge (SPOK):
```txt
A SPOK is any piece of institutional knowledge
that exists in only one person.
Every SPOK is a structural vulnerability.
Every SPOK must be resolved.
```
Resolution options:
```txt
Documentation — Write it down in accessible format
Cross-training — Transfer to at least one other person
Systemisation — Embed in process or technology
Redundancy — Ensure multiple holders of same knowledge
```
2.3 — Successor Pipeline
A successor is not a replacement.
A successor is a prepared continuation.
The Successor Pipeline has three tiers:
```txt
TIER 1 — READY NOW
Can assume role within 2 weeks
Has 80%+ of required capability
Has been briefed on critical knowledge
Has relationships with key stakeholders
TIER 2 — READY IN 6 MONTHS
Can assume role with structured development
Has 50–80% of required capability
Needs targeted knowledge transfer
Needs relationship building
TIER 3 — READY IN 12–24 MONTHS
Has potential but requires significant development
Has 30–50% of required capability
Needs formal training programme
Needs mentoring from current holder
```
Pipeline rules:
```txt
Every EXISTENTIAL Key Person must have a TIER 1 successor
Every SEVERE Key Person must have a TIER 2 or above successor
Every HIGH Key Person must have at least a TIER 3 successor
No successor may appear in more than 2 pipelines simultaneously
Pipeline status reported to board quarterly
```
2.4 — Departure Simulation
Theory is insufficient. You must test.
```txt
A Departure Simulation removes a Key Person
from operations for a defined period
and measures institutional impact.
```
Simulation protocol:
```txt
Step 1 — Select Key Person for simulation
Step 2 — Define simulation period (1 week minimum)
Step 3 — Key Person is fully unavailable (no calls, no emails)
Step 4 — Designated successor or backup assumes responsibilities
Step 5 — Track all decisions, delays, failures, escalations
Step 6 — Debrief: What broke? What held? What was never tested?
```
Simulation outcomes:
```txt
RESILIENT — Operations continued with minimal disruption
STRAINED — Operations continued but with visible degradation
FRAGILE — Significant decisions stalled or failed
CRITICAL — Core function ceased or produced errors
```
Every Key Person rated EXISTENTIAL must undergo Departure Simulation annually.
2.5 — Succession Readiness Score
The composite measure:
```txt
SRS = (Key Person Coverage + Knowledge Documentation
+ Pipeline Depth + Simulation Performance) / 4
```
Each component scored 0–100:
```txt
Key Person Coverage — % of Key Persons with assigned successors
Knowledge Documentation — % of SPOK items resolved
Pipeline Depth — % of Key Persons with TIER 1 successors
Simulation Performance — % of simulations rated RESILIENT or STRAINED
```
Interpretation:
```txt
SRS 80–100 — Institution survives any single departure
SRS 60–79 — Institution survives most departures with strain
SRS 40–59 — Institution vulnerable to specific departures
SRS 0–39 — Institution structurally dependent on individuals
```
3. Application Playbook
Step 1 — Conduct Key Person Inventory
Deliverable: Complete register of all Key Persons with criticality ratings.
```txt
Assess all leadership positions
Assess all revenue-generating roles
Assess all regulatory and compliance roles
Assess all technology and infrastructure roles
Peer-validate criticality ratings
Flag all EXISTENTIAL and SEVERE ratings for immediate action
```
Step 2 — Execute Knowledge Audit
Deliverable: Knowledge map for every Key Person rated SEVERE or above.
```txt
Interview each Key Person (structured format)
List all critical functions and classify knowledge type
Identify all Single-Points-of-Knowledge
Prioritise SPOK resolution by criticality and transferability
Create resolution plan with 90-day targets
```
Step 3 — Build Successor Pipeline
Deliverable: Named successors at appropriate tiers for all Key Persons.
```txt
Identify internal candidates per role
Assess current capability against role requirements
Classify into TIER 1 / TIER 2 / TIER 3
Develop individual development plans for TIER 2 and TIER 3
Initiate knowledge transfer for TIER 1 candidates
Validate: No candidate appears in more than 2 pipelines
```
Step 4 — Run Departure Simulations
Deliverable: Simulation report for all EXISTENTIAL Key Persons.
```txt
Schedule simulation windows (1 week each)
Brief successor and team on simulation rules
Execute simulation with full unavailability
Track all operational impacts
Debrief within 48 hours of simulation end
Document findings and remediation actions
```
Step 5 — Calculate Succession Readiness Score
Deliverable: SRS with component breakdown.
```txt
Compute Key Person Coverage percentage
Compute Knowledge Documentation percentage
Compute Pipeline Depth percentage
Compute Simulation Performance percentage
Calculate composite SRS
Present to board with trend data
```
Step 6 — Remediate Gaps
Deliverable: Prioritised remediation plan for all scores below 60.
```txt
Identify lowest-scoring component
Define targeted interventions
Assign owners and deadlines
Track progress monthly
Re-score quarterly
```
Step 7 — Report and Institutionalise
Deliverable: Standing board item for succession readiness.
```txt
SRS reported quarterly to board
Key Person Inventory refreshed every 6 months
Knowledge Audit refreshed annually
Departure Simulations conducted annually for EXISTENTIAL roles
Pipeline reviews integrated into talent management cycle
```
4. Metrics & Measurement
```txt
Succession Readiness Score (SRS) — Composite 0–100
Key Person Count — Total EXISTENTIAL + SEVERE
Key Person Coverage Rate — % with assigned successors
SPOK Count — Total unresolved single-points-of-knowledge
SPOK Resolution Rate — % resolved per quarter
Pipeline Depth Ratio — TIER 1 successors / Key Persons
Simulation Pass Rate — % rated RESILIENT or STRAINED
Knowledge Documentation Rate — % of critical knowledge documented
Departure Risk Concentration — % of Key Persons with HIGH or IMMINENT departure risk
Recovery Time Estimate — Average days to restore function after departure
```
Measurement cadence:
```txt
Monthly — SPOK resolution tracking
Quarterly — SRS calculation and board report
Biannually — Key Person Inventory refresh
Annually — Full Knowledge Audit and Departure Simulations
Event-triggered — Any Key Person resignation or health event
```
5. Board-Level Questions
```txt
What is our current Succession Readiness Score?
How many EXISTENTIAL Key Persons do we have?
How many of them have a TIER 1 successor?
How many Single-Points-of-Knowledge remain unresolved?
When did we last run a Departure Simulation and what did we learn?
If our CEO departed tomorrow, what is the recovery time?
If our CTO departed tomorrow, what systems would be at risk?
Are any Key Persons at IMMINENT departure risk?
Is our SRS improving or declining quarter over quarter?
What is the cost to move our SRS from current level to 80+?
```
6. Failure Modes
```txt
FOUNDER_DEPENDENCY
Cause: Institution built around a single visionary leader
Signal: No decisions made without founder involvement
Fix: Mandatory delegation framework with Departure Simulation
KNOWLEDGE_HOARDING
Cause: Key Persons retain knowledge as job security
Signal: Resistance to documentation or cross-training
Fix: Knowledge sharing embedded in performance evaluation
PAPER_SUCCESSION
Cause: Successors named but never developed or tested
Signal: TIER 1 successor cannot perform in Departure Simulation
Fix: Pipeline validation through live simulation, not paperwork
PIPELINE_CONCENTRATION
Cause: Same person named as successor for multiple Key Persons
Signal: One candidate appears in 3+ pipelines
Fix: Enforce maximum 2-pipeline rule per candidate
SIMULATION_THEATRE
Cause: Key Person remains available by phone during simulation
Signal: No real stress on operations; simulation shows false RESILIENT
Fix: Full unavailability enforced; simulation monitored independently
SUCCESSION_PROCRASTINATION
Cause: Board treats succession as long-term project, never urgent
Signal: SRS below 40 for 3+ quarters with no remediation
Fix: SRS threshold triggers mandatory board intervention
```
7. Case Application
Situation
Technology company. 200 employees.
Founder-CEO. CTO with 15 years of undocumented architectural knowledge.
Head of Sales with all key client relationships.
Problem
```txt
Key Person Inventory: 8 identified (3 EXISTENTIAL)
SPOK count: 23 (11 held by CTO alone)
Successor Pipeline: No TIER 1 successors for any EXISTENTIAL role
Departure Simulations: Never conducted
SRS: 18 (STRUCTURALLY DEPENDENT ON INDIVIDUALS)
```
Intervention
```txt
Phase 1 — Full Key Person Inventory with peer validation
Phase 2 — Knowledge Audit: CTO's 11 SPOKs prioritised for documentation
Phase 3 — Cross-trained 2 senior engineers on critical architecture
Phase 4 — Sales relationships mapped; introduced backup contacts
Phase 5 — Named TIER 1 successor for COO role; TIER 2 for CEO and CTO
Phase 6 — Conducted Departure Simulation for CTO (1 week)
Result: FRAGILE (3 decisions stalled, 1 system issue unresolved)
Phase 7 — Remediated gaps identified in simulation
Phase 8 — Re-ran simulation at 6 months: STRAINED (improved)
```
Outcome
```txt
SRS: 18 → 58 (6 months), 71 (12 months)
SPOK count: 23 → 7
TIER 1 successors: 0 → 2 (of 3 EXISTENTIAL roles)
CTO simulation: FRAGILE → STRAINED → RESILIENT (18 months)
Board confidence: Succession moved from unknown risk to managed risk
Insurance: Key Person insurance repriced favourably
```
8. Canon References
```txt
ND-14 — Institutional Continuity and Knowledge Preservation
Core principle: An institution that dies with its founder was never an institution.
Application: The Succession Readiness Model operationalises ND-14
by measuring and eliminating single-person dependencies.
FD-07 — Foundational Durability and Structural Permanence
Core principle: What is built to last must survive the builder.
Application: The Key Person Inventory and Departure Simulation
directly test FD-07 by removing the builder and measuring what remains.
```
9. Product Integration
```txt
Key Person Dashboard → Executive Reporting
SPOK Resolution Tracker → Knowledge Management Module
Successor Pipeline View → Talent & Governance Module
Departure Simulation Scheduler → Strategy Room
SRS Trend Report → Board Pack (quarterly)
Departure Risk Alerts → Risk Register
Knowledge Audit Workflow → Compliance Engine
Pipeline Gap Analysis → Decision Exposure
```
10. Final Position
People are not the problem.
Dependence on people is the problem.
```txt
Every institution must answer:
Who can we not afford to lose?
What do they know that no one else knows?
Who is ready to step in?
Have we tested it?
```
If the answer to any of these is unknown,
the institution is operating on borrowed time.
The Succession Readiness Model converts
personal dependency into institutional capability.
What depends on one person is fragile.
What is documented, distributed, and tested is durable.
Durability is not optional.
It is the definition of an institution.