Skip to content
Playbook
IntermediateManagerHREngManager

Bonus 12 — Crisis Leadership — Calm Is a Skill

Bonus 12: every manager will face production incidents, surprise resignations, customer escalations, team conflict, and missed deadlines.

11 min read
On this page
60-Second Summary
  • Bonus module 12 of the program (Critical Skills extension). Theme: How you lead the 1% of moments your team remembers forever.
  • Personal crisis playbook (one page per archetype) — the ritual you install.
  • Same rhythm as weeks 1–12: pre-read, cohort live, ritual, falsifiable homework.
  • Closes a high-priority gap most new-manager programs ignore.

Your team will remember 1% of your meetings and 100% of how you behaved in the crises. Crisis leadership is a learnable skill: pause before reacting, separate facts from interpretations, name what you know and don't know, and run the post-mortem that prevents the next one. This module installs the muscle.

What the evidence says

  • Heifetz & Linsky (adaptive leadership): the leader's first move in crisis is to 'get on the balcony' — separate from the heat to see the pattern.
  • Etsy, Google SRE, Atlassian: blameless post-mortems are now the industry standard because blame-based ones suppress reporting and re-cause incidents.
  • Klein (Sources of Power): expert crisis responders share one trait — they pattern-match to past incidents in seconds; the way to install this in new managers is rehearsal of common scenarios.

Pre-read (60 minutes)

  • Read: the four crisis archetypes a manager faces — operational (incident), personnel (resignation/conflict), customer (escalation), commitment (missed deadline) — and the first three moves for each (25 min).
  • Read: the blameless post-mortem template and what 'blameless' actually means in practice (15 min).
  • Read: how to communicate in a crisis — the 4 C's (Calm, Candid, Concrete, Cadenced) (10 min).
  • Reflect (10 min): the last crisis you were in. What was your first reaction? What was the gap between your reaction and the right move?

Live session (90 minutes)

Cohort flow with a senior coach
  1. 1
    Crisis scenario rotation (30 min)
    Cohort splits; each group is handed a live scenario (P0 outage / star engineer resigning at 5pm Friday / major customer threatening to leave / VP says 'this deadline is now half the time'). 10 minutes to draft the first 60 minutes of response. Coach pressure-tests every plan.
  2. 2
    The pause practice (10 min)
    Coach demonstrates the literal 90-second pause before responding to bad news — and the script for buying it ('let me think for 5 minutes and come back to you with a plan').
  3. 3
    Comms drill (20 min)
    Pairs practice the 5-minute crisis comm: what we know, what we don't, what we're doing now, when the next update is. Coach edits ruthlessly — most managers over-explain and under-commit.
  4. 4
    Blameless post-mortem walkthrough (20 min)
    Coach runs a sample post-mortem on a fictional outage: timeline, contributing factors, action items, owners, dates. Cohort sees how blameless ≠ accountability-free.
  5. 5
    Wrap (10 min)
    Each manager commits to: writing their own crisis playbook (1 page per archetype) within 30 days.

The ritual you install

Personal crisis playbook (one page per archetype)

Write a 1-page playbook for each of the four archetypes: who I call first, what I say in the first 60 minutes, what I commit to publicly, how I run the debrief. Store it where you can find it at 11pm on a Friday. Update it after every crisis you handle. Within two years you'll have a personal operating manual that's worth more than any management book.

Modern tools for this skill

CategoryExamples (2026)Use
Incident managementPagerDuty, Incident.io, FireHydrant, Rootly, StatuspageOperational crisis tooling — adopt your eng team's stack
Post-mortemsHowie (CCSP), Etsy template, Google SRE workbook, Notion templateBlameless format, action items, owner, due date
CommsStatus page templates, internal Slack channel conventions, customer letter templatesReduce the activation energy when minutes count
Crisis kitsOn-call runbook, escalation matrix, executive notification thresholdsPre-write the rules of engagement before you need them
Copy-paste AI prompt

I'm in a crisis: [type of crisis, what's happened, who's affected, what's been done so far, who's asking for an update]. Help me: (1) draft a 5-minute holding comm using the 4 C's, (2) name the next 3 moves in priority order, (3) identify who I should escalate to and what I should say, (4) draft the blameless post-mortem template I'll use afterwards.

Homework — falsifiable artefacts

  • Personal crisis playbook drafted for at least 2 of the 4 archetypes.
  • Most recent incident or escalation post-mortem reviewed against the blameless template — gaps named.
  • Escalation matrix drafted: at what threshold do I notify my manager, skip-level, exec sponsor, customer?
  • Crisis comms templates saved where you can find them under stress.

Success signal

By end of this module, you can write a credible 5-minute holding comm in your head, your team has seen you pause before reacting at least once, and your last incident produced a blameless post-mortem with named owners and dates rather than a finger-pointed Slack thread.

Reviewer notes

HR Director (15+ yrs)

I have hired and fired more managers than I can count and the differentiator at the senior level is almost always crisis behaviour. Smart, kind, capable managers crumble under heat that calmer, less brilliant managers absorb. The good news: this is trainable.

Line Manager (20+ yrs)

The 90-second pause is the single most important thing I've ever learned. Almost every regret I have as a manager came from speaking in the first 30 seconds after bad news.

OB / HR Professor (25+ yrs)

The crisis-leadership literature (Boin, James, Useem) converges on one finding: technical preparedness matters less than psychological preparedness. The leader who has rehearsed will out-perform the leader who is more talented but improvising.

Written by Pawan Joshi.Sources cited inline.
First published 30 Jun 2026See site changelog →