Crisis and Critical Incident Fundamentals
Definitions and thresholds
An incident is an unplanned event that can be handled with normal resources and authority. A crisis is a destabilizing event-or series of events-that threatens people, critical operations, reputation, or viability and exceeds routine decision capacity. A disaster usually implies widespread impact requiring external support. These are thresholds, not synonyms; exam questions often hinge on which label applies and therefore which governance path is triggered.
Key concepts: crisis characteristics (high uncertainty, compressed time, high stakes, intense scrutiny), VUCA conditions, the crisis lifecycle (mitigation, preparedness, response, recovery), stakeholder salience, and command versus coordination. Distinguish emergency response (life safety, containment, tactical control) from crisis management (strategic direction, prioritization, external engagement). Crisis leadership requires sense-making, decision logging, and explicit authority delegation.
Traps: assuming every disruption is a crisis (over-activation burns credibility) or waiting for certainty before escalating (under-activation); treating the emergency operations center as the same thing as the crisis management team; confusing the person who commands the scene with the executive who owns the organizational response; and letting a reputational or cyber event sit in an IT queue because no one was hurt.
Rule of thumb - escalation test: escalate when any of three conditions is met: (1) serious harm or potential harm to people; (2) loss of a critical service beyond its maximum tolerable disruption; (3) high uncertainty or public/regulatory scrutiny beyond local authority. If two of the three are unclear, escalate and de-escalate later.
Worked example: A warehouse fire is contained in 40 minutes with no injuries. It is an incident-unless a key customer's sole production line depends on that inventory, making it an enterprise crisis. Impact, not size, drives the label.