The word gets applied to anything urgent and unwelcome, which makes it useless for the purpose it should serve, which is telling a leader which set of behaviours to reach for.
Three situations are routinely conflated, and each requires a different response. Applying the wrong one is expensive in both directions.
The three
A problem is difficult. It requires work, judgment, and possibly money. Ordinary processes handle it. Most of what a leader deals with is this, and the defining feature is that the organization’s continued functioning is not in question.
An emergency is urgent. Something must be done now, and what to do is generally known. A burst line, an injury, a system failure. Emergencies are demanding and they are not confusing; the response is usually procedural and somebody has trained for it.
A crisis threatens the organization’s ability to continue functioning in something like its current form. It is characterised less by speed than by uncertainty: the situation is not fully understood, the standard responses do not obviously apply, and the decisions being taken will still matter in five years.
An emergency can be handled by a competent duty manager. A crisis cannot, and the distinction is about who must be involved rather than about how loud the situation is.
Both errors are costly
Treating a problem as a crisis is the more common failure and the more corrosive one. It consumes the leadership team on something the organization could have absorbed, it teaches people that ordinary difficulty triggers extraordinary response, and it exhausts the capacity that will be needed later. An organization that has been in crisis mode four times this year has no way to signal the fifth time, when it is real.
Treating a crisis as a problem is rarer and worse. The matter is delegated to somebody competent, handled through normal channels, and reported upward in the ordinary reporting cycle. By the time anybody at the top engages, the window in which the situation could have been shaped has closed. This is how most serious institutional failures actually unfold: not through anybody deciding wrongly, but through nobody deciding that a decision was required.
The test
Three questions, and two affirmatives make it a crisis.
Could this end the organization, or permanently change what it is able to do? Is the situation genuinely not understood, as distinct from being unpleasant? And will decisions taken in the next few days constrain the organization for years?
Note what is not on that list. Whether it is stressful, whether it is public, and whether people are upset. Those describe how a situation feels rather than what it threatens, and organizations that classify by feeling reliably misclassify.
Naming it is itself a decision
Declaring a crisis has consequences: it reallocates attention, it changes who decides what, and it signals something to everybody watching. That makes declaration a political act inside most organizations, and it means the declaration frequently does not happen.
The person best positioned to see it early is usually somebody at operating level who has no authority to declare anything and considerable incentive not to be the one who panicked. Above them, each layer has reason to contain rather than escalate.
Which is why the authority to declare should be settled in advance and held low. An organization where a site supervisor can say the word and trigger a defined response has a chance of engaging early. One where only the chief executive can declare will declare late, every time, and the lateness will be attributed to the situation rather than to the arrangement.
What changes when it is one
Four things, and they are the reason the classification matters.
Decision rights move, temporarily and explicitly, usually upward and always to fewer people. Information flow is centralised so that one account of the facts exists. External communication narrows to a named voice. And the ordinary rhythm of the organization is suspended for a defined period rather than indefinitely, because a crisis footing held too long becomes a permanent condition nobody is managing.
Each of these is disruptive, which is precisely why the classification should be reserved for situations that warrant them.
What this chapter covers
The subchapters that follow treat the sequence in order. Understanding, which is the taxonomy and the types. Preparation, which is what can usefully be arranged in advance and what cannot. Response, which is the first hours and the sustained middle. Aftermath, which is where institutional learning is available for a narrow window and usually squandered.
Then change, which is the other half of this subject: why deliberate change fails so reliably, how it is sequenced when it works, and what to do about an organization in decline that has not yet admitted it.
The two halves belong together because they are frequently the same situation. Most serious organizational change is undertaken because something has gone wrong, and most crises end in a change programme that either holds or reverts.
Edited by Patrick J. Wolf, PhD