Now, the cursor blinks on the shared document at 2:01 AM, a rhythmic, taunting reminder that the blank space under ‘Root Cause’ needs to be filled with something that sounds like progress but feels like an escape. Eleven people are currently hovering in the document, their anonymous animal icons-a kraken, a nyan cat, a wombat-flickering at the top of the screen. We are all pretending to be detectives, but we are actually just funeral directors for the same ghost. My eyes burn, likely because I spent the last forty-one minutes clearing my browser cache in a desperate, superstitious attempt to make the internal monitoring dashboard reflect a reality that isn’t broken. It didn’t work. It never works. Clearing the cache is the digital equivalent of crossing your fingers behind your back while swearing an oath.

Insight: The Shield

I work as a museum education coordinator, a role that, on the surface, has nothing to do with server clusters or high-availability databases. Yet here I am, Riley J.D., pulled into another ‘blameless post-mortem’ because our digital archive went dark during the most visited hour of the year. The lead engineer is currently typing a sentence about ‘unexpected latency in the upstream provider,’ a phrase so beautiful and hollow it belongs in a gallery of contemporary art. It’s a linguistic shield. If the failure is ‘upstream,’ then the stain on our carpet isn’t our fault. We write these documents not to learn, but to achieve a state of corporate absolution.

We want to be told that we did our best, that the systems are complex, and that if we just add one more alert to the 101 alerts we already ignore, it won’t happen again.

But it will happen again. It happened in May. It happened last November. It will happen again in precisely 31 days if the traffic patterns hold. We are trapped in a liturgical cycle where the post-mortem is the confession, the action items are the penance, and the subsequent outage is the inevitable fall from grace.

Inherent Vice: The Design Flaw

In the world of museum conservation, we deal with ‘inherent vice.’ It’s a term for an object that is destined to destroy itself because of the way it was made. Low-quality paper turns acidic and eats itself; early plastics off-gas and crumble into vinegar-scented dust.

Corporate culture, however, is allergic to the concept of inherent vice. It prefers the recurring pain of fifty-one small failures over the one-time, agonizing expense of a strategic correction. We would rather spend $1,001 in engineering hours every week to patch a leaking pipe than spend $41,001 once to replace the entire plumbing system. The post-mortem meeting is the mechanism we use to justify this insanity. In today’s session, the manager is very carefully steering the conversation away from the fact that our core database architecture is a decade old and held together by the digital equivalent of duct tape. Instead, he is focusing on ‘improving visibility.’

Visibility is the great lie of the modern incident report.

If I tell you that my house is on fire, and you tell me that the solution is to install a higher-resolution camera so we can watch the flames in 4K, you haven’t solved the problem. You’ve just made the failure more cinematic. We focus on monitoring because monitoring is an ‘action item’ that doesn’t require us to tell the Board of Directors that we need to stop all feature work for a quarter to rebuild the foundation. Monitoring is safe. Monitoring is a line item that fits into the existing budget without triggering a performance review for the person who approved the original, flawed design.

Desire Lines: The Honest Data

I remember an exhibit we ran about the history of urban planning… a desire line is actually the most honest piece of data you can find. It tells you where the system is failing to meet the human need. Our recurring outages are the desire lines of our infrastructure. They are telling us exactly where the system is broken, yet we keep trying to pave the old sidewalks and wondering why people-and data-keep cutting through the mud.

We use the word ‘blameless’ to protect people, which is noble, but we’ve weaponized it to protect the status quo. If no one is to blame, then no one is responsible for the fix. If the system is at fault, but the system is an abstract entity that no one is allowed to dismantle, we are just historians of our own inevitable decline.

True accountability isn’t about finding a scapegoat to fire; it’s about finding the courage to admit that the initial premise was wrong. It’s about stopping the ritual.

I’ve seen this work in rare pockets of the industry where the goal isn’t just to ‘stay up,’ but to be fundamentally robust. Companies that use Email Delivery Pro understand this distinction intuitively-they realize that certain foundational decisions, like how you handle the critical infrastructure of communication, aren’t things you can just ‘monitor’ your way out of if you get them wrong at the start. You have to choose a path that isn’t built on inherent vice. You have to decide that you’re tired of the seance and ready for a solution.

The Toxic Glue: Strategy vs. Tweak

During the meeting, I tried to bring up the museum metaphor… The manager nodded, typed ‘Consider alternative glue’ into the document, and then immediately moved on to discussing the dashboard colors. He is the priest of the Status Quo, and his job is to ensure the liturgy is followed so that the gods of the Quarterly Report remain appeased.

Theatrical Penance

We are currently at the part of the meeting where we assign ‘owners’ to the action items. This is the most theatrical part of the process. We all know that the ‘owners’ won’t be given any extra time to complete these tasks. They will be expected to do them alongside their regular 41 hours of weekly work.

By next month, these tickets will be buried under a mountain of new features, only to be resurrected during the next ‘incident review’ where we will express shock that they weren’t completed.

The Real Post-Mortem

I wonder what a real post-mortem would look like. It wouldn’t be a document. It would be a mirror… As a museum coordinator, I spend my life trying to preserve the past, but in tech, we seem obsessed with preserving our mistakes. We curate our failures, tagging them and filing them away in digital archives, making sure they are well-lit and easy to browse, but never actually removing them from the gallery.

I closed the Google Doc at 3:11 AM. The kraken and the wombat were still there, lingering in the ‘Conclusion’ section. I didn’t say goodbye. I just shut my laptop and sat in the dark, thinking about the 1921 film reels. They smelled like vinegar right before they disappeared.

We call it a post-mortem because it sounds professional, but a post-mortem is supposed to tell you how the patient died so you can save the next one. If you keep performing an autopsy on the same body every six months, you’re not a doctor. You’re just someone who likes looking at ghosts. What would happen if we just stopped? We might actually learn something, but that would mean the ritual is over, and I don’t think any of us are ready for the silence that follows.