Door 2: SURVIVE 2.3
Crisis Execution Playbook
"We're in active crisis — what do we do right now?"
What you'll get
A day-by-day execution plan with communication templates, resource reallocation targets, decision checkpoints, and recovery metrics that takes you from chaos to stability in 90 days.
When to use this
Deploy the moment you declare a crisis — revenue collapse, product failure, security breach, leadership scandal, or any event threatening organizational survival.
The process
1
Declare and Assemble (Hours 0-6)
Questions to answer
How to do this
Formally declare the crisis. Assemble a 5-7 person crisis team with a designated Crisis Lead who has full authority for the next 30 days. Establish a 2-hour approval workflow for external communications. Begin fact-gathering: what happened, who is affected, what is the worst-case scenario. If you don't have a pre-built crisis team roster (from the Twenty-Four Hour Response infrastructure), you're already behind — designate one now.
What you'll have when done
- Crisis Lead designation with authority scope
- Crisis team roster with contact tree
- Fact summary distinguishing confirmed from unconfirmed
- Worst-case scenario assessment
If the crisis is existential (threatens company survival), proceed to Step 2 with maximum resource reallocation. If contained (threatens a unit or product but not survival), proceed with proportional response.
2
First Public Response and Costly Signal (Hours 6-24)
Questions to answer
How to do this
Issue a first public statement within 12 hours. The biological rule: amplify, don't minimize. Assume worst case, provide maximum transparency, resist the instinct to downplay. Within 24 hours, take one costly action that demonstrates commitment — a recall, executive accountability, direct compensation, or structural change. Words without costly action signal weakness. J&J recalled 31 million bottles of Tylenol within 24 hours; that action rebuilt trust faster than any statement could.
What you'll have when done
- Public statement issued within 12 hours
- One costly action announced or executed within 24 hours
- Internal all-hands communication completed
- Stakeholder-specific messages sent (board, investors, key customers, vendors)
If the crisis requires operational hibernation (market crash, revenue collapse), activate Hibernation Entry in Step 3A. If the crisis requires reputation repair (product failure, scandal, breach), activate Investigation Sprint in Step 3B.
3
Operational Triage (Days 2-14)
Questions to answer
How to do this
Execute metabolic triage. Identify the ONE survival priority — the single thing that, if fixed, extends runway by 6+ months or restores viability. Allocate 80% of all resources (founder time, team bandwidth, cash) to that priority. Everything else stops — not slows, stops. Simultaneously: conduct root cause analysis (Days 2-3), execute quick wins (Days 3-5), draft structural changes roadmap (Days 5-7), issue second public statement with findings (Day 7), and design permanent mechanisms (Days 8-14). Cut asymmetrically: protect core capabilities completely, cut periphery to zero. Proportional cuts across departments are fatal in crisis.
What you'll have when done
- Single survival priority identified and communicated
- Resource reallocation plan (80% to survival priority)
- List of stopped activities with communication to affected teams
- Root cause analysis report
- Quick wins implemented
- Second public statement with transparency on findings
- Structural changes roadmap drafted
If survival priority is clear and resources are reallocated, proceed to Step 4. If the team cannot agree on survival priority, the Crisis Lead decides unilaterally — consensus is a luxury crisis cannot afford.
4
Execute and Communicate (Days 15-30)
Questions to answer
How to do this
Roll out structural changes. Train teams on new processes. Tie leadership compensation to crisis recovery metrics. Issue a third public update with specific evidence — not promises, but photos, screenshots, metrics, testimonials showing progress. Establish ongoing reporting cadence: monthly updates for 6 months, then quarterly. Internally, track daily survival metrics against week 4 milestone. If operating in hibernation mode, verify burn rate has reduced 60-80% and essential employees are retained.
What you'll have when done
- Structural changes implemented and documented
- Third public update with evidence of progress
- Ongoing reporting commitment published
- Monthly burn tracking operational
- Week 4 milestone assessment
If Week 4 metrics show measurable progress on survival priority, continue to Step 5 stabilization. If no progress despite 80% resource allocation, convene crisis team for survival priority reassessment — you may be solving the wrong problem.
5
Stabilize and Build Monitoring (Days 31-90)
Questions to answer
How to do this
Shift from daily crisis cadence to weekly stabilization reviews. Set specific milestones for weeks 8 and 12. Continue 80% resource concentration on survival priority through week 14 if operating in survival sprint mode. Monitor emergence signals: market indicators turning positive, financial runway extending, team morale recovering. Rebuild reserves gradually — don't declare victory at first revenue or first positive signal. Trust rebuilds through consistent action over months, not announcements. At Day 90, conduct full assessment: is the organization stable, recovering, or still in crisis?
What you'll have when done
- Week 8 milestone assessment
- Week 12 milestone assessment
- Emergence signal dashboard showing trend lines
- 90-day full assessment report
- Decision: exit crisis mode / extend crisis mode / pivot strategy
At Day 90: if survival metrics are positive for 3+ consecutive months, begin measured exit from crisis mode. If metrics are improving but not yet sustainable, extend crisis mode 30 days. If no measurable progress after 90 days of concentrated effort, escalate to pivot or shutdown decision (return to Crisis Response Decision framework 2.1).
✓ Framework complete