A Lesson Is Not a Lesson Until You Do Something Different
Think about the last debrief you sat in after something did not go to plan. The one where the team discussed what had happened, identified what should have been done differently, generated some useful observations, and then returned to work.
How much of what was discussed in that room actually changed anything?
Not in theory. Not in intention. In practice, six weeks later, in the next comparable situation.
For most leaders and most organisations, the honest answer is: less than it should have. The 2022 systematic review of 59 studies on organisational resilience and learning identified this as one of the most consistent and costly failures in how organisations try to build resilience. The finding was unambiguous: "organisations often generate new knowledge but fail to translate this knowledge into new behaviours." And the conclusion was equally direct: a lesson has not been learned until it is successfully implemented.
The Difference Between Identifying Lessons and Learning Them
The confusion between these two things is so common it has its own name in the research literature. Organisations are systematically better at lesson-identification than at lesson-implementation. The debrief happens. The report is written. The recommendations are noted. The behaviours continue as before.
This is not cynicism about people’s intentions. Most leaders leave a post-mortem genuinely intending to do things differently. The gap is structural, not motivational. The conditions that would make the implementation more likely than the reversion — specific behavioural commitments, structured follow-through, accountability that outlasts the meeting — are almost always absent.
What the research identifies as necessary is a system: not just the learning moment, but the infrastructure that converts the learning moment into sustained behavioural change. Without that infrastructure, the learning evaporates. The familiar pattern reasserts — and the next comparable disruption produces the same inadequate response, with the same debrief, generating the same unimplemented lessons.
“Identifying what went wrong is easy. Changing what you do about it is the whole point. Most organisations are much better at the first than the second.”
How do you and your Organisation learn from disruption and genuinely do something different? photo Getty Images Unsplash
Why Implementation Is the Hard Part
The brain’s preference for established patterns is the primary structural obstacle to lesson implementation. As covered in the first blog in this series, new knowledge does not override existing habits. It competes with them. Under pressure — precisely the conditions when new approaches are most needed — the established pattern tends to win.
This is why the three conditions for sustained behaviour change are all necessary, not just useful. A specific, observable framework (The Resilience Wheel) makes the target behaviours concrete rather than vague. A reflective practice (the three questions) converts daily experience into deliberate adjustment rather than accumulated habit. A structured accountability relationship (coaching) provides the external consistency that internal intention cannot reliably maintain.
Without all three, lesson implementation is dependent on willpower, which is a finite and unreliable resource. With all three, implementation becomes progressively more natural as the new pattern builds and the old one weakens.
What Genuine Post-Disruption Learning Requires
The research is specific about what distinguishes organisations that genuinely learn from disruption from those that simply process it and move on. Four practices are consistently identified.
The first is root cause inquiry rather than surface correction. Many post-disruption reviews identify what went wrong without asking why it went wrong. The "five whys" approach — asking why repeatedly until the underlying system issue is surfaced — is more demanding than identifying the immediate failure point, and significantly more generative.
The second is cross-level knowledge transfer. Learning that stays within the team or department where the disruption occurred rarely produces organisational resilience. The knowledge needs to travel — across teams, functions and levels — to become a genuine organisational capability rather than a local adjustment.
The third is implementation commitment rather than aspiration. The difference between "we should do X differently" and "by this date, this person will have done X, and this is how we will know" is the difference between lesson identification and lesson learning.
The fourth is follow-through review. Genuine learning is confirmed not in the debrief but in the next comparable situation. Building a practice of reviewing not just what happened but whether the lessons from last time were actually applied is the most reliable test of whether learning has occurred.
The Organisational Resilience Wheel and Learning Infrastructure
The Organisational Resilience Wheel’s Adaptability dimension specifically asks whether the organisation has processes for learning from experience — not just responding to it. The Meaning dimension asks whether the collective narrative about setbacks is genuinely constructive: whether difficult events are treated as learning opportunities or quietly managed, explained away, or attributed to others.
An organisation that genuinely learns from disruption has these things embedded in how it operates, not just in how it talks about itself. The Organisational Resilience Diagnostic surfaces exactly where the gaps are — and provides a structured starting point for building the learning infrastructure that makes lesson implementation more likely than lesson evaporation.
Ready to have a conversation?
Start with the Organisational Resilience Diagnostic — a structured, honest snapshot across The Resilience Wheel.
Organisational Resilience Diagnostic:
theresiliencecoach.co.uk/resilient-organisations-diagnostic
Book an introductory call: