When a crisis ends, the instinct is to move on. Teams are exhausted, normal work has piled up, and leaders want to put the disruption behind them. Yet the period after a crisis is one of the most valuable an organization will have. It is the moment when weaknesses are most visible, when people are most willing to change, and when leaders have the clearest view of what truly matters to customers, employees, and the business.
Organizations that use this moment well come out stronger. They fix what failed, reinforce what worked, and make decisions that leave them better prepared for whatever comes next. This article explains how to turn disruption into lasting improvement through disciplined lessons learned. It is written for executives and the operational resilience, continuity, and crisis leaders who guide recovery.
Why this matters
Every crisis tests assumptions. Some plans work as intended; others fail in ways no one predicted. Some decisions prove sound; others look different with hindsight. The organization learns, in a very direct way, where its resilience is real and where it was assumed.
That knowledge is perishable. Within weeks, memories fade, people move on, and the details that would have explained why something went wrong are lost. Without a deliberate process, the same problems resurface in the next disruption.
Recognized guidance treats learning as an essential part of resilience. ISO 22301:2019 requires organizations to react to nonconformities, determine their causes, take corrective action, review the effectiveness of that action, and continually improve their business continuity management system. ISO 22361:2022 includes training, validation, and learning from crises as a core element of crisis management. NIST's incident response guidance, SP 800-61 Revision 3, emphasizes that lessons learned from incidents should feed back into governance, risk identification, and protection, not only into the incident response process itself. FEMA's Homeland Security Exercise and Evaluation Program (HSEEP) offers a widely used structure for capturing findings in an after-action report and tracking corrective actions in an improvement plan.
The business challenge
Organizations often intend to learn from crises but fall short in practice.
- Reviews happen too late, or not at all. By the time a formal review is scheduled, the people involved have dispersed and memories have faded.
- Reviews become exercises in blame. When post-crisis reviews focus on individual fault, people become defensive, and the systemic causes of problems remain hidden.
- Findings are too general to act on. Lessons such as "communication should be improved" describe a symptom without identifying what specifically must change.
- Actions are not owned or tracked. Recommendations are listed in a report but not assigned, resourced, or followed up, so little changes.
- Effectiveness is never verified. Even when actions are completed, no one checks whether they actually solved the problem.
- Lessons stay local. Insights from one business unit or one crisis are not shared with others who face similar risks.
- People's recovery is overlooked. Staff who carried the response may be exhausted or affected, and their experience is not acknowledged or supported.
Key concept: a disciplined lessons-learned cycle
Turning a crisis into lasting improvement requires a cycle that begins before the response ends and continues until changes are proven.
1. Capture while it is fresh
Learning starts during the response. Decision logs, situation reports, and communication records created during the crisis are the raw material of later review. As soon as practical after the acute phase, short "hot debriefs" with each team capture immediate impressions: what worked, what did not, and what surprised them. These debriefs do not need to be polished. Their value is in preserving details that would otherwise be lost.
2. Conduct a structured review
A more formal review follows once the organization has stabilized. It should reconstruct the timeline of events and decisions, compare what happened with what plans anticipated, and examine both outcomes and the conditions that shaped them. Effective reviews draw on records as well as interviews, include people from every level and function involved, and involve key third parties where appropriate.
3. Focus on systems, not scapegoats
A blameless approach does not mean ignoring accountability. It means recognizing that most failures in a crisis arise from conditions such as unclear roles, missing information, untested assumptions, or inadequate tools, rather than from individual negligence. Asking "what made this outcome likely?" rather than "who got this wrong?" surfaces the causes that can actually be fixed, and encourages people to share what they really saw.
4. Identify root and contributing causes
For each significant finding, the review should trace the issue back to its underlying causes. A delayed decision, for example, may have stemmed from an unclear activation threshold, an unavailable decision-maker with no designated deputy, and a situation report that did not highlight the decision needed. Each cause suggests a different corrective action.
5. Turn findings into specific, owned actions
Every finding should lead to an action that is specific, has a named owner, a target date, and the resources needed to complete it. HSEEP's improvement planning model, which pairs each corrective action with a responsible owner and a completion date, is a useful reference. Actions should be prioritized by their importance to critical services and stakeholder outcomes, so that limited capacity is spent where it matters most.
6. Verify that changes work
Completing an action is not the same as solving the problem. The organization should confirm through testing, exercises, or observation that the change has the intended effect. ISO 22301's requirement to review the effectiveness of corrective action reflects this principle.
7. Share and embed lessons
Lessons should be shared across the organization, adapted for other business units and scenarios, and embedded in plans, training, and exercises. A crisis in one part of the organization is an opportunity for every part to improve.
Learning from near misses
Not every lesson requires a full crisis. Near misses, such as a supplier problem caught just in time, an outage contained before customers noticed, or an exercise that exposed a gap, carry many of the same insights at a fraction of the cost. Organizations that review near misses with the same discipline they apply to major events build a steady stream of improvement, and they reduce the chance that a small weakness grows into a serious crisis. A lightweight review format, with a short timeline, causes, and one or two owned actions, makes this practical.
Looking beyond repair
The most resilient organizations use crises as a prompt to ask bigger questions, not only to repair what failed. A crisis can reveal that a critical service depends too heavily on a single provider, that a process is more complex than it needs to be, or that the organization's priorities are not reflected in its investments. It can show which capabilities, such as remote working, alternative suppliers, or manual workarounds, proved more valuable than expected. Leaders who take time to consider these strategic lessons can make decisions that strengthen the organization well beyond the specific scenario it faced.
Caring for people
Recovery also involves people. Staff who led the response may have worked long hours under pressure, and some may have been personally affected by events. Acknowledging their efforts, offering support where needed, and giving them a voice in the review process all contribute to recovery and to the organization's readiness for the next crisis. People who feel their experience was heard are more likely to engage fully the next time.
An illustration
Consider a manufacturer that experienced a prolonged outage at a key supplier, halting production on two lines. The response held up reasonably well, but the hot debriefs revealed frustration: procurement learned of the supplier's problems from a trade publication, the crisis team spent the first day debating who could authorize premium freight, and customers received conflicting delivery estimates. The structured review traced these issues to an absence of supplier early-warning arrangements, an unclear spending authority during crises, and the lack of a single source of customer information. Actions were assigned to named owners: new notification terms in supplier contracts, a pre-approved crisis spending threshold, and a customer communication protocol. Six months later, an exercise tested all three, and two worked as intended while the third needed refinement. At the strategic level, leadership decided to qualify a second supplier for the affected component. The organization did not simply recover; it came out more resilient.
What organizations should do
A practical lessons-learned program typically includes these elements.
- Plan for learning before the next crisis. Include lessons-learned steps, roles, and templates in crisis and continuity plans.
- Keep good records during response. Maintain decision logs and situation reports that will support later review.
- Hold hot debriefs promptly. Gather immediate impressions from each team once the acute phase has passed.
- Conduct a structured, blameless review. Reconstruct the timeline, compare it with plans, and identify root and contributing causes.
- Produce an after-action report and improvement plan. Assign every action to an owner with a target date and resources.
- Track actions at the executive level. Review progress regularly, and escalate actions that stall.
- Verify effectiveness. Test or exercise changes to confirm they work.
- Share lessons widely. Communicate findings across the organization and update plans, training, and exercises.
- Consider strategic implications. Ask what the crisis revealed about priorities, dependencies, and investments.
- Support the people involved. Recognize the response team's efforts and provide support where needed.
Leadership considerations
Executives determine whether an organization truly learns from crises.
- Make learning an expectation. Leaders should commission reviews after significant events and near misses, not only after major crises.
- Protect candor. People will share what really happened only if they trust that the review is about improvement rather than blame.
- Commit resources. Improvement actions require time and investment. Without them, reviews produce reports rather than change.
- Follow up personally. Executive attention to the status of improvement actions signals that they matter.
- Look for the strategic lesson. Ask what the crisis revealed about the organization's resilience priorities and whether investments reflect them.
- Recognize the people. Thanking those who carried the response, publicly and specifically, builds the culture that makes the next response stronger.
How OpResONE can help
OpResONE helps organizations turn disruption into lasting improvement. Our Crisis Management advisory work can include:
- Facilitating hot debriefs and structured, blameless post-crisis reviews.
- Identifying root and contributing causes and translating them into specific, owned improvement actions.
- Building after-action reporting and improvement tracking that leadership can oversee.
- Designing exercises that verify whether improvements work.
- Helping leaders consider the strategic implications of a crisis for priorities, dependencies, and investment.
For professionals building resilience expertise, OpResONE is an authorized PECB training partner and offers training courses that prepare candidates for PECB credentials, including PECB Lead Operational Resilience Manager and Lead Crisis Manager. PECB awards the credentials.
Related resources
- Crisis Management advisory services
- From Disruption to Opportunity
- The Executive's Guide to Crisis Readiness
- Communicating with Clarity in a Crisis
- Operational Resilience advisory services
Schedule a strategy call
If your organization has come through a disruption, or wants to be ready to learn from the next one, a focused conversation can help. Schedule a strategy call with OpResONE to discuss how to turn experience into lasting resilience.
Sources
- ISO 22301:2019, Security and resilience — Business continuity management systems — Requirements
- ISO 22361:2022, Security and resilience — Crisis management — Guidelines
- NIST SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile (April 2025)
- FEMA, Homeland Security Exercise and Evaluation Program (HSEEP) Doctrine, 2020 revision

