Distributed Decapitation Resilience
Distribute authority and resources so one lost leader cannot stop the system
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 95%
Professor Steve describes Iran's military as divided across 31 provinces after its leaders studied earlier attacks that removed a country's leadership and left its forces disorganized. In his account, each unit has local resources, missiles, production systems, and a fallback arrangement, so an attacker would have to disable many units rather than one command center. Generalized beyond the military claim, the mechanism is distributed continuity: map the functions whose loss would stop the system, create independently viable operating cells, give each cell clear authority and essential resources, and establish succession paths before a crisis. The resulting organization may be harder to coordinate in normal times, but it is less likely to collapse when a leader, facility, network, or supplier disappears.
Origin
Extracted from The Diary of a CEO
Core principles
- 01A system should survive the loss of its central leader
- 02Local units need authority as well as responsibility
- 03Resources and production capacity should not sit at one point of failure
- 04Fallback arrangements must exist before disruption begins
How to run it
- 1
Map the decapitation risks
List the leaders, systems, facilities, and suppliers whose loss would halt the whole operation. Separate genuine single points of failure from merely important roles.
Pro tip Trace what stops within the first hour, day, and week after each loss.
Watch out Do not treat every dependency as equally critical.
- 2
Create viable operating cells
Divide the system into units that can continue a minimum mission independently. Define the boundary, purpose, and minimum output of each unit.
Pro tip Use geography, customer group, or operating function where it creates a natural boundary.
Watch out Nominal decentralization fails if every decision still requires headquarters.
- 3
Delegate real authority
Specify which decisions each cell can make when central command is unavailable. Give local leaders clear triggers for switching into continuity mode.
Pro tip Write decision rights as actions, thresholds, and limits rather than vague empowerment.
Watch out Unbounded autonomy can create conflicting or unsafe responses.
- 4
Distribute critical capacity
Place the data, tools, inventory, skills, and communication methods needed for minimum operation inside or within reach of each cell. Avoid duplicating nonessential capacity.
Pro tip Prioritize resources with long replacement times.
Watch out A local team without resources is not an independent unit.
- 5
Build succession paths
Name fallback owners for each critical role and define how authority transfers. Ensure successors can access the information and systems they need.
Pro tip Use at least one successor outside the same failure domain.
- 6
Run a loss-of-command exercise
Temporarily remove a leader, system, or facility from a simulation and observe whether the cells maintain minimum output. Repair the dependencies the exercise reveals.
Pro tip Test communications failure as well as leadership absence.
Watch out A paper plan is not evidence that continuity works.
In the wild
Professor Steve says Iran divided its military into 31 provincial units after observing earlier decapitation attacks. He claims the units have their own resources, weapons, production systems, and fallback arrangements, making the whole force harder to disable by removing national leaders.
→ In his account, an attacker must neutralize many semi-independent units instead of expecting one leadership strike to collapse the system.
A national service business gives each regional team access to customer records, emergency funds, supplier contacts, and an approved continuity lead. When headquarters loses connectivity, regions can still deliver the minimum service within defined limits.
→ A central outage degrades coordination without stopping every region.
Common mistakes
Delegating responsibility without authority
A local unit cannot preserve continuity if it must wait for unavailable central approval.
Copying every resource everywhere
Resilience requires enough local capacity for the minimum mission, not wasteful duplication of everything.
Skipping disruption exercises
Untested succession and access arrangements often fail when the designated fallback actually needs them.
Is it for you?
Best for
It is best for geographically distributed or mission-critical organizations that must continue through severe disruption.
Not ideal for
It is not ideal where duplicated resources would cost more than the disruption risk justifies or where local autonomy would create unacceptable safety failures.
From the transcript
“They have broken their military into 31 divisions.”
“They've got their own fail safe system running in the background.”
From the episode
Financial Crash Expert: In 3 months We’ll Enter A Famine! If Iran Doesn’t Surrender It's The End!