The HVAC system in conference room 6 was humming with a low-frequency vibration that I could feel in the soles of my shoes. It was a 56-hertz drone, the kind of sound that slowly erodes your ability to remain civil. I sat there, shifting my weight in a chair that had been designed by someone who clearly hated the human spine, watching Marcus stand at the whiteboard.

He had a marker in his hand and a look of practiced empathy on his face. “I want to be clear before we start,” he said, his voice dropping into that low, serious register people use when they’re about to do something terrible. “We are not here to point fingers. This is a blameless post-mortem. We are here to look at the process and learn how Project Aegis went sideways so spectacularly.”

He then spent the next 46 minutes doing exactly the opposite. He didn’t point with his finger; he pointed with his timeline. He pointed with his questions. He pointed with the way he lingered on a specific timestamp-10:16 PM-when Dave, a senior dev who looked like he hadn’t slept since the previous fiscal year, had pushed the final commit. Marcus wasn’t looking for a systemic failure. He was looking for a narrative that had a protagonist he could sacrifice to the gods of the quarterly report. I’ve seen this ritual 126 times in 26 different companies, and it never gets less exhausting.

I tried to interject at the 26-minute mark… I asked Marcus if the system had any safeguards to prevent a 10:16 PM commit from going live without a peer review. Marcus blinked at me… He told me that the peer review process was ‘clearly outlined’ in the 156-page internal handbook.

[The ritual of the blameless post-mortem is often just a sophisticated way to gaslight the workforce into believing that systemic flaws are personal character defects.]

It’s a hard truth to swallow because it requires the people at the top to admit they built a fragile world. It’s much easier to say Dave was careless. I looked around the room. There were 16 people present, and 6 of them were actively checking their phones under the table. They weren’t being rude; they were surviving. They knew that whatever ‘learnings’ Marcus wrote on that board wouldn’t change the fact that they’d be back in this same room in another 6 months, dissecting another corpse.

The Wider System: From Code to Consumer

The failure wasn’t the commit. The failure was a culture that prioritized the appearance of accountability over the reality of resilience. We build these complex, interlocking grids of responsibility and then act shocked when a single point of failure-a human being with a mortgage and a flickering internet connection-causes the whole thing to tilt.

Consumer Friction Points (Example Data)

We are constantly blamed for not being ‘smart’ enough to navigate systems that are intentionally designed to be opaque. If you spend $676 on a flight and find out later that the person sitting next to you paid $186, the industry tells you it’s your fault for not knowing the secret handshake of booking on a Tuesday during a lunar eclipse.

It’s why I’ve started appreciating tools that actually take the burden off the individual. Instead of blaming a user for not being a professional bargain hunter, a well-designed system like LMK.today assumes the user has better things to do with their life than manually track every price fluctuation on a registry. That is the essence of good ergonomics: reducing the cognitive load so the human can actually exist without constant friction.

Back in the meeting, Marcus was now asking Dave why he didn’t ‘sound the alarm’ when he saw the error logs. Dave looked up, and for a second, I thought he was going to scream. Instead, he just said, “There were 1236 logs in the span of 6 minutes, Marcus. Everything was an alarm. When everything is an alarm, nothing is an alarm.” That is the most profound thing I’ve heard in 66 days of consulting. It is the definition of alarm fatigue.

The Decorated Wall of Red

The Path to Resilience

I think about my neighbor again. He wasn’t a bad guy, he just couldn’t read the systemic cues I was sending… I am as much a victim of my own bad internal programming as Dave was of the Aegis deployment script. We are all just meat-based processors trying to run complex software on legacy hardware.

By the end of the meeting, Marcus had a list of 6 ‘action items.’ None of them involved changing the deployment pipeline. None of them involved reducing the 156-page handbook to a 6-step checklist. Every single one of them was a variation of ‘be more careful.’ It was a masterclass in futility.

[True accountability is the act of looking at a disaster and asking, ‘How did we make it so easy for this to happen?’ rather than ‘Who made this happen?’]

As the room cleared out, Dave stayed behind for a moment, staring at the whiteboard. I walked over and adjusted his monitor. It was too low, forcing him to hunch forward in a way that compressed his diaphragm.

“Raise your screen by about 6 inches,” I told him. “It won’t fix the culture, but it’ll stop the headaches.”

He looked at me with a weary sort of gratitude. He knew, and I knew, that the headaches weren’t coming from his neck. They were coming from the 206-employee weight of a company that preferred a scapegoat to a solution.

I walked out of the building and into the cool evening air, feeling the 66-degree breeze on my face. I had 46 unread messages on my phone, but I didn’t check them. I wasn’t going to be the human element in a failing system for the rest of the night. I went to my car, sat in the driver’s seat-which is, incidentally, one of the few pieces of furniture I own that actually fits my frame-and just sat there in the silence. No alarms. No logs. No Marcus. Just the quiet realization that until we stop blaming the people and start fixing the pipes, we’re all just waiting for the next leak.