The “Blameless Post-Mortem” slide is projected on the far wall, glowing with the sterile optimism of a corporate brochure. It’s a beautiful lie. We all know what we’re here for. We aren’t here to find the “why”; we are here to find the “who.”
I’m sitting next to a guy named Marcus who keeps clicking his pen-44 times a minute, if I had to guess. I’m a researcher of crowd behavior, so I count these things. It’s a nervous tic. People in a room where a failure is being dissected act exactly like a herd of gazelles sensing a predator. They don’t all need to outrun the lion; they just need to outrun the slowest one among them. The air in the room is stale, heavy with the scent of overpriced coffee and the collective breath of 24 anxious adults trying to look indispensable.
The project lead, Sarah, clears her throat. She’s been rehearsing this for at least 14 hours. “While this was a team effort,” she begins, “the critical path was blocked during the 14th week of production due to… inconsistencies in the database migration.” She pauses. She doesn’t look at Janet, who is sitting 4 seats down from me. But everyone else does. It’s a coordinated, involuntary shift of 24 pairs of eyeballs.
[Insight: The collective gaze functions as the first, non-verbal allocation of blame.]
The Performance of Belonging
I remember a joke someone made earlier in the hallway about “SQL injection therapy.” I laughed and nodded, pretending to get it, because that’s what you do to stay part of the herd. In reality, I have no idea why that’s funny. It’s a litmus test for belonging. If you laugh, you’re safe. If you don’t, you might be the “inconsistency” Sarah is talking about. It’s a performance. We are all actors in a play where the ending is already written in a 144-page internal memo that no one has read but everyone has sensed.
The Corporate Math of Blame
High executive effort, admitting flaw.
Low effort, preserves management.
Companies love the word “culture.” They use it like a spice to cover the taste of burnt management. Learning is expensive. It’s much cheaper to decide that Janet simply messed up a 104-line script.
The Primal Relief
Sarah talks about “process friction” and “communication silos.” These are the ghosts we conjure to avoid talking about the living. We use technical precision to mask emotional cowardice. I’ve noticed that the length of the post-mortem report is usually inversely proportional to the amount of actual learning that happens. A 164-page document is usually just a very long way of saying “Not my fault.”
Complexity Hides Simplicity
(Systemic Design Flaw)
(Blaming the Janitor)
They wanted 44 pages of data on floor wax and shoe-sole friction to hide the simple truth: they bought the wrong signs.
The Paradox of Closure
The truth is, we don’t want to learn. Learning is painful. Learning requires change. What we want is closure. Closure is the feeling you get when you’ve identified a villain. The post-mortem provides that villain. It’s a political diagnostic tool. It’s used to prune the garden.
Systemic Issue Resolution
73% IDENTIFIED, 0% SOLVED
If we actually addressed the systemic issues-the impossible deadlines, the lack of resources, the toxic pressure-we’d have to admit that the entire 44th floor is part of the problem. And nobody on the 44th floor is going to sign off on a report that says they are the problem.
The Scapegoat Cycle
Janet has been the scapegoat 4 times in 14 months. The company keeps her because she’s competent enough to blame but not powerful enough to escape. It’s a symbiotic relationship based on mutual resentment.
Complicity in Observation
I catch myself tapping my own pen. 1, 2, 3… no, I have to stop. I don’t want to be the one making the noise. I want to be invisible. I laughed at the joke I didn’t understand. I am complicit in the ritual. We pretend to be scientists dissecting a failure, but we are actually just priests performing a sacrifice to appease the gods of the quarterly earnings report.
The Beautiful Paradox
If you take away the ability to blame an individual, you force the collective to take responsibility. And responsibility is the one thing corporate culture is designed to avoid. We create these 14-step processes specifically so that no one person is ever truly responsible, yet we still need a single person to point at when it all goes wrong.
Sarah is wrapping up. “We’ve identified 14 key action items to ensure this doesn’t happen again.” I look at the list. Item number 4 is “Better communication.” Item number 14 is “Increased accountability.” They are meaningless. They are the same items from the post-mortem 4 months ago.
The Aftermath
As we stand up to leave, the tension evaporates. The predator has fed, and the rest of the gazelles are safe for another day. I walk past Janet. I want to say something, but I don’t. I just nod, a small, cowardly gesture of solidarity. She’s already thinking about the next script she has to write, the next 104 lines of code that will eventually be used as evidence against her.
I laugh when the VP of Sales says something about “circling the wagons.” I’m documenting the eye contact, the pen clicking, and the hum of the light. In the end, I’ll probably blame the green exit signs again. It keeps the herd moving. But I wonder how many more sacrifices we can make before there’s no one left in the room to turn on the lights. I’ll document the logistics, the way niche shipping for something as mundane as an Auspost Vape delivery involves too many layers of regulation, leading to the absurdity of blaming the final counter worker.
The cost of maintaining the hierarchy always outweighs the value of actual learning.
