The cursor flickers on slide 32 of a deck that was supposed to be 12 slides long. I’m dragging a red rectangle over a cluster of data points that represent a catastrophic collapse in our Q2 deliverables. Outside the glass walls of the conference room, the city hums with 102 different types of noise, but in here, there is only the rhythmic click of my mouse and the heavy, collective breath of 12 people who would rather be literally anywhere else. We are here to conduct a post-mortem. It is a sterile word for a bloody process. We call it ‘lessons learned,’ a phrase that carries the same weight as ‘with all due respect’-which is to say, none at all.

“The post-mortem isn’t actually about preventing the next disaster. It’s about the absolution of the current one. If we can name the demon-if we can label it ‘Poor Cross-Departmental Synergy’-then the demon no longer has power over our performance reviews.”

– Claire J.P., Meme Anthropologist

I once spent 42 hours preparing a report on why a server migration failed, only to realize halfway through that I was the one who had accidentally deleted the root directory. Did I put that in the report? Not in so many words. I used the phrase ‘unanticipated permission conflicts during the execution phase.’ It sounded professional. It sounded like something that happened to us, rather than something I did. And that is the fundamental lie of the post-mortem. It removes the ‘I’ and the ‘we’ and replaces them with the ‘it.’ The project failed. The communication broke down. The deadline was missed. These are passive voice tragedies.

We sit in these rooms for 62 minutes at a time, nodding sagely at ‘Action Items’ that have the structural integrity of wet tissue paper.

There is a specific kind of silence that follows the presentation of the Action Items slide. It’s the silence of 12 people realizing that none of these items will ever be completed. We will leave this room, delete the calendar invite, and the PDF will sit in a folder titled ‘Archive_2022_Do_Not_Delete’ until the heat death of the universe or the next server migration, whichever comes first. This is how organizations learn to fail better, or rather, how they learn to fail with more paperwork. It’s a protection racket where the currency is jargon.

The 52 Variations of ‘Be Better’

Claire J.P. once sent me a screenshot of a post-mortem from a defunct tech startup that had 52 distinct action items. Every single one was a variation of ‘be better.’ They went bankrupt 12 weeks later. There is something deeply human about that-the refusal to look at the rot in the foundation because we’re too busy debating the color of the paint on the third floor.

The Amber of True Heritage

True heritage isn’t about repeating the same motions; it’s about understanding the ‘why’ behind the ‘how.’ In industries where history actually matters, you don’t just file away a failure. You taste it. You let it age. You understand that you cannot rush the process of learning. When you look at the deep, amber history of something like Old Rip Van Winkle 10 Year Old, you aren’t seeing a list of Jira tickets or a vague commitment to ‘improve fermentation cycles.’ You are seeing the result of decades of actual, painful experience where the stakes weren’t just a missed KPI, but the loss of an entire legacy.

In the corporate world, we’ve decoupled the consequence from the ritual. If a master distiller ruins a batch, they don’t write a slide deck; they lose the batch. They feel the loss in their bones and their ledger. But in our glass-walled conference rooms, the only consequence for a $500002 failure is a 72-minute meeting where we drink lukewarm sparkling water and agree to ‘touch base’ more often. We have ritualized the failure to the point that the failure itself becomes a comfortable part of the quarterly cycle.

The Unvarnished Circle

Claire J.P. argues that if we actually wanted to learn, the post-mortem wouldn’t have any slides. It would involve 12 people sitting in a circle, admitting to 1 specific thing they personally screwed up, and then figuring out how to fix that one thing. No jargon. No passive voice. Just the uncomfortable, sweating reality of human fallibility. But that would require a level of psychological safety that most companies haven’t seen since 1992. It would require us to stop pretending that we are optimized machines and start admitting that we are just people trying to figure things out in a room that is always 2 degrees too cold.

I’ve noticed that the longer the post-mortem document is, the less likely it is that anything will change. A 2-page document might contain a kernel of truth. A 132-page document is a shroud. It’s designed to be so dense that no one can find the blame hidden inside it. We’ve become experts at the post-mortem because it’s the only part of the project where we are guaranteed to succeed.

The Fear of History

Perhaps the real ‘lesson learned’ is that we are afraid of our own history. We are afraid that if we look too closely at the 22 projects we’ve botched in the last 2 years, we’ll realize that the problem isn’t the process or the communication or the tools. The problem is the fundamental structure of how we value ‘doing’ over ‘being.’ We would rather do a hundred useless post-mortems than be quiet for 12 minutes and listen to what the failure is actually trying to tell us.

I wonder if Claire J.P. is right. Maybe the only way to win is to stop writing the reports. To let the failure sit there, ugly and unwashed, until it bothers us enough to actually change. But for now, I have 12 pairs of matched socks and a slide deck to upload. The ritual continues. The absolution is complete. I’ll see you at the next one in 32 days. Or maybe 42. Who’s counting anyway?