Skip to content

All best practices

BP-020Grade B28 supporting cases (26 counted), 0 counter-examples

Build succession into the transformation, not after it

The practice

Plan leadership succession inside the transformation, so the operating system and the plan survive the loss or departure of the leader who started it.

Why it works

Many transformations are identified with one leader, which speeds decisions but concentrates risk. When that leader leaves, dies or is removed, a plan without a successor team and an embedded operating system stalls or is quietly abandoned. Building a bench of successors and codifying the management system turns personal authority into institutional practice. Succession that investors can see also protects market confidence. The key-person risk is greatest after an acquisition or a founder-led transformation.

KB synthesis: the mechanism is the knowledgebase's own reasoning, drawn from the member lessons. Factual support is the case claims under evidence.cases and the research under evidence.research (R-refs).

How to apply it

  • Name at least two credible successors for the transformation leader and for each critical role.
  • Codify the management system (reviews, measures, decision rights) so it does not depend on one person.
  • Rotate successors through visible roles in the programme.
  • Disclose succession plans to the board and, where appropriate, investors.

Warning signs

  • Only one person can explain the plan.
  • Successors are external because none were developed.
  • The operating rhythm lapses when the leader is absent.

When it applies

  • Leader-driven turnarounds, founder-led companies and post-acquisition leadership teams.

When it does not

  • Short, bounded programmes that will finish within the leader's expected tenure.

Evidence grade: Grade B

At least 6 counted supporting cases for every 100 cases in the knowledgebase (6 × cases ÷ 100, rounded to the nearest whole number), whose primary regions span at least 4 regions.

Why this grade

Grade B by schema 4.10 route: >=14 counted cases across >=4 primary regions (the case bar is 6 per 100 cases in the knowledgebase, 235 cases). A needs a systematic, peer-reviewed study that tests this practice. None of the research cited in the KB does. 2 supporting case(s) rest only on company-reported claims and are not counted toward the grade.

Where it applies

Transformation type
  • T03 Cost and restructuring
  • T06 Customer and commercial
  • T11 Turnaround
Topic (business problem)
  • Revenue growth has stalled
  • Margins are eroding despite revenue
  • Legacy ERP and fragmented systems block execution
  • Workforce costs and capacity no longer match demand
  • Operations cannot meet demand efficiently
  • Quality, scrap, defects and rework are out of control
Function
  • Supply Chain & Logistics
  • Marketing & Go-to-Market
  • Manufacturing & Production
  • Product, R&D & Innovation
Starting situation
  • Portfolio of initiatives
Industry
  • B2B SaaS and Subscription Software
  • Chemicals and Process Manufacturing
  • Commercial Banking
  • Discrete Manufacturing
  • Engineering, Construction and EPC
  • Grocery and Food Retail
  • Industrial Distribution and Wholesale
  • Logistics, Warehousing and 3PL
  • Other (cross-industry)
  • Physician Groups, Practices and MSOs
  • Restaurants and Quick Service
  • Specialty Retail and Omnichannel Commerce
Region
  • Africa
  • Central and Eastern Europe
  • East Asia
  • Global
  • Latin America
  • Middle East
  • North America
  • Oceania
  • South Asia
  • Southeast Asia
  • Western Europe

Supporting and counter cases

Researched and fact-checked knowledgebase · Knowledgebase built 5 November 2026

Practices, their evidence grades and case summaries are public. Full case studies are available in AXIOM to subscribers and AXIOM Discover participants.