The Ritual Begins

The whiteboard was pristine, shimmering under the weak fluorescent lights. Half-a-dozen pens lay scattered next to a stack of sticky notes in five different shades of institutional pastel. We were here, again, for the ritualized cleansing of organizational guilt. They called it a ‘blameless post-mortem,’ which is like calling a trial by combat a friendly disagreement. I was already exhausted, not from the failure itself-which was predictable, given the timeline and resource constraints-but from the performance we were about to stage.

The atmosphere was thick with feigned empathy and professional detachment. Everyone had the script memorized: focus on process, not people. Talk about systems, not decisions. Look forward, never backward-unless ‘backward’ involves finding a sufficiently low-ranking individual whose mistake can be narratively isolated.

We spent the first hour diligently placing notes: “Inadequate monitoring,” “Insufficient testing environment,” “Communication silo.” Standard, sterile fare. Jeremy, moving with the solemnity of a priest administering last rites, built a neat, contained little island of failure centered around the one thing Maya, a new junior engineer, had done that wasn’t strictly according to the 239-page handbook she hadn’t yet been trained on.

Immunity and the Pressure Point

We had systemic risks everywhere. The dependency management was a joke. The deadline itself-pushed forward by exactly 9 days, arbitrarily, because the marketing department wanted to align with a major retail promotion-was the single, undeniable root cause. But you can’t blame Marketing. You certainly can’t blame the CEO who signed off on the revised schedule based on a PowerPoint slide that promised magical acceleration. They are immune. The system must find a place to dump the political toxicity, and the lowest available pressure point is always the easiest target.

I’ve tried the pure, genuinely blameless approach. I remember once trying to run a similar review after a massive platform outage that coincided with a sale event featuring smartphone on instalment plan. The internal report was exhaustive, detailing the nine layers of technical debt and miscommunication. But when the summary reached the executive floor, the question wasn’t, “How do we fix the nine layers?” The question was, “Who signed off on the last pull request before everything crashed?” It’s a trick question, because what they are really asking is, “Who is expendable?”

Optimization for Forgetting

“The first, most powerful mechanism of denial is to point the finger outside. If I can convince myself that the failure was caused by a specific circumstance, a specific person, or a specific anomaly-something external and non-essential-then I don’t have to face the terrifying fact that the core structure, the foundation of my life, or in your case, the core of the company culture, is broken.”

– Aiden R.J., Addiction Recovery Coach

That conversation changed how I look at sticky notes. They aren’t tools for analysis; they are tokens in a political game. When Jeremy finished his arrangement, the board presented a perfect visual narrative: Systemic problems (which were everyone’s fault, thus no one’s fault) led up to the final, isolated action (which was Maya’s fault, thus her fault). The solution, predictably, became ‘more detailed process documentation’ and ‘mandatory training on deployment protocols’-an intervention that costs maybe $979 to implement but allows everyone else to go home feeling morally and professionally clean.

I raised a single point, a small act of defiance. I said, “We need to account for the fact that we continually ask people to operate outside of documented procedure because the velocity demanded is incompatible with adherence to the process we wrote.”

Jeremy smiled thinly, the smile of a predator who has already secured dinner. “That’s a valuable perspective,” he said, scribbling a new sticky note that read: ‘Review velocity vs. compliance trade-offs.’ He stuck it far away from Maya’s deployment notes, on the absolute bottom right corner of the board, destined for the ‘Next Quarter/Maybe Never’ action list. He assimilated the critique without engaging the contradiction. The criticism was neutralized and filed away, the system successfully defending itself against self-reflection.

The Cost of Psychological Safety

The real failure wasn’t the code; it was the fact that for 1299 days, we had rewarded the people who delivered fast regardless of the technical debt, and we had punished, subtly or overtly, those who insisted on rigor. And now, facing the consequences, we were continuing the pattern by sacrificing the lowest-ranking participant on the altar of speed and shareholder optics. The psychological safety in that room wasn’t just damaged; it was utterly destroyed. Everyone present learned exactly what failure costs and how to ensure they are never the one holding the political bomb when it detonates.