Why We Default to Blame (and Why That Makes Sense)

This week, our son started outside school hours care for the first time.

Because he takes medication, I had to complete a medication administration form. As I was filling it in, I noticed something small—but important. At the bottom of the form was a document control footer. The review date was early September 2024.

It was out of date.

So I circled the date, completed the form, and the next morning handed it to the staff member at drop-off. I said, calmly and politely, that they might want to check whether there was a newer version, given the nature of the form.

What happened next was immediate—and familiar.

Her posture changed. Her tone shifted. She became defensive.

She told me this was the correct form. I said I understood that, but it was clearly out of date, and that could matter when we’re talking about medication. She replied that it would have to go “up to the higher ups.”

But the reaction wasn’t about the form.

It was about what she foresaw.

Before I had said anything about blame—before anyone had mentioned fault—she had already imagined the outcome: I’m going to get in trouble. And that reaction made complete sense.

Because many of us have learned, through experience, that when something is wrong, someone will be held responsible. Even if the issue lives in systems, processes, document control, or governance. Even if the person standing in front of you had no ability to change any of it.

So people defend themselves early. Not because they are difficult. Not because they don’t care. But because they are trying to protect themselves.

I could see she was carrying this personally, so I paused and said something like:

“I work in health and safety. I know this isn’t your fault. Somewhere in the organisation there’s a gap in systems or processes—but this is the form you’ve been given to use. You’re not responsible for that.”

I also said I was more than happy to raise it myself if she was worried it might come back on her.

That was the moment her face changed. Her shoulders dropped. Her tone softened. She relaxed.

Later, when I picked up my son, her entire demeanour towards me was different—warmer, kinder, more open.

Nothing about the form had changed yet.

But the threat of blame had been removed.

And that’s the part I keep thinking about.

We often say, “People shouldn’t get defensive.”Or, “If you haven’t done anything wrong, you shouldn’t worry.” But that ignores how organisations actually work.

People don’t become defensive because they are fragile. They become defensive because they have learned—often the hard way—that mistakes are personalised, even when they are systemic. They don’t wait to see whether blame will come. They anticipate it. They prepare for it. They armour up.

This isn’t irrational behaviour.It is locally rational behaviour.

It is a perfectly sensible response in environments where:

• errors are individualised,

• learning is secondary to accountability,

• and being associated with a problem carries personal risk.

Traditional safety thinking often asks, “Who made the mistake?” A more modernised view on safety asks, “How does it make sense that people expect blame?”

That small interaction at OSHC wasn’t about an out-of-date form.

It was about conditioning.

When we want people to speak up, raise issues, or point out gaps, we have to remember this: people aren’t responding to the issue in front of them—they’re responding to what they believe will happen next.

If the organisation has a history of blame, people will act accordingly.

And if we want different behaviour—more openness, more learning, more trust—then the response to small issues matters just as much as the response to big ones.

Because long before blame is spoken, it is often already felt.

What have people in your organisation learned about blame, long before you ever say a word?