Crisis Management Fundamentals
Crisis Management Fundamentals
This domain tests whether you can distinguish a crisis from routine disruption and apply a consistent decision framework when threat, uncertainty, and time pressure coincide. Expect questions on definitions, lifecycle, command roles, and escalation criteria.
Core rules
- A crisis threatens core objectives, reputation, or survival and demands coordinated decisions beyond normal authority. An incident is contained by existing procedures; an emergency is a time-critical event with a known response; a crisis is marked by ambiguity, cascading effects, and strategic stakes.
- The lifecycle runs through anticipation, signal detection, activation, containment, recovery, and learning. Crisis management governs the whole; emergency response and business continuity are complementary capabilities.
- Decision-making under uncertainty uses structured sense-making: establish facts, assumptions, unknowns, and decision deadlines; assign owners; record decisions and triggers for review.
- A single accountable crisis lead with a small decision team outperforms consensus-by-committee. Legal, communications, operations, people, and finance must have seats at the table.
Worked example
A key supplier reports a fire and cannot confirm restart dates. Production is unaffected for five days. Classify: not yet a crisis, but a potential crisis. Activate monitoring and a pre-agreed watch level, set indicators (restart date slips beyond day three, alternate supplier cost exceeds threshold, customer commitments at risk), and draft holding communications. If two indicators trip, escalate to full activation. Reasoning: the trigger is strategic impact and uncertainty, not the fire itself.
Traps
Calling every incident a crisis causes warning fatigue; waiting for certainty causes late response. Do not confuse incident command with crisis governance, assume a single cause, or ignore second-order effects such as supplier contagion and regulatory scrutiny.