Standards, frameworks, and templates give us a shared language for crisis management. They align expectations and create consistency across organizations.  The risk is not in using them, but in optimizing for the document instead of the work that should come before it.

A crisis plan only becomes valuable once people have aligned on how they think, decide, and act under pressure. The plan should capture that thinking. It should never replace it.

If I had to set up a crisis management function today, with limited time, attention, and organizational patience, this is how I would spend the day.  I am not aiming for completeness. I am aiming for a foundation that works when things are unclear, evolving, and uncomfortable.

9:00 – Decision Principles First

I would start by defining four or five principles that guide decisions in a crisis. When information is incomplete, principles matter more than procedures.

My default first principle is simple: we treat customers the way we would want to be treated ourselves. That single sentence resolves more trade-offs than most detailed playbooks ever will. It influences how transparent we are, how quickly we communicate, and how we balance legal, reputational, and operational considerations once pressure builds.

In a crisis, teams rarely lack opinions. What they lack is a shared reference point that keeps decisions consistent when facts are still emerging.

9:30 – From Observation to Escalation

Early situations are rarely black and white. They evolve, sometimes quickly, sometimes slowly. Not everything needs to be escalated into a full, company-wide crisis immediately, but waiting for perfect clarity is what usually causes delay. What matters is having structure before certainty.

At this stage, I would define when we move from normal operations into structured observation, who is involved in that early assessment, and how escalation works once thresholds are met. In practice, this means agreeing on a small number of directional triggers that signal when escalation is required. Examples could include a significant portion of staff being unable to work, any credible risk of a breach of customer or personal data, a confirmed data breach, or severe reputational damage likely to impact the business in the short or long term.

A good crisis structure allows an organization to move quickly without overreacting.

10:30 – Assemble the Crisis Core Team

Next, I would assemble a small crisis core team. This typically includes customer-facing roles, legal, technology, communications, and security, along with one or two relevant executives. People are part of this team because they have authority and accountability in their domains, not because of their titles alone.

This is also where buy-in matters most. Being part of the crisis team means crisis responsibilities supersede day-to-day work, even if the situation is not yet visible across the entire organization. The role of the crisis function is to remove friction so decision-makers can focus on their responsibilities, rather than on figuring out how coordination, communication, or escalation works.

I would collect their contact details and reach out to them directly to make this explicit, using both official communication channels and an out-of-band option. Membership, expectations, and how we stay in touch should be clear from the start. This avoids confusion later, when speed and clarity matter most.

12:00 – Lunch

By noon, we have already made real progress. Lunch is a chance to recharge before moving into the more hands-on work of the afternoon.

1:00 – Plan and Run a Walkthrough

After lunch, I would run a walkthrough. Not to test edge cases or exhaust scenarios, but to practice activation and coordination.

I would choose a realistic loss scenario, ideally one with clear customer impact. Then we walk through how the team assembles, how information flows, how decisions are made and logged, and how documentation supports the team without slowing it down. This is where decision principles show up in practice and where alignment becomes necessary, practical and trained.

Walkthroughs build trust quickly. Teams that have already navigated uncertainty together behave very differently when it actually matters.

3:30 – Coffee and Reflection

A short pause to reflect on what felt unclear, slow, or awkward while it is still fresh. These moments often surface the most valuable insights, long before anything is written down.

4:00 – Rough Dependency Mapping

To close the day, I would sketch a rough dependency map. Starting with the organization’s mission, we identify the critical services that support it and then look at what those services depend on, across technology, people, suppliers, and capabilities.

The map will be incomplete, and that is expected. The objective is visibility, not documentation. It connects crisis management to the broader resilience backbone and helps us understand how to navigate the organization based on impact, where confidence is high or low, where known single points of failure exist, and where improvement efforts will matter most. In practice, this becomes tomorrow’s to-do list for strengthening resilience.

5:00 – Back to Real Life

The work is done for today. Time to pick up the kids from daycare.

What You Have by the End of the Day

By the end of this day, the organization knows when it considers itself to be in a crisis, who is involved and fully committed, how decisions are made and coordinated, and where actions and information flow. It also has an initial view of which dependencies matter most.

You do not have a perfect plan. You have something more useful: a shared way of operating under pressure.

Key Takeaways

• Do the thinking before the documentation. Crisis plans only add value once decision logic, roles, and coordination are clear.
• Principles guide decisions when data is incomplete. A small set of shared principles prevents hesitation and internal friction under pressure.
• Structure enables speed without overreaction. Clear observation and escalation paths allow teams to move fast while situations are still evolving.
• Commitment matters more than formal roles. Crisis teams work when members are explicitly empowered and fully bought in.
• Walkthroughs build capability faster than writing. Practicing activation, communication, and decision-making creates trust and muscle memory.
• Crisis management is the entry point to resilience. Dependency visibility and coordination under pressure lay the foundation for broader resilience capabilities.

Crisis management is not built in a document. It is built through alignment, decisions, and shared understanding under uncertainty. The document should simply capture that work, not substitute it.

A single focused day will not make an organization resilient. It does, however, create a common operating model for pressure. From there, resilience becomes a deliberate and achievable build, rather than an abstract ambition.

###

What are your thoughts on this article? Do you agree?  Anything to add? Come to LinkedIn to share your thoughts on Patrick’s insights.  Or, Engage with Patrick at LinkedIn.