The Empty Ritual: Why Your Post-Mortem Guarantees Future Failure

99%

The Empty Ritual: Why Your Post-Mortem Guarantees Future Failure

We are obsessed with blamelessness, and in doing so, we have sterilized the possibility of genuine growth.

I’m watching the little grey circle spin. It’s sitting there at 91 percent, then 98 percent, and finally, it hangs at 99 percent like a person holding their breath until they turn blue. I’ve been staring at this loading bar for what feels like 11 minutes, a digital purgatory that perfectly mirrors the state of modern corporate accountability. It’s that agonizing pause where everything is almost finished, but the final, most crucial bit of data-the truth-just refuses to load.

Winter D.-S. is sitting in the passenger seat next to me… He watched a student driver roll slowly into a stop sign yesterday. In the report, the student wrote that ‘environmental factors and brake-pressure variability led to a sub-optimal stop.’ Winter just looked at him and said, ‘You didn’t hit the pedal, kid.’

That’s the core of it. We are currently obsessed with the ‘blameless post-mortem,’ a ritual designed to protect feelings while ostensibly improving systems. We gather in a room that smells faintly of 41-cent whiteboard markers and unearned confidence. We pull up a slide deck that took someone 31 hours to build. We look at a catastrophic failure-a server crash, a lost client, a botched launch-and we perform a surgical extraction of human agency.

The Beautiful, Empty Sentence

31

Hours Spent

11

Warnings Ignored

0%

Actual Solution

The final slide of the presentation invariably reads: ‘Key Learnings: Improve Cross-Functional Communication.’ Everyone in the room nods sagely. It is a beautiful, empty sentence. It is the 99 percent buffer of corporate insights. It looks like progress, it feels like progress, but it contains 0 percent of the actual solution.

We conveniently ignore that the project failed because a specific VP ignored 11 direct warnings from the engineering team. We ignore that the lead developer was spread across 21 different tasks and simply stopped caring. By focusing only on abstract ‘process’ issues, we fail to address the poor decisions or incompetence that actually caused the crash.

πŸ˜”

The Hiding Place

I’ve done this myself. I once wrote a 151-page post-mortem for a failed software rollout… I hid behind the ‘system’ because the system doesn’t have a face you have to look at during lunch.

The Sun, The Branch, and The Phone

Winter D.-S. told me about a crash he witnessed 11 years ago. Two cars met at a four-way stop. One driver claimed the sun was in their eyes; the other claimed the ‘stop’ sign was slightly obscured by an overgrown branch. They both blamed the environment. They both blamed the city’s maintenance ‘process.’ Neither of them admitted they were both looking at their phones.

β˜€οΈ / 🌳

External Factors (Blamed)

VS

πŸ“±

Internal Action (Ignored)

In a corporate post-mortem, we would have spent 31 minutes discussing sun-glare mitigation strategies and 21 minutes on a branch-trimming schedule. We would have walked away feeling productive, while both drivers continued to text while driving.

The Cost of Protecting Incompetence

This faux-psychological safety actually creates more risk by making incompetence a protected class. When you remove the possibility of blame, you also remove the possibility of excellence. If no one is responsible for the failure, then no one can be truly responsible for the success. We’ve turned accountability into a dirty word, something to be avoided at all costs, like a 101-degree fever.

Clarity Over Comfort

Consider the ν™˜μ „ κ°€λŠ₯ κ½λ¨Έλ‹ˆ user protection community.

In that world, if a platform fails to pay out or if a scam occurs, they don’t sit around talking about ‘cross-functional communication gaps.’ They name the perpetrator. They document the specific lie. They understand that honest assessment is the only foundation for safety.

Winter D.-S. grabbed my steering wheel once when I was 21. I had drifted toward the center line while adjusting the radio. I started to say that the knob was sticky, that the sun was bright, that the lane markings were faded. He didn’t let me finish. He just said, ‘The car goes where you point it. Point it somewhere else.’ It was the most honest post-mortem I’ve ever received.

The Courage to Own the Wreckage

We need to stop treating incompetence as a systemic glitch. Sometimes, a project fails because someone didn’t do their job. Sometimes, a VP makes a call based on ego rather than data. Sometimes, the ‘process’ was fine, but the execution was lazy. If we can’t say those things out loud, we are just waiting for the next 131-page report about it.

The 99 Percent Stalemate

I realize now that it’s not the internet connection that’s stalled; it’s the file itself. It’s corrupted. It was built on a foundation of half-truths, and the system can’t reconcile them. We try to upload a version of reality that doesn’t include our own mistakes, and we wonder why the progress bar never hits 101 percent.

To build something that actually lasts, you have to be willing to look at the wreckage and say, ‘I did this.’ Or, ‘He did that.’ It’s not about cruelty; it’s about clarity. Rigorous, honest assessment is the only way to break the cycle. Everything else is just a 21-minute exercise in creative writing disguised as a business meeting.

✍️

Winter D.-S. finally let go of the brake handle… He just pointed at the tire marks on the pavement. ‘That’s your signature,’ he said. ‘Decide if you want to sign your name to that again.’

We are all signing our names to failures every day. We can either pretend the pen was broken, or we can learn how to write a better story.

The loading bar is still spinning, but I’ve decided to close the tab. I don’t need to wait for the 99 percent to finish when I already know what the last 1 percent looks like. It looks like the truth, and it’s been sitting right in front of me for 41 minutes, waiting for me to be brave enough to say it.

Posted on Tags