Succession — What an installed architecture returns

The return · 04 of 06

Succession

Judgment transferred, not just titles handed over.

Succession is the transfer of judgment. A title can be granted in a memo; judgment has to be built, observed and verified.

Freedom within a framework: you cannot hand over what was never written down

Most succession plans are org charts with a date on them. They name a person and assume that proximity produced capability. Then the handover happens, the first hard call arrives, and everyone discovers that the outgoing leader's judgment was never externalized — it lived in relationships, instinct and thirty years of pattern recognition.

A framework makes succession an engineering exercise rather than a hope. It names the decisions the role actually owns, the standard each decision must meet, and the evidence a successor must produce to be considered ready. That is not bureaucracy; it is the only fair thing to do to a successor. Ambiguous expectations are how good people are set up to fail in public.

Playbooks carry the judgment itself: worked calls, near-misses, the reasoning behind the standard, the failure modes that only appear once a cycle. Measurement makes readiness observable — decisions made at level, outcomes over time, and the shrinking need for the incumbent to be consulted.

Done properly, the successor is not waiting for a title. They are already running the decisions and building a record. The announcement becomes an administrative event, which is exactly what it should be.

The decisions a role owns and the readiness standard for each.

• — Role charter: decisions owned, decisions shared, decisions escalated
• — Readiness criteria stated as observable evidence, not opinion
• — A three-to-five-year pathway with review gates
• — Named development owner, separate from the incumbent

How judgment is transferred rather than described.

• — Worked decisions and near-misses from the incumbent's record
• — Shadow-then-lead sequence with real accountability, not observation
• — Debrief discipline after every consequential call

Whether readiness is real or asserted.

• — Share of role decisions made by the successor at level
• — Consultation rate with the incumbent, trended down
• — Outcome quality across a full business cycle
• The decisions the role owns
• The readiness standard
• The review gates
• The successor's own style and method
• Which experiences to seek first
• How they build their team

Which decisions has the successor already made alone, and what is the record?

• 01 Write the role charter for the seat being handed over
• 02 Convert readiness from adjectives into observable evidence
• 03 Transfer three real decisions this quarter, with debriefs
• 04 Review at a gate and publish the readiness position honestly

Failure mode: The incumbent stays as an informal court of appeal, so the successor holds the title while the organization keeps routing around them.

• Succession Architecture
• Enterprise Leadership 360
• Leadership 360 Playbook

If succession is the return you need, the work starts with an honest read of the system that would have to produce it.