Blame is a design choice

After something goes wrong, there is a strong pull toward finding the person who did it. It feels like closure. It is quick, it is satisfying, and it lets everyone else conclude that they would not have made the same mistake.

It also, reliably, sets you up to have the same failure again.

Human and Organizational Performance starts from a different assumption: that people are not the unreliable part to be controlled, but the adaptive part to be learned from. When a capable person makes an error, the interesting question is not who, it is what the conditions were that made the error likely, and what made those conditions look normal at the time.

Blame closes that question. The moment an incident has a name attached, the investigation stops, the conditions stay exactly as they were, and the next capable person walks into the same setup. Worse, everyone watching learns that the cost of reporting a near miss is that you might be the name next time. So the near misses stop being reported, and you lose the early warnings that were your best chance to fix the conditions before they cost you.

This is why I treat blame as a design choice rather than a natural response. An organization decides, in how it runs its reviews and what it does with what it finds, whether failure is treated as fault or as information. That choice shapes whether people tell you the truth about how work actually happens.

None of this means no accountability. It means accountability for the conditions as well as the actions, held by the people who own the system and not only by the person at the sharp end.

The test is simple. After your last incident, did anything about the work actually change, or did only the paperwork? If it was only the paperwork, the design is still choosing blame, whatever the policy says.