How do you lead through a major crisis like a breach or outage?

Question

Accepted Answer

In a crisis, the CTO's job is to **provide calm, structure, and decisive coordination**, not to fix it personally. Establish command, communicate honestly, stabilize first, and learn afterward, in that order.

## A crisis framework

```text
DURING THE CRISIS
1. ESTABLISH COMMAND → clear incident commander & roles
2. STABILIZE → contain/mitigate before root-causing
3. COMMUNICATE → honest, frequent updates (internal + external)
4. PROTECT THE TEAM → avoid blame and burnout, rotate people

AFTER
5. BLAMELESS POSTMORTEM → fix systemic causes, not people
6. REBUILD TRUST → show concrete changes
```

The leader's **composure sets the tone**; panic at the top spreads instantly.

## Concrete example

During a security breach, a CTO names an incident commander, focuses the team on containment, gives the board and customers honest hourly updates, brings in outside help, and afterward runs a blameless postmortem that drives concrete control improvements rather than scapegoating.

## Trade-offs and pitfalls

- **Pitfall:** the CTO diving into hands-on fixing and losing the coordinating role.
- **Pitfall:** hiding or downplaying the incident, which destroys trust when truth emerges.
- Speed to communicate can conflict with certainty; share what you know and update often.

## Why it matters

How a leader handles a crisis is remembered far longer than the crisis itself.

Calm, honest, structured leadership can preserve trust and even strengthen it; panic, blame, or cover-ups cause lasting damage.

Crisis leadership is a defining test of a senior technical leader's character and competence.