Coordinated Existential Risk Management
Preserve expertise, centralize coordination, and build fallbacks before crises hit
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 90%
This model treats catastrophic risk as an organizational-management problem rather than an ideological dispute. Leaders begin by identifying threats that could cause widespread or irreversible damage, then preserve the knowledge accumulated by outgoing operators and subject-matter experts. Because crises cross departmental boundaries, one accountable coordinator must reconcile competing agencies, test their claims, and direct a unified response. The system also assumes fallibility: a test, supplier, forecast, or agency may fail, so leaders establish alternative paths before they are needed. Readiness is judged through evidence, exercises, and comparison with competent peers rather than confidence or loyalty. The output is an institution that can detect emerging danger, coordinate action quickly, and adapt when its first response proves inadequate.
Origin
Extracted from Masters in Business during Michael Lewis's discussion of The Fifth Risk and the management failures that weakened the United States pandemic response.
Core principles
- 01Treat low-probability catastrophic threats as management responsibilities
- 02Transfer operational knowledge before leadership changes
- 03Give one accountable leader authority to coordinate the response
- 04Assume critical systems and experts can fail
- 05Preserve nonpartisan expertise across administrations
How to run it
- 1
Map existential risks
List threats capable of causing severe, widespread, or irreversible harm. Identify which teams currently monitor and manage each threat.
Pro tip Include neglected operational risks, not only threats that already receive executive attention.
Watch out Do not confuse low probability with low importance.
- 2
Transfer institutional knowledge
Require outgoing experts to brief incoming leaders on systems, past incidents, unresolved vulnerabilities, and lessons learned. Record ownership and open questions.
Pro tip Begin the transfer before authority formally changes hands.
Watch out Documents alone may omit tacit knowledge held by experienced operators.
- 3
Install central coordination
Appoint one accountable leader to coordinate every participating unit and resolve conflicting priorities. Give that person access to decision-makers and operational evidence.
Pro tip Use a shared operating picture so teams act from the same facts.
Watch out Distributed responsibility without central authority can produce competition and delay.
- 4
Build in fallibility
Demand proof that critical capabilities work and prepare alternatives if they do not. Exercise those fallback paths under realistic conditions.
Pro tip Ask teams to demonstrate readiness rather than merely report it.
Watch out A single untested test, supplier, or communications channel creates a hidden point of failure.
- 5
Benchmark and improve
Compare outcomes and readiness with competent peer organizations. Convert every exercise and incident into explicit improvements.
Pro tip Study near misses as closely as visible failures.
Watch out Partisan framing can prevent organizations from learning operational lessons.
In the wild
An incoming administration receives structured briefings on testing, stockpiles, agency responsibilities, and lessons from earlier outbreaks. It retains a White House coordinator, verifies the national testing pathway, and prepares university and commercial laboratories as backups.
→ The government detects failures earlier and coordinates a faster national response.
Before a new chief risk officer takes over, the outgoing team documents liquidity threats, model weaknesses, emergency counterparties, and regulatory contacts. The new leader runs a simulation in which the primary pricing system and one funding source fail simultaneously.
→ The institution exposes gaps while corrective action is still inexpensive.
Common mistakes
Skipping the handover
New leaders discard accumulated knowledge and must rediscover vulnerabilities during the crisis itself.
Fragmenting command
Multiple teams pursue competing responses because nobody has authority to coordinate the whole enterprise.
Trusting the primary system
Leaders accept assurances without testing capabilities or preparing alternatives.
Is it for you?
Best for
It is best for governments and complex organizations responsible for high-impact risks spanning multiple teams.
Not ideal for
It is not ideal for small, reversible decisions that one empowered operator can manage independently.
From the transcript
“there's meant to be a transition where which is an exchange of knowledge and expertise”
“it is absolutely critical that there be someone in the White House who is coordinating the entire federal response”
From the episode
Michael Lewis on the Power of Intelligent Leadership (Podcast)