If you dispose of explosives for a living, they give you a bomb suit.
If you weld, you get a helmet, gloves, protective clothing, ventilation, and procedures designed around the fact that sometimes sparks go somewhere you didn't expect them to go.
If you work construction, you wear a hard hat.
The interesting thing about all of this equipment is that it isn't an admission that the worker is bad at their job.
Quite the opposite.
We give skilled people safety equipment because we understand something fundamental about work: sometimes things go wrong.
Materials have defects. Equipment fails. Conditions change. Someone makes a mistake. Something nobody predicted happens anyway.
The purpose of safety equipment isn't to make failure impossible.
It's to make failure survivable.
Then you walk into an office.
And the safety equipment disappears.
When something goes wrong, the person becomes the safety equipment
Imagine you're responsible for a project.
You gather the requirements. You coordinate the teams. You make decisions based on the information available. You communicate the risks you know about. You work through dozens or hundreds of small uncertainties.
And then something goes sideways.
Maybe a dependency you were told was solid wasn't solid.
Maybe another team misunderstood something.
Maybe the customer changed direction.
Maybe the data was wrong.
Maybe someone made a perfectly ordinary human mistake.
Maybe you made the mistake.
Maybe nobody made a mistake at all and reality simply turned out to be more complicated than the plan.
Now watch what happens.
Everyone starts putting on their own invisible protective gear.
"I told them about that."
"That wasn't our team's responsibility."
"We assumed they were handling it."
"That decision came from product."
"Engineering wasn't involved early enough."
"Leadership was very clear about the deadline."
"The project owner should have caught that."
And eventually all of that organizational energy has to go somewhere.
Usually it lands on the person closest to the work.
Congratulations.
You are the blast shield.
We confuse accountability with blame
Accountability matters.
If I make a bad decision, I should be willing to examine it. If I miss something, I should learn from it. If I'm responsible for an outcome, I shouldn't disappear when things become uncomfortable.
But accountability and blame are not the same thing.
Accountability asks:
What happened? Why did it happen? What should we change so this is less likely to happen again?
Blame asks:
Whose fault was it?
Those questions produce radically different organizations.
One produces better systems.
The other produces better politicians.
And when people learn that every failure will become a search for someone to blame, they adapt.
They document everything defensively.
They avoid risky decisions.
They escalate things they could easily resolve themselves.
They invite twelve people to meetings so nobody can later say they weren't informed.
They add approvals.
They send emails whose real purpose isn't communication but evidence preservation.
They stop experimenting.
Most importantly, they stop being honest about uncertainty.
Because uncertainty is dangerous when the organization expects someone to pay for every unexpected outcome.
Where is the office-worker equivalent of a hard hat?
A good organization should have safety equipment too.
Not literal equipment.
Organizational equipment.
Clear decision logs.
Explicit assumptions.
Reasonable escalation paths.
Leaders who absorb some of the impact when their teams take responsible risks.
Postmortems that examine systems instead of prosecuting individuals.
Project structures where responsibility is shared honestly instead of concentrated conveniently.
Processes that distinguish negligence from uncertainty.
Enough psychological safety for someone to say, "I don't know," before it becomes much more expensive to admit later.
And perhaps most importantly: managers who understand that part of their job is to provide cover.
That's an underrated responsibility of leadership.
If you're the manager, you should not simply stand farther away from the explosion.
Sometimes your job is to be the protective equipment.
To say:
"We made this decision together."
"The information we had at the time supported that choice."
"There were warning signs we missed as an organization."
"We're going to understand what happened and fix the system."
That doesn't mean nobody is ever responsible for anything.
There are careless decisions. There is negligence. There are people who repeatedly make the same mistakes and refuse to learn from them.
But those are exceptions.
Most failures at work are considerably messier.
They are combinations of incomplete information, incentives, communication failures, rushed timelines, organizational boundaries, hidden assumptions, competing priorities, and ordinary human imperfection.
Yet we routinely compress all of that complexity into:
"Who owned the project?"
The safest organizations can probably make more mistakes
That might sound like a criticism.
I mean it as a compliment.
An organization where people can survive mistakes can attempt harder things.
People can experiment.
They can move faster.
They can make decisions without routing every choice through five layers of approval.
They can tell leadership bad news while there is still time to do something about it.
They can try things that might not work.
They can say, "I screwed this up," without wondering whether they just volunteered to eat the entire shit sandwich themselves.
That organization will still make mistakes.
Probably lots of them.
But it will learn.
The dangerous organization isn't necessarily the one where people make the most mistakes.
It might be the one where everyone has learned that the safest strategy is making sure the mistake belongs to somebody else.
Give people some protection
We accept that firefighters need protective clothing because fire is unpredictable.
We accept that welders need helmets because sparks are part of welding.
We accept that people handling explosives need armor because even experts cannot reduce risk to zero.
Maybe knowledge work deserves the same basic assumption.
Not that every failure is acceptable.
Not that responsibility doesn't matter.
Just that doing complicated work means eventually encountering something you didn't anticipate.
And when that happens, the organization shouldn't immediately start looking for the nearest human being to use as protective equipment.
People should be accountable.
They should learn.
They should improve.
But they should also have some protection.
Because if the only safety mechanism your organization has is figuring out who gets blamed when something explodes, you don't really have a safety system.
You just have a blast radius.