"We need to learn from this." The phrase hangs in the air like an ending that refuses to end. Around the table, everyone nods. Of course we need to learn. We always need to learn. We have learned so much from so many failures that by now we should be wise beyond measure. Yet here we are again, performing the familiar choreography of retrospection, preparing to learn what we already know we'll learn: nothing that matters.
Organisations speak of learning from failure with religious fervour, but the conversion never quite takes. This is not hypocrisy. It's something more interesting: a collective mythology that serves purposes we rarely examine. The story of learning from failure has become one of the great organisational fictions of our time, not because it's untrue, but because it conceals more than it reveals.
What we call learning from failure is often a mechanism for metabolising threat while preserving existing structures. The organisation must appear to change while ensuring nothing fundamental shifts. The post-mortem becomes a ritual of containment, transforming potential systemic questioning into manageable technical adjustments. We learn to fail better within the same constraints that produced the failure.
Power authors the very category of failure. Senior leadership's strategic missteps become "bold experiments." Operational failures lower in the hierarchy become evidence of incompetence. The same outcome carries different meanings depending on who owns it. A project hemorrhaging money for three years might never be coded as failure if the right executive sponsors it, it's a "long-term investment" until the sponsor moves on, at which point it retrospectively becomes their predecessor's folly.
The organisation's memory proves endlessly editable. When does a failure begin? When does it end? The answers serve present power dynamics. The boundaries we draw around failure are never neutral; they're political acts that determine what can be thought, who bears responsibility, what remains untouchable.
In the gaps between what happened and what we say happened, entire worlds disappear. The failure that might have taught us about the violence of our performance system becomes a lesson about "clearer goal-setting." The failure that might have revealed how our structures systematically exclude crucial voices becomes a reminder to "communicate more effectively." We learn what we can afford to learn.
The comfort we take in root cause analysis reveals our discomfort with genuine unknowing. There must be a source, an identifiable point where things went wrong. This isn't learning; it's anxiety management. The five whys become a ritual of false certainty, each why taking us further from the irreducible complexity of what actually happened. We'd rather have a wrong answer than live with the vertigo of not knowing.
But unknowing operates deeper still. The failures we recognise are vastly outnumbered by the failures we never notice, the initiatives that quietly die, the innovations that never emerge, the voices that learn to stay silent. For every dramatic failure that gets its post-mortem, there are countless slow failures that never register as failures at all. They're just "the way things are."
Real learning might require sitting with unknowing long enough for new patterns to emerge, but the organisational metabolism rarely allows this patience. The quarterly review demands lessons. The board wants action items. So we manufacture them, choosing from the infinite field of possible causes those that fit our existing frameworks, that don't threaten too much, that can be addressed without fundamental change.
The stories we tell about failure become more real than the failures themselves. A project's failure crystallises into narrative "we were too ambitious," "the market wasn't ready" and this becomes organisational truth. Alternative interpretations fade. The story hardens into memory, shaping how future failures will be understood.
These narratives distribute responsibility in ways that preserve existing hierarchies. The executive whose pet project fails frames it as "pushing the boundaries of innovation." The team whose project fails finds themselves restructured out of existence. Same failure, different meanings, different consequences. Meaning-making around failure is never neutral; it's a political process that determines what changes and what endures.
The language itself reveals these dynamics. "Failure" carries violence, so we soften it: setback, challenge, learning opportunity. This isn't just euphemism, it's active meaning-making that shapes what's possible to think and feel. When failure becomes a "learning opportunity," certain responses become appropriate (reflection, adjustment) while others become inappropriate (grief, anger, systemic questioning).
The organisation becomes a museum of unintegrated failures, each processed into something digestible. The failures accumulate, each with its tidy lesson attached, while the patterns that connect them remain invisible. We learn from each failure in isolation, never stepping back to see the failure of failures.
There are those who have permission to fail and those who don't. The entrepreneur celebrating their failures at the innovation summit occupies a different universe from the operations manager whose single mistake becomes career-limiting. Psychological safety, that prerequisite for learning from failure, is distributed along existing lines of power and privilege.
The same organisation that encourages "intelligent failure" in its innovation lab might operate a performance system that punishes any deviation from plan. Those without failure privilege learn quickly that the organisation's embrace of failure is rhetorical. They watch colleagues fail upward while knowing their own failures would mean exile.
Even the ability to admit failure becomes privilege. The leader who says "I failed" performs a vulnerability that actually reinforces their power, they're secure enough to admit failure without being diminished by it. Meanwhile, those with precarious belonging learn to hide their failures, to never quite admit when things go wrong.
The rituals around failure, post-mortems, retrospectives, lessons learned, become performances of belonging. Who gets invited, whose voice carries weight, whose interpretation becomes official, these inclusions and exclusions reinforce existing hierarchies. The junior engineer might sit in the retrospective, but their observation about systemic dysfunction will be translated into something safer.
The organisation creates elaborate mechanisms to appear to learn while ensuring that learning remains superficial. The lessons learned database fills with entries no one reads. The retrospective generates action items that reproduce the same dynamics. We perform learning without transformation, change without difference.
This isn't necessarily conscious. Organisations, like all human systems, resist threats to their coherence. Real learning from failure would require questioning fundamental assumptions, examining power structures, reimagining possibilities. This threatens the organisation's sense of itself. So we create sophisticated simulations of learning, convincing enough to feel real but safe enough to leave deep structures untouched.
The consulting firm analysing its failed client engagement will focus on process improvements. It won't question whether its fundamental model, parachuting in expertise, generating recommendations, leaving, might be the failure. The technology company examining its failed product launch will discuss market fit. It won't examine whether its entire approach to innovation rests on flawed premises about human needs.
The four forces, dynamics, unknowing, meaning, and belonging, interweave around every failure, creating a complex field that resists simple interpretation. Power shapes what can be known, unknowing destabilises meaning, meaning determines belonging, belonging influences power. The failure exists not as a discrete event but as a node in this living network.
A team's failure to deliver on time might seem straightforward, but the fractures reveal complexity. The dynamics of power meant certain concerns couldn't be raised. The unknowing about technical complexity was systematically suppressed. The meaning of "on time" shifted depending on who was asking. The belonging of team members affected whose expertise was trusted. The failure is not one thing but many things, not one story but multiple stories.
The mythology of learning from failure serves important functions. It makes the unbearable bearable. It transforms suffering into meaning. These are not small things. Organisations need stories to survive. The problem is not the mythology itself but our forgetting that it is mythology.
When we mistake the story for reality, when we believe we're actually learning rather than performing elaborate rituals of containment, we lose the possibility of genuine transformation. The failures continue, wearing different costumes but following the same patterns. The organisation becomes like someone who gains insight after insight without ever changing their behaviour.
What if failure is not a teacher but a mirror? What if it doesn't provide lessons but reveals what we already are? What if the point is not to learn from failure but to see how our responses to failure expose the invisible structures that shape organisational life?
The meeting ends. The action items are assigned. Everyone agrees on the lessons learned. Tomorrow, the same dynamics will produce new failures that we'll process through the same machinery. We'll call it learning, and in a sense, it will be, we'll learn, again and again, how to maintain the illusion that we're learning.
The tragedy is not that organisations fail to learn from failure. The tragedy is that they succeed too well at creating the appearance of learning, at metabolising threat into method, at transforming the potential energy of failure into the kinetic energy of business as usual. We become experts at learning the wrong lessons, masters of missing the point.
In the end, perhaps the most honest thing we could say about failure is nothing. Perhaps the most useful thing we could do is stop pretending we're learning and sit with the discomfort of what failure actually reveals: that our organisations are not machines for learning but organisms for surviving, not systems for growth but structures for preservation, not vessels for transformation but elaborate mechanisms for staying exactly as we are while appearing to change.
The next failure is already taking shape in the space between what we say and what we do, between what we know and what we can bear to know, between who belongs and who doesn't, between the story we tell and the truth we live. We'll meet it with our post-mortems and our action items, our lessons learned and our process improvements. We'll call it learning. We'll believe ourselves. And nothing will change.