Succession Planning and Key Person Risk Map Builder

Map critical roles, key-person dependencies, successor readiness, and continuity actions for small teams and growing companies.

Prompt Template

You are an organizational design consultant specializing in succession planning for lean companies. Build a practical succession and key-person risk map for:

**Company/team:** [company or team name]
**Company size:** [number of employees]
**Business model:** [SaaS / agency / ecommerce / services / other]
**Critical roles:** [roles or people you are worried about]
**Known dependencies:** [systems, relationships, approvals, expertise]
**Planning horizon:** [3 months / 12 months / 24 months]
**Constraints:** [budget, hiring freeze, founder bottlenecks, geography]

Create:

1. **Critical Role Inventory** — role, owner, business impact, single-point-of-failure score
2. **Key Person Risk Map** — what would break in week 1, month 1, and quarter 1 if each person left
3. **Successor Bench Matrix** — ready now, ready in 6 months, external hire needed
4. **Knowledge Transfer Plan** — documents, shadowing, decision logs, customer/vendor handoffs
5. **Emergency Coverage Plan** — temporary owners, access requirements, escalation paths
6. **Talent Development Actions** — projects and coaching to build successors
7. **90-Day Implementation Roadmap** — prioritized actions with owners

Be realistic for a resource-constrained team. Flag uncomfortable risks clearly instead of hiding them in generic HR language.

Example Output

# Succession and Key Person Risk Map: AtlasOps

Highest-Risk Roles

| Role | Current Owner | Risk | What Breaks First | Coverage |

|---|---|---:|---|---|

| Founder/CEO | Maya | 5/5 | Enterprise renewals, pricing approvals, investor updates | COO can cover operations, not strategic accounts |

| Lead Backend Engineer | Theo | 4/5 | Deployment approvals, billing service incidents | Senior full-stack dev can shadow within 60 days |

| Finance Ops | Lina | 4/5 | Payroll exceptions, vendor payments, cash forecast | Fractional accountant needs access and SOPs |

90-Day Roadmap

1. **Week 1:** Create emergency access checklist for finance, cloud, CRM, and payroll.

2. **Weeks 2-4:** Have Theo record billing-service architecture walkthroughs and incident playbooks.

3. **Month 2:** Assign two enterprise account calls per week to the COO to reduce founder-only context.

4. **Month 3:** Run a one-day absence tabletop exercise for CEO and lead engineer coverage.

Uncomfortable Risk

The CEO is the only person who can confidently negotiate renewals over $100K. This is not a personality issue; it is a revenue continuity risk.

Tips for Best Results

  • 💡Score roles by business impact, not seniority; an operations specialist can be a bigger risk than a VP.
  • 💡Plan for temporary coverage first, then long-term succession.
  • 💡Include access, authority, and customer context in the continuity plan.
  • 💡Run a tabletop exercise to expose hidden dependencies before a real resignation does.