N13-7: Crisis Leadership for Technical Executives
Leading through outages, layoffs, security breaches, and other engineering crises with economic precision.
🎯 What You'll Learn
- ✓ Lead incident response economically
- ✓ Communicate during crisis
- ✓ Make rapid resource allocation decisions
- ✓ Recover organizational trust
Lesson 1: Incident Response Economics
Every production incident has a cost-per-minute: lost transactions, customer churn risk, SLA penalty exposure, and engineer opportunity cost. For a $100M ARR product, a full outage costs ~$190/minute in direct revenue alone. Decision speed in the first 15 minutes determines whether you lose $3K or $300K.
ARR / 525,600 minutes/year = revenue cost per minute of downtime.
Most incidents either resolve in 15 minutes or escalate to multi-hour events.
Escalating early has a small cost (executive attention). Not escalating has a massive cost (extended outage).
Calculate cost-per-minute for your primary product. Design the 15-minute rapid response protocol.
Lesson 2: Crisis Communication for Executives
During a crisis, the CTO communicates to three audiences: (1) The engineering team — "here's what we know, here's what we're doing, here's how you can help," (2) The executive team — "here's the business impact and our ETA to resolution," (3) Customers — "here's what happened, here's what we're doing, here's how to reach us."
Frequent, honest updates every 30 minutes. Don't hide uncertainty.
Business impact in dollars, ETA ranges (not false precision), and resource needs.
External status page updates within 30 minutes. Empathy + transparency + action.
Draft crisis communication templates for all 3 audiences. Practice delivering the executive update in under 2 minutes.
Lesson 3: Post-Crisis Trust Recovery
After a crisis, trust is damaged with three groups: customers (will the product be reliable?), executives (is the engineering team competent?), and your own team (did leadership handle this well?). Recovery requires: a transparent post-mortem published within 7 days, concrete actions with deadlines, and visible follow-through.
A public or internal document detailing: what happened, why, and what changes.
Every post-mortem item gets an owner and a deadline.
Report on post-mortem action item completion 30 days later.
Design a post-crisis trust recovery plan: post-mortem timeline, action item framework, and 30-day follow-up process.
Continue Learning: Track 13 — Engineering-to-Executive
2 more lessons with actionable playbooks, executive dashboards, and engineering architecture.
Unlock Execution Fidelity.
You've seen the theory. The Vault contains the exact board-ready financial models, autonomous AI orchestration codes, and executive action playbooks that drive 8-figure valuation impacts.
Executive Dashboards
Generate deterministic, board-ready financial artifacts to justify CAPEX workflows immediately to your CFO.
Defensible Economics
Replace heuristic guesswork with hard mathematical frameworks for build-vs-buy and SLA penalty negotiations.
3-Step Playbooks
Actionable remediation templates attached to every module to neutralize friction and drive instant deployment velocity.
Engineering Intelligence Awaiting Extraction
No generic advice. No filler. Just uncompromising architectural truths and unit economic calculators.
Vault Terminal Locked
Awaiting authorization clearance. Unlock the module to decrypt architectural playbooks, P&L models, and deterministic diagnostic utilities.
Module Syllabus
Lesson 1: Lesson 1: Incident Response Economics
Every production incident has a cost-per-minute: lost transactions, customer churn risk, SLA penalty exposure, and engineer opportunity cost. For a $100M ARR product, a full outage costs ~$190/minute in direct revenue alone. Decision speed in the first 15 minutes determines whether you lose $3K or $300K.
Lesson 2: Lesson 2: Crisis Communication for Executives
During a crisis, the CTO communicates to three audiences: (1) The engineering team — "here's what we know, here's what we're doing, here's how you can help," (2) The executive team — "here's the business impact and our ETA to resolution," (3) Customers — "here's what happened, here's what we're doing, here's how to reach us."
Lesson 3: Lesson 3: Post-Crisis Trust Recovery
After a crisis, trust is damaged with three groups: customers (will the product be reliable?), executives (is the engineering team competent?), and your own team (did leadership handle this well?). Recovery requires: a transparent post-mortem published within 7 days, concrete actions with deadlines, and visible follow-through.