The fluorescent light hums at 63 hertz, a frequency that usually signals a dying ballast, but today it just feels like a headache boring into the base of my skull. I am sitting across from a project manager who is currently vibrating with the kind of performative empathy that usually precedes a firing. On the table between us lies a loaf of rye bread I bought 3 hours ago. I took exactly one bite before noticing the constellation of grey-green mold blooming across the crust. The taste is still there-a metallic, fuzzy bitterness that coats the back of my tongue. It is the exact same flavor as this meeting.
We are here for a ‘blameless post-mortem.’ That is the official title on the calendar invite sent to 23 people. We are supposed to be using the Five Whys technique to uncover why the production database decided to commit ritual suicide at 3:13 in the morning. But as I look around the room, I realize no one is looking for a root cause. They are looking for a neck. They are looking for the specific person whose throat they can fit their hands around so they can feel safe again.
Logan M.K. is sitting in the corner, clutching a portable Zoom recorder and a shotgun microphone covered in a deadcat windscreen. Logan is a foley artist, a man who spends his days snapping celery to simulate breaking bones and dropping heavy leather bags to mimic the sound of a body hitting the pavement. I invited him here because I wanted someone to record the sound of a corporate lie. I wanted to see what the ‘Five Whys’ sounds like when it is being used as a weapon rather than a tool.
Logan leans in, adjusting his levels. He whispers to me that the room sounds ‘thin.’ There is no acoustic depth when people are holding their breath. In a blame culture, silence has a very specific texture-it is heavy, damp, and smells vaguely of ozone.
The Descent: Five Whys Becomes Five Whos
“Why did the server go down?” the facilitator asks. This is Why Number 1.
“Because the storage volume reached 103 percent capacity,” the lead engineer says, staring intently at a coffee stain on the table.
“Why did the storage volume reach capacity?” “Because the log rotation script failed to execute.”
I think about that moldy bread. You can’t just scrape the green part off and pretend the rest of the loaf is fine. The mycelium has already threaded its way through the entire structure. If your culture is built on the fear of being the ‘one’ who broke the build, every analytical tool you introduce will eventually be used for surveillance. You can’t fix a systemic rot with a checklist. It is like trying to cure a fever by breaking the thermometer.
Logan M.K. once told me that the hardest sound to record is a ‘natural’ footstep. When people know they are being recorded, they change their gait. They become self-conscious. They stomp or they tiptoe. The same thing happens in these meetings. When engineers know that the ‘root cause’ will eventually be tied to a performance review or a 13-minute dressing down from a VP, they stop providing data. They start providing excuses. They build elaborate narratives where the failure was an act of God or a bizarre edge case that no human could have predicted.
Process is a mirror, but most organizations are too terrified to look at the reflection.
The Original Sin: Pinpointing Human Error
We hit Why Number 3: “Why did the log rotation script fail?”
“Because the permissions were changed during the last deployment,” the engineer replies. His voice is flat. He knows what’s coming. The room shifts. The air pressure seems to drop by 3 millibars. The facilitator’s eyes light up. We’ve found the ‘human error.’ In the theology of the blame culture, human error is the original sin. If we can find the human, we don’t have to fix the system. We just have to ‘retrain’ the human, or better yet, remove them.
Cost Analysis: Blame vs. Resilience
Replace component/person
Fix infrastructure/process
But human error is never the root cause. It is the starting point for a real investigation. Why was it possible for a single person to change permissions without a secondary check? Why did the monitoring system wait 43 minutes to alert the on-call engineer? Why are we running scripts that require manual permission sets in an automated pipeline? These are the questions that lead to resilience. But they are also the questions that cost money and require management to admit that they’ve underfunded the infrastructure for the last 53 months.
It is much cheaper to blame the engineer.
The Technician’s Truth:
This reminds me of a conversation I had with a technician regarding climate control systems. When a unit fails, the instinct is to blame the compressor. But often, the compressor died because the unit was sized incorrectly for the room, or the layout forced it to work at 93 percent capacity for three years straight. If you just replace the compressor without looking at the load calculation, you’re just waiting for the next explosion. This level of honesty is what defines companies like minisplitsforless, where the focus is on the precision of the initial setup-the sizing, the layout, the physics of the space-rather than waiting for a failure to start pointing fingers. They understand that success is a byproduct of the right environment, not just the absence of a visible mistake.
Why Number 4: The Designated Sacrifice
In our meeting, the facilitator is now stuck on Why Number 4: “Why were the permissions changed?” He is looking directly at a junior developer named Sarah. Sarah is 23 years old and has been with the company for 3 weeks. She looks like she’s about to cry. Logan M.K. is capturing the sound of her shivering. It’s a rhythmic, high-frequency rattle of a person who realizes they are the designated sacrifice.
“Iā¦ I followed the documentation,” Sarah whispers.
I go back to my desk and look at the moldy bread again. I realize that I’m the one who failed here. I saw the mold, but I was so hungry I tried to eat it anyway. I saw the culture, but I thought I could use a ‘blameless’ tool to fix it. But tools are agnostic; they take on the properties of the hands that hold them. In a hand that wants to heal, the Five Whys is a scalpel. In a hand that wants to hide, it’s a silencer.
The Sound of Egos Grinding
Logan M.K. packs up his gear. He looks at me and shakes his head. “The audio is useless,” he says. “There’s too much background noise.”
“What noise?” I ask. “It was practically silent in there.”
“Not that kind of noise,” Logan says. “The sound of everyone’s ego grinding against their fear. It’s a 103-decibel screech that drowns out the truth every single time. You can’t record the truth when everyone is auditioning for the role of ‘Not Guilty.'”
A process without trust is just a sophisticated way to lie to ourselves.
If we actually wanted to fix the problem, we would have started with Why Number Zero: Why are we more afraid of each other than we are of the system failing? But that question doesn’t fit on a spreadsheet. It doesn’t have a neat ‘remediation step’ that can be checked off by Friday at 3:33 PM.
The Final Surrender
I throw the bread in the trash. The plastic bag makes a crinkling sound that Logan M.K. would probably describe as ‘the sound of a thousand small surrenders.’ I think about the next post-mortem, and the one after that. I think about the 73 different ways we will use logic to justify our cowardice.
I leave the office and walk past the server room. The rack lights are blinking in a steady, 3-beat rhythm. Green, green, red. Green, green, red. It looks like a heartbeat. Or a warning. Probably both. I realize I’m still holding the receipt for the bread. It cost me $6.03. A small price to pay for a reminder that you can’t build something healthy on a foundation of decay. If the first ‘Why’ doesn’t start with a look in the mirror, the next four don’t matter at all.
