After Michael's accident, I sat down with a blank sheet of paper.

Not to write a report. Not yet. First, I needed to see the truth.

I drew a simple line across the middle of the page. At the right end: Michael's fall. At the left end: everything that was supposed to prevent it.

Then I started mapping the defenses that failed:

  1. Physical barrier: Anchor points inadequate—known for 18 months
  2. Procedural barrier: Risk assessment didn't match reality—never updated after site modification
  3. Administrative barrier: Budget approval process—£1,200 modification stuck in queue
  4. Supervision barrier: No verification that the job could be done safely—production pressure overrode safety concerns
  5. Training barrier: Workers taught to clip on—but not what to do when the system made that impossible

Five barriers. All failed. Not because five people made mistakes, but because the system had five holes—and they lined up.

This is one of the tools I use in investigation: Barrier Analysis.

Not fancy software. Not complicated diagrams. Just a clear map of what was supposed to protect someone, and where each protection broke down.

Because here's what I've learned across 500+ investigations: accidents don't happen because one thing goes wrong. They happen when multiple defenses fail simultaneously—and that only happens when the system allows it.

The mobile phone ban from post three? That's adding one barrier while ignoring the five that were already broken.

The five-minute investigation from post two? That's stopping at the first failed barrier and missing the systematic failures behind it.

Real investigation maps all the barriers. Then asks why each one failed. Then fixes the system, not just the person.

When I showed the plant manager Michael's barrier map, something changed in his expression. This wasn't about blame anymore. It was about the decisions he had control over. The budget approval. The risk assessment process. The gap between procedure and reality.

"We could have prevented this," he said quietly.

Yes. And that's the only truth that matters.

Because somewhere in your organisation right now, barriers are failing. Budget requests are pending. Procedures don't match practice. Workers are adapting to broken systems.

The question is: will you map those failures before or after you learn someone's name?

This series started with a simple premise: investigation is about systems, not blame. If you're serious about finding truth instead of scapegoats, we should talk.

www.industrialaccidentinvestigators.co.uk