Cross-Box Crisis Planning
Break institutional silos and command the whole response from the top
- Difficulty
- Expert
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 95%
Cross-Box Crisis Planning begins by recognizing that no single department sees or controls an organization-wide threat. Leaders map the affected units, assemble practitioners who hold complementary pieces of the problem, and place coordination at a central command point with enough authority to resolve conflicts. Specialists retain responsibility for their domains, but information, assumptions, and decisions move across institutional boundaries. The plan records not only actions but the reasoning that produced them, allowing successors to understand rather than rediscover it. Ownership is deliberately shared so entrenched institutions will adopt the result. Finally, records, relationships, and experienced personnel are preserved across leadership transitions, preventing each new administration or executive team from erasing hard-won organizational memory.
Origin
Extracted from Masters in Business through Michael Lewis's description of the cross-agency pandemic-planning effort initiated under George W. Bush.
Core principles
- 01Complex crises cross organizational boundaries
- 02Operational expertise is often distributed across silos
- 03Central command must coordinate rather than replace specialists
- 04Institutional memory must survive leadership transitions
How to run it
- 1
Map the Boxes
Identify every department, agency, jurisdiction, and specialist group involved in preventing or responding to the threat. Record what each controls and what information each sees.
Pro tip Include frontline practitioners, not only senior institutional representatives.
Watch out An organizational chart rarely reveals where the most useful operational expertise actually resides.
- 2
Assemble the Cross-Box Team
Bring together people whose combined knowledge covers the whole threat. Select for practical insight and intellectual flexibility rather than institutional prestige alone.
Pro tip Look for overlooked experts in adjacent units who have confronted analogous problems.
Watch out Dominant institutions may defend existing doctrine or turf instead of reconsidering assumptions.
- 3
Establish Central Command
Give one leadership point authority to integrate the response across participating units. Use specialist agencies as components of the response rather than allowing any one component to dictate the whole strategy.
Pro tip Make escalation paths and decision rights explicit before the crisis.
Watch out Decentralized execution without unified command can produce incompatible local responses.
- 4
Build and Test the Plan
Develop the plan collaboratively, challenge received wisdom, and test key assumptions against historical evidence, models, and exercises. Document why each intervention belongs in the plan.
Pro tip Reinvestigate old conclusions when their supporting evidence is weak.
Watch out A playbook without preserved reasoning becomes difficult for successors to trust or adapt.
- 5
Create Adoption and Ownership
Present the plan in a way that lets essential institutions recognize themselves in it and accept responsibility for implementation. Preserve substantive safeguards while accommodating legitimate ownership needs.
Pro tip Allow institutions visible authorship when it increases adoption without corrupting the plan.
Watch out A technically superior plan is useless if the organizations required to execute it reject it.
- 6
Preserve Institutional Memory
Retain records, decision rationales, relationships, and knowledgeable personnel through leadership transitions. Conduct direct handoffs between outgoing and incoming teams.
Pro tip Maintain a permanent nonpartisan continuity group for existential risks.
Watch out Removing both records and experienced leaders forces the next team to relearn critical lessons during an emergency.
In the wild
A White House-led effort brought participants from several federal agencies together to address vaccine production, agricultural risks, social interventions, and other components of pandemic response. The group challenged received wisdom about 1918, developed a plan, and secured CDC adoption so the guidance could spread internationally.
→ Distributed expertise became a coordinated pandemic playbook rather than remaining trapped in separate agencies.
After suspicious network activity appears, a company forms a command group spanning security, legal, operations, communications, finance, and customer support. One incident commander integrates decisions, while each function executes its specialist tasks. The team records assumptions and creates a handoff package for future leaders.
→ The company contains the incident without contradictory actions or losing lessons after personnel changes.
Common mistakes
Leaving Expertise in Silos
A solution held by one unit cannot protect the wider organization when information and authority never cross boundaries.
Confusing One Agency with the System
A specialist institution may be essential while still lacking the perspective or authority to command the entire response.
Erasing the Previous Team
Treating every leadership transition as a clean slate destroys records, relationships, and hard-earned reasoning.
Is it for you?
Best for
It is best for large organizations facing risks that span several departments, agencies, or jurisdictions.
Not ideal for
It is excessive for contained problems that one accountable team can solve independently.
From the transcript
“people in one box might have the solution to a problem that's one or two boxes over, but they never meet”
“you have to do it from the White House.”
“what kind of company like could function if every four years you whacked off the heads of all the managers”
From the episode
Michael Lewis on White House Pandemic Planning (Podcast)