Organizational Crisis Management

Organizational crisis management (business-focused summary)

Purpose

• Equip organizations with tools to anticipate, respond effectively, and learn from crises to improve resilience.
• Emphasizes that crisis management must be systematic and ongoing, not improvised during an incident.

Why many organizations are unprepared

• Cites a 2011 Sherm study:
  • 76% of American organizations had a crisis management plan
  • Only 33% felt “very well prepared”
• Gap attributed to lack of systematic crisis management programs and planning.

---

Core framework / playbook (end-to-end)

1. Prevent / anticipate (pre-crisis readiness)

   • Identify potential risks early
   • Perform a risk assessment:
     • Identify risks
     • Estimate likelihood
     • Evaluate business impact (e.g., loss of customers, reputation tarnish, drop in sales)

2. Design the response (so speed and clarity aren’t improvised)

   • Define communication protocols
   • Assign clear roles to team members
   • Establish an activation protocol and emergency contact numbers

3. Execute during the crisis

   • Transparent, quick communication with:
     • Internal stakeholders
     • External stakeholders
   • Leadership behaviors:
     • Make quick decisions
     • Stay calm
     • Inspire confidence
   • Decision process:
     • Quickly assess the situation
     • Consult the right experts
     • Choose the best response
     • Maintain flexibility to adjust as the crisis evolves
   • Example operational approach (cyber attack):
     • Assign people to:
       • Secure the network
       • Inform customers
       • Assess damage

4. Learn / improve (post-crisis)

   • Conduct a post-crisis evaluation
   • Capture what worked vs. what to improve
   • Feed lessons back into the system to strengthen future resilience

5. Keep it current

   • Treat the crisis plan as a living document
   • Regularly review and update it as risks and conditions change

---

Key business impacts to account for

• Customer loss
• Reputational damage
• Sales decline

---

Metrics / targets mentioned

• Preparedness gap (from Sherm, 2011):
  • Plans exist: 76%
  • Feel “very well prepared”: 33%

No additional quantitative KPIs, targets, or timelines were provided beyond this preparedness statistic.

---

Actionable recommendations (from the training)

• Build risk assessments by likelihood + business impact, not just a list of threats.
• Pre-define who does what, especially for incident response (secure systems vs. customer comms vs. damage assessment).
• Use rapid, transparent stakeholder communication to limit rumors and maintain trust.
• Run post-incident reviews and update the plan continuously (living document).
• Ensure leadership is prepared to decide quickly and guide calmly, consulting experts as needed.

---

Presenters or sources

• Source cited: Sherm study (2011)
• Presenter(s): Not explicitly identified in the subtitles.