Crisis management is how your organization prepares for, responds to, and recovers from events that threaten its people, its operations, its reputation, or its survival. That is the whole definition. Everything else in this post is about what it means in practice.
Most people asking “what is crisis management?” picture a spokesperson at a podium. That is one small piece of it. Crisis management is a decision-making process. It gets the right people into the right room, fast, to make good decisions with incomplete information, and then makes sure everyone who needs to know hears about those decisions.
Here is the definition, what counts as a crisis, what crisis management is actually for, and the basics every program needs. When you want the deep version, our Ultimate Guide to Crisis Management covers every part of a program in detail.
What Is Crisis Management? A Working Definition
Crisis management covers four kinds of work:
- Preparation. A framework, a plan, and a trained team, in place before you need them.
- Response. A way to escalate, convene the right people, make decisions, and communicate with everyone who needs to hear from you.
- Recovery. A path back to normal operations, in the short term and the long term.
- Learning. A process to capture what happened and make the next response better.
Notice what is not on that list: a 300-page binder. Crisis management is not a document. It is a capability. The plan matters, but the plan is not the program. The program is the people, the practice, and the decisions you have rehearsed enough times that they feel familiar under pressure.
The international guidance agrees on that point. ISO 22361, the crisis management guidelines published in 2022, treats crisis management as a strategic capability that top management leads, not a procedure that sits with one department.
What Counts as a Crisis?
Not every bad day is a crisis. If you call everything a crisis, your team stops listening. If you call nothing a crisis until it is on the evening news, you activate too late.
The useful definition of a crisis is practical: a crisis is an event your normal operating structure can’t handle on its own. It needs a coordinated, cross-functional response and decisions above the level of any one team.
We use four severity levels to draw that line:
- Level 4: Routine event. Handled every day by the people who own it. A broken conveyor, a routine media call, a phishing email.
- Level 3: Escalating incident. A disruption within one area that requires mandatory notification, so nobody in leadership learns about it from the news.
- Level 2: Crisis. The organization can’t function normally, but its survival isn’t at risk. The cross-functional crisis team activates.
- Level 1: Critical disruption. Novel or extreme impact, potentially material, needing a round-the-clock operational and strategic response. Executives, and possibly the board, are engaged.
It doesn’t matter what you call the levels. It matters that everyone agrees on the definitions before the event. When IT’s “Severity 1” and the crisis team’s “Level 1” mean different things, somebody has to yield, and the middle of an incident is the worst time to decide who. Our guide walks through severity levels and activation in more detail.
Types of crises
Crises come from every direction:
- Cyber and technology: ransomware, data breaches, cloud and vendor outages
- Natural disasters: floods, wildfires, hurricanes, tornadoes
- Product and safety: contamination, recalls, injuries
- Workplace violence: threats, assaults, an active assailant
- Misconduct: fraud, executive misconduct, deception of stakeholders
- Reputational: a viral video, a social media attack, false rumors about your products
- Supply chain: the loss of a critical supplier or a single-source component
- Civil unrest: protests, boycotts, strikes, occupations
The list is useful for one reason: to show you that you can’t write a plan for every scenario. You don’t need to. A crisis is a crisis. How you got into it doesn’t change how you escalate, decide, and communicate. Build one crisis process for every crisis, then add short scenario annexes for the specific actions a cyber attack or a hurricane demands. I talked through why on Managing Uncertainty, Episode 279.
Routine Emergency or True Crisis?
There is one more distinction worth knowing, and it comes from Harvard’s Dutch Leonard.
In a routine emergency, the playbook works. A fire, a power outage, a severe weather warning: your plan, checklists, and trained team carry you through. The challenge is execution.
In a true crisis, something novel makes the playbook wrong or incomplete. The answers have to be invented in the room, under stress, with incomplete facts. Plans fail on contact with novelty. Process survives it.
That is why we build the process first. Read more about routine emergencies and true crises in the guide, or the longer piece on crisis leadership when the playbook fails.
What Is the Goal of Crisis Management?
The goal of crisis management is not to avoid damage. Crises almost always cause damage. The goal is to control how much, and to recover faster than you otherwise would.
In order of priority, crisis management exists to:
- Protect people. Life safety first: employees, customers, contractors, and the community. A prepared team accounts for its people faster.
- Keep the business running. Limit the operational, financial, and legal damage, and get critical operations back on their feet.
- Protect trust. Reputations take decades to build and minutes to lose. How you respond in the first hours is what customers, employees, and regulators remember.
- Learn. Capture what happened so the next response is better.
Underneath all four is one job: make good decisions quickly when the facts are incomplete. Perfect information never comes. If you wait for it, you have already lost. Silence and inaction are decisions too.
There is a limit worth stating plainly. Crisis management can’t save an organization from its own conduct. Peanut Corporation of America was the source of a 2008 to 2009 Salmonella outbreak that sickened 714 people in 46 states and may have contributed to nine deaths, according to the CDC. The company stopped operating and filed for bankruptcy in February 2009. Its former CEO was later convicted of knowingly shipping contaminated products and sentenced to 28 years in federal prison. No response plan fixes that. Crisis management works when leaders are willing to act on what they learn, even when it is expensive.
That is also why we measure a crisis response by the process, not the outcome. Even well-managed crises rarely end well. The question is whether your team escalated early, made sound decisions with what it knew, and communicated clearly. For the business case, see the value of effective crisis management.
Crisis Management vs. Business Continuity
The two are related and often confused.
Business continuity keeps your critical processes running through a disruption: the workarounds, the alternate sites, the recovery time objectives for each process.
Crisis management is the decision layer above it. It decides what matters most right now, which resources to commit, what to tell employees, customers, and regulators, and when to escalate to your executives and the board.
In a real event you need both, working from the same severity levels and the same escalation path. When they run as separate silos, the crisis finds the seams. Our Ultimate Guide to Business Continuity covers the continuity side.
The Basics: What a Crisis Management Program Includes
Crisis management doesn’t start with a set of plans. It starts with a framework: one way to escalate, decide, and communicate, whatever the event. Build that first, then the plans.
Our Bryghtpath Crisis Management Framework has six parts:
- Strategy. What the program protects and why, tied to your strategic objectives.
- Planning and preparedness. A focused plan, severity levels, decision rights, and short scenario annexes.
- Monitoring. A “radar screen” that spots issues early, around the clock, with triggers for escalation.
- Education and training. A crisis team that knows its roles and has practiced them.
- Crisis response. Activation, meetings with a fixed rhythm, decisions, and communication.
- After-action review. A hot wash right away and a formal After-Action Report (AAR) within 7 to 10 days, with owned actions.
Two roles hold it together. The incident leader owns the process: activates the team, chairs the meetings, and drives to decisions. The responsible executive makes or confirms the decisions that are above the team’s authority and connects the team to the rest of your executives. Around them sits the crisis management team: legal, HR, communications, IT, security, finance, operations, and every line of business that could be affected.
For the step-by-step build, see How to Craft Your Crisis Management Framework.
Nine Signs of Effective Crisis Management
We have reviewed hundreds of crisis programs. The ones that work share nine traits:
- A rapid response process, fed by a radar screen that spots issues early
- Clear roles and responsibilities, including a named incident leader
- A cross-functional coordination body, with every business line at the table
- Decision rights defined in advance
- A clear escalation path for declaring a crisis, committing capital or headcount, and approving external messages
- A single source of internal truth, with regular updates
- Communication products prepared in advance: messages and templates, with fast approval
- A documented, repeatable process, with a trained crisis team and a trained incident leader
- An after-action process that feeds every lesson back into the plan
If you are missing several, start with the three that cost the most time in a real event: decision rights, the escalation path, and a single source of truth. If you have multiple sources of truth, you will have multiple sets of facts, and multiple sets of facts confuse leaders.
Old View, New View
| Old View | New View |
| Crisis management is a plan on the shelf | Crisis management is a decision-making capability your team practices |
| Crisis management is a communications job | Communications is one part of a cross-functional response |
| Write a plan for every scenario | One process for every crisis, with short scenario annexes |
| Wait for the facts before activating | Over-respond, don’t overreact: activate early, assess, scale back |
| Judge the response by how it ended | Judge the response by how well the team decided with what it knew |
Where to Start
If your organization has no crisis management program, or one that hasn’t been touched in years, start here:
- Agree on your severity levels. Write down what a routine event, an escalating incident, a crisis, and a critical disruption look like in your business, with examples.
- Name your incident leader and two backups, plus the responsible executive for each severity level.
- Write down decision rights. What the crisis team decides, what is reserved to your executives, and what goes to the board.
- Set up one source of truth. One situational update, on a set cadence, that every leader works from.
- Run a tabletop exercise within 90 days, built around the scenario that worries your executives most. Then fix what it exposes.
The best time to decide how your organization will make decisions in a crisis is before you are in one.
Keep Going
A few ways to go deeper if this was useful.
- Read more. Resilience, crisis management, and continuity writing at Bryghtpath Insights, or the structured Ultimate Guide to Crisis Management.
- Learn the fundamentals. Our free Crisis Management 101 course covers the basics of building a crisis program.
- Get a maturity score. Our Resiliency Diagnosis® is a standards-based review that produces a maturity score and a prioritized roadmap.
- Talk to us. Set up a call to think through your program with us.





