Verified against ChatGPT · 2026-08-12
Build a succession plan for the one role that would actually hurt if the person left tomorrow
Maps bench strength and readiness gaps for a specific single-point-of-failure role, so succession planning produces a real development plan for named people instead of an abstract org-chart exercise.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Build a succession plan for one specific role that would create real disruption if the current person left with normal notice — not a company-wide succession exercise, just this one role, treated seriously because the risk is real. ROLE AND CURRENT PERSON Head of Infrastructure, currently held by one person for the last 6 years. WHY THIS ROLE IS A SINGLE POINT OF FAILURE He is the only person who fully understands the legacy on-prem-to-cloud hybrid setup that half the product still runs on. INTERNAL CANDIDATES TO CONSIDER Two senior infrastructure engineers, both 2-3 years tenure, neither has managed people or owned architecture decisions independently yet. CURRENT FLIGHT RISK SIGNAL, IF ANY He mentioned in his last 1:1 that he's been approached by a recruiter and is 'thinking about what's next' in general terms. For each internal candidate given, assess readiness against the role's actual requirements on a realistic timeline (ready now, ready in 12 months with specific development, ready in 24+ months or unlikely) — do not default every candidate to a hopeful "could grow into it" without naming the specific gap and what closing it would require. If no internal candidate is genuinely close, say so plainly rather than stretching a weak internal case to avoid recommending an external search, since a succession plan that pretends readiness exists when it doesn't leaves the organization exposed at the exact moment it matters. For the single most viable candidate, write a concrete 12-month development plan tied to the specific gap identified, not a generic "more leadership exposure" recommendation — name the actual project, stretch assignment, or exposure opportunity that would close that specific gap. Separately, address the interim coverage question directly: if the current person left with only standard notice today, name who would cover the most critical parts of the role in the gap, even if that coverage is partial or comes with an explicit tradeoff (something else that would have to slip). If a flight-risk signal was given, treat the timeline in this plan as more urgent accordingly, and say so explicitly rather than treating this as a routine, unhurried planning exercise. OUTPUT FORMAT 1. Readiness assessment per candidate (ready now / 12 months / 24+ months or unlikely), with the specific gap named for each. 2. If no strong internal candidate exists, a plain statement recommending an external search be started in parallel. 3. A 12-month development plan for the most viable candidate. 4. An interim coverage plan for a sudden departure, naming who covers what and what tradeoff that creates.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Succession plans routinely fail as an exercise because the default output for this kind of request is a comforting fiction — every internal candidate gets marked as having growth potential regardless of the actual gap, since a model asked to assess readiness will lean toward optimistic, encouraging framing unless explicitly told that overstating readiness is itself the failure mode being guarded against here. Requiring a named, specific gap for every readiness tier, rather than accepting a vague "could grow into it," forces GPT-5.1 to actually reason about what's missing between the candidate's current scope and the role's requirements instead of pattern-matching to generic development language, which is the difference between a plan that produces an actual 12-month assignment and one that produces a sentence nobody can act on. The instruction to say plainly when no internal candidate is genuinely close addresses a specific organizational bias this exercise is prone to: succession planning is often run to demonstrate internal bench depth exists, which creates pressure, even unstated, to find a plausible internal story rather than admit the org needs to look outside — an AI drafting tool has no stake in that internal political pressure, so it's well positioned to state the honest assessment if explicitly instructed to prioritize accuracy over a reassuring narrative. The interim-coverage section exists because a succession plan focused only on the 12-24 month horizon leaves the actually dangerous window uncovered — the two-week-notice gap — and asking for that explicitly, including the tradeoff the interim coverage creates, prevents the plan from looking complete while leaving the highest-probability near-term risk unaddressed. Treating a stated flight-risk signal as urgency-shifting rather than just background color matters because a model given ambiguous risk information will often average it into a moderate, business-as-usual tone unless told directly that the mentioned signal should change the plan's pacing.
What you get back
Candidate A: ready in 12 months with specific development — has strong technical depth but has never owned an architecture decision independently; needs to lead one significant infra project end-to-end with formal ownership, not just execution. Candidate B: 24+ months or unlikely without a role change — strong IC but has shown no interest in the people-management half of this role in two prior conversations. No candidate is ready now; given the recruiter contact mentioned, recommend starting a quiet external search in parallel rather than waiting the full 12 months. Interim coverage: Candidate A could cover architecture decisions with the current person's remote availability for urgent escalations only, which would slow the pending database migration by roughly one quarter.
Verified against
ChatGPT GPT-5.1 · 2026-08-12
Changelog
- 2026-08-12 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
