Succession Planning Dialogue

Template Overview

Organizational resilience depends on identifying and nurturing successors for mission-critical engineering and executive roles. The Leadership Succession Planning template structures talent bench evaluations, identifies single-point-of-failure vulnerabilities, and outlines stretch developmental assignments.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Succession Planning: [Key Leadership Role]"
date: [YYYY-MM-DD]
executive_sponsor: "[[Chief Executive Officer]]"
evaluator: "[[VP Engineering]]"
critical_role: "Head of Systems Architecture"
business_impact: "Tier 1: Core Intellectual Property & System Stability"
tags: [succession-planning, leadership, talent-bench, governance]
---

# Succession Planning — [Key Leadership Role]

## 1. Role Criticality & Vulnerability Assessment
- **Key Responsibilities:** Architecture oversight of local audio capture, neural engine Whisper inference, and local SQLite data storage.
- **Single-Point-of-Failure Risk:** High. The current lead architect possesses concentrated tacit knowledge of ScreenCaptureKit audio driver quirks.
- **Vacancy Impact:** Inability to ship macOS Sequoia compatibility fixes without external consulting.

## 2. Successor Pipeline & Readiness Evaluation
| Candidate Name | Current Title | Readiness Level | Primary Development Gap |
|---|---|---|---|
| **[[Alex Chen]]** | Staff Systems Engineer | **Ready Now (0–3 Months)** | Executive board presentation experience |
| **[[Maya Lin]]** | Senior Systems Engineer | **Ready in 12–18 Months** | Low-level C++ whisper.cpp memory optimization |
| **[[Julian Vance]]** | Staff UI Architect | **Emergency Proxy Only** | CoreAudio driver debugging depth |

## 3. Targeted Stretch Growth Assignments
### Development Plan for [[Alex Chen]]
- Lead next quarter's Architecture Review Board as primary chairperson.
- Co-present enterprise compliance architecture during executive Customer Advisory Board sessions.

### Development Plan for [[Maya Lin]]
- Shadow core audio driver debugging sessions during macOS beta release cycles.
- Author comprehensive internal technical guides on memory ring-buffer mechanics.

## 4. Knowledge Institutionalization Actions
- [ ] Record all core architecture decision histories into local vault ADR documents.
- [ ] Enforce dual-approver review policies on all ScreenCaptureKit entitlement modifications.

## 5. Review Governance Cadence
Succession readiness reassessed every 6 months during executive talent review assemblies.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Succession Planning: Lead Systems Architect"
date: 2026-10-06
executive_sponsor: "[[Robert Sterling]]"
evaluator: "[[Elena Rostova]]"
critical_role: "Lead Systems Architect"
tags: [succession-planning, leadership]
---

# Succession Planning: Lead Systems Architect

## 1. Review Summary
Elena Rostova evaluated readiness profiles for the Systems Architecture leadership seat. Confirmed that Alex Chen has demonstrated ready-now capability, having successfully led the FTS5 search index rebuild architecture.

## 2. Action Items
Elena will transition Architecture Review Board facilitation to Alex Chen starting next month to solidify his organizational leadership presence.

When to Use and When to Avoid

When to Use

• Use during executive talent reviews and organizational succession planning meetings.
• Use to identify single-point-of-failure risks in mission-critical engineering roles.
• Use to design targeted developmental assignments for high-potential emerging leaders.

When to Avoid

• Avoid using for routine weekly 1-on-1 task reviews.
• Avoid using to announce premature or unconfirmed personnel changes to broad teams.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the leadership succession planning audio recording:
1. Extract candidate readiness evaluations (e.g. Ready Now vs 12-18 Months) for each critical role.
2. Outline specific development gaps and agreed stretch assignments for emerging leaders.
3. List knowledge institutionalization actions and review milestones into structured Markdown.

Your data remains securely on your Mac with zero cloud exposure.