Leadership Challenge

If your best leader left tomorrow, what breaks?

Succession is treated as a name on a slide — a designated heir — when it is really a question of distributed capability. The risk isn't that you lack a candidate; it's that critical judgement, relationships and context live in individuals rather than in the system. When capability is installed as infrastructure, succession stops being a single point of failure and becomes a continuity property of the organisation.

Meet the adversary

Key-Person Risk

Key-Person Risk concentrates the organisation's continuity in a handful of individuals, so a single resignation, illness or burnout can stall a function for months. The cost is paid in fragility: the better someone is, the more the business quietly depends on them being there.

What the research shows

A large share of organisations report they are not ready to fill critical leadership roles from within, and most have no robust pipeline beyond the immediate successor — leaving continuity exposed to a single departure.

Ask yourself

For each of your most critical roles, could two people step in capably — or just one, or none?

The reframe

Succession is not a name on a slide — it is distributed capability, where critical judgement, relationships and context live in the system rather than in one person's head. You don't program a single heir; you install the structures — documented decision standards, shared context, deliberate bench-building — that make continuity a property of the organisation.

Why naming a successor is not a plan

Designating an heir feels like progress, but it only relocates the single point of failure. If the successor leaves, or the original incumbent goes before any real transfer happens, the exposure is unchanged — because nothing about how capability is held has actually changed. A name addresses the org chart; it does not address where the judgement lives.

Building continuity into the system

Resilient succession comes from deliberately distributing what currently sits in individuals: writing down the decisions and standards a role carries, widening the relationships so they aren't single-threaded, and giving more than one person live reps at the consequential calls. When capability is installed this way, a departure becomes a transition rather than a crisis — the organisation keeps running because the structure, not the person, was holding it.

Free · 10 Minutes

See where this shows up in your organisation

Install capability as infrastructure. Start with a clear picture, take Stuart's AI-powered Leadership Capability Diagnostic.

Take the free diagnostic

Proof

Leaders who've moved past this

Real client outcomes, attributed by role and sector (names withheld).

Strongest succession bench

"Two years in, our succession bench and decision rights are the strongest they've ever been."

C

Chief Executive

Energy & utilities · UAE

Succession became a plan

"Succession was the elephant in the room. He made it a plan, not a worry."

C

CEO

Family-owned distribution · India

Capability that outlasts

"A multi-year partnership that rebuilt how our entire leadership layer operates. The capability outlasted my tenure."

C

CEO

Enterprise telecommunications · Australia

Board-ready clarity

"Evidence-based and board-ready. He challenged our thinking at the top, the operating model is materially clearer."

C

CFO

ASX-listed financial services · UK

A clearer operating model

"He re-architected our leadership operating model from the top. Fewer meetings, faster decisions, clearer ownership."

E

EVP Operations

Industrial manufacturing · Canada

Measurable capability

"He turned a vague 'leadership development' ambition into a measurable, organisation-wide capability."

C

CHRO

Global manufacturer · UK

Proof

What installing capability changed

Real engagements where this exact constraint was removed, the intervention, and what changed.

Fortis Investment Management Australia (FIMAL) → BNP Paribas

Alignment System

Constraint

Under a global corporate transaction, FIMAL's European parent was acquired by BNP Paribas. With $4.3B in local assets under management across individually managed accounts, the APAC restructure carried extremely complex and sensitive strategic and operational stakes, and two earlier attempts to lead the integration had already failed before Stuart was called in.

Intervention

Brought in as the fixer after two prior attempts had stalled, Stuart took over the restructure and led the APAC region integration program end-to-end through the M&A, resolving leadership and operating-structure issues across the newly combined organisation on multiple fronts simultaneously, not the single workstream that had failed twice before.

Outcomes

  • Succeeded where two earlier attempts had failed, the $4.3B AUM APAC integration led through to completion
  • Strategic and operational continuity maintained across multiple fronts through a highly sensitive restructure
  • Individually managed accounts transitioned without disruption to service
  • Earned a lasting reputation inside the organisation as "the Fixer", the person called in when an integration was already failing, not just when it started

International Telco · multi-team

Confidential engagement

Constraint

Change kept living in the PMO instead of the business, this wasn't the first attempt: new processes and systems had already been rolled out more than once without sticking, adoption stalling below 60% each time, with every relaunch meaning the same work redone from scratch.

Intervention

Rather than run a fourth identical rollout, installed a common leadership language and toolset owned by the leaders themselves, not the program office, fixing the ownership problem, the process problem, and the habit problem together.

Outcomes

  • Adoption of new processes and systems rose from 57% to 86% in 6 months, this time, it actually stuck
  • Rework due to poor adoption decreased by 33% within 9 months
  • Stakeholder satisfaction with change delivery improved by 19 points over 12 months

Healthcare scale-up · ~$60M

Confidential engagement

Constraint

Rapid hiring had roughly doubled headcount inside eighteen months, and the culture hadn't kept pace, what got rewarded in practice (speed, individual heroics) quietly contradicted what leadership said mattered (collaboration, sustainable pace). Regretted attrition was climbing fastest in the teams the business could least afford to lose, and exit conversations kept naming the same gap: what was said and what was actually lived didn't match.

Intervention

Activated a cultural reinforcement system rather than another values poster, translated the stated values into specific, observable behaviours, built them directly into how every manager ran recognition and performance conversations, and made the gap between what the organisation said it valued and what it actually rewarded visible and correctable in real time.

Outcomes

  • A culture the team is proud of again, not just words on a wall
  • Regretted attrition in critical teams fell
  • What gets rewarded finally matches what's said

International Bank · global division · 1000+ leaders

Confidential engagement

Constraint

A multi-region digital transformation was already stalling by the time Stuart stepped in, each country ran its own version of the operating model, wide variance in performance, and rising local resistance to change, after an earlier transformation cycle had failed to land.

Intervention

Took over a program that had already burned one cycle and installed a single execution rhythm across every country at once, decision rights, meeting cadence, and accountability loops fixed together rather than one country at a time, coaching local leaders to run it themselves instead of waiting on direction from HQ.

Outcomes

  • 87% of countries implemented the new operating model within ±10% of the planned timeline over 18 months, in the cycle that actually landed
  • Performance variance in core processes across countries reduced by 27% in 12 months
  • Escalated resistance incidents decreased by 38% compared to the previous, unsuccessful transformation cycle

Frequently asked questions