Every time a major accident or organizational failure makes the news, the same postmortem observation follows: there were warning signs, and plenty of them. As safety and risk management increasingly fall under executive accountability, companies are rebuilding the systems that track small, easy-to-dismiss signals. This piece explains what the 1:29:300 ratio behind Heinrich's Law actually means in practice, and what an organization needs in place to catch minor accidents and small warning signs early. The conclusion is simple: major accidents never come out of nowhere. They are always preceded by small signals, repeated.
What Does the 1:29:300 Ratio Actually Mean?
What matters about Heinrich's Law isn't the precision of the ratio but the sequence and the repetition it describes. Before one major accident occurs, there are 29 minor accidents, and before those, a far larger number — 300 — small warning signals. Mapped out, the path from signal to disaster looks like this.
What this path tells us is that the organization had at least 329 chances to intervene before disaster struck. Looked at in isolation, a single major accident looks like bad luck or one person's mistake. But seen against the 300 signals that preceded it, the accident looks like an outcome anyone could have predicted. Applying Heinrich's Law in practice doesn't mean racing to stop the one big accident — it means building an organization that can actually see the 300 small signals.
Why Organizations Miss the 300 Warning Signs
Individually, small signals never look worth reporting. It's the same thing that always happens, nothing came of it last time, and filing a report just creates extra work. So the 300 signals live only in the memory of whoever was on the floor that day — they never make it into a report. Even the 29 minor accidents tend to get closed out after the fact, with no one tracking how many times the same type of incident has occurred.
This is the trap executives fall into: a report is already filtered information, and the 300 signals get filtered out along the way. The place to learn is the floor, not the conference room. No summary read in a meeting will ever surface the bottom 300 of Heinrich's pyramid. Leaders have to stand on the floor themselves and see, firsthand, the annoyances staff shrug off, the workarounds that keep getting repeated, and the small problems that keep showing up in the exact same spot.
How to Build a System That Catches Small Signals Early
The first step is lowering the bar for what gets logged. Don't wait for an actual accident — capture the near-misses too, the moments that caused no damage but felt off. The form can be one line: when, where, and what was different from usual. Set the bar too high and you'll only ever capture the 29. Only a low bar surfaces the 300.
Next, count repetitions. What matters in Heinrich's Law isn't that a signal exists but that it recurs. Track how many times a similar signal has shown up in the same location, the same process, the same area of responsibility. Anything that has repeated three or more times should be treated as a structural problem and investigated separately.
Executive floor visits need to be locked into the calendar, on a fixed cadence. Visits scheduled around whenever there's spare time never last. The 300 signals that never make it into a report can only be heard on the floor.
Who Should Lead Signal Management?
Plenty of organizations build the system and still fail. The reason is almost always the same: whoever is leading signal management — the "champion" — isn't driving the schedule, but being dragged along by it. Accident prevention never looks urgent day to day. Sales meetings, deadlines, and customer issues always jump the queue, and signal reviews get pushed to next week. Once that pattern starts, the effort fails 100% of the time.
For the champion to drive the schedule means setting the review cadence themselves, putting it ahead of other commitments, and treating any slippage as a problem in its own right, not a footnote. The champion doesn't have to be an executive, but they need both the authority to hold the schedule and the responsibility to personally review the 300 logged signals.
Four Things to Check Right Now
To apply Heinrich's Law inside your own organization, check the following.
1. Is there a place to log small signals, not just accidents? If not, start with a one-line form. 2. Are you counting how many times the same signal has repeated? Three or more means it's a structural problem. 3. When did leadership last set foot on the floor? Set a cadence and lock it into the calendar. 4. Who is the champion for signal management, and are they driving the schedule — or being dragged by it?
If two or more of those four boxes are empty, your organization is likely sitting right in the middle of its own 300 — and simply not seeing it.
