Who This Article Is For
- Owners facing repeated mistakes or problems
- Managers treating small complaints as potential major risks
- Business owners building a culture that reduces failures
Use Heinrich’s Law to Learn From Near Misses Before Losses Grow
Understand the 1-to-29-to-300 idea behind Heinrich’s law, then build simple reporting and improvement habits that address causes behind small mistakes.
Published
Report Small Irregularities and Address Causes Before Incidents Grow
Many serious incidents follow smaller irregularities that were repeatedly overlooked.
Heinrich’s law describes one major accident behind which lie 29 minor accidents and 300 near misses. Its practical emphasis is the shared causes that can underlie small irregularities and serious incidents.
Miscommunication, incomplete checks, missing information, and vague procedures can create larger losses when left unresolved. Build a way to notice everyday concerns before reacting only after a major event.
What Heinrich’s Law Means
This rule of thumb describes one major accident, 29 minor accidents, and 300 near misses. It became known through analysis of workplace accidents and is also used as a perspective in operational risk management.
Use it to investigate smaller signs, beyond focusing on an exact ratio. Large failures can be the visible part of a broader accumulation.
Before a data leak, for example, there may have been almost-misdirected messages, incorrect permissions, or weak password practices. Treating the final incident as exceptional can hide those causes.
Signals Before a Major Incident
Early signs can be overlooked or dismissed.
| Type | Example | Potential risk if ignored |
|---|---|---|
| Near miss | Catching a message before sending it to the wrong person | Information leakage |
| Minor incident | Incorrect guidance given to a customer | Loss of a major customer |
| Operational irregularity | Only one person understands a task | Operational stoppage |
| Small complaint | Repeated dissatisfaction with delayed delivery | Loss of trust |
An unresolved cause can recur at a different scale. Avoid closing the review with a finding of individual carelessness alone; examine organizational conditions.
Near Misses Offer a Chance to Prevent Serious Incidents
Everyday reporting can provide a frontline opportunity for improvement.
Small Signs Reveal Underlying Causes
Vague procedures, person-dependent checks, complex communication routes, and limited training can first appear as minor concerns.
Addressing them early can reduce exposure. Dismissing the event as a small mistake leaves the cause in place.
More Reports Can Mean Better Visibility
A rising number of reports may feel worrying, but it can indicate that people are noticing and sharing risks.
Silence may conceal problems. More reporting can show increased organizational awareness rather than simply a worsening situation.
Early Corrections Limit Losses
Fixing a near miss generally requires less than responding after a serious incident. Customer departures, reputational damage, compensation, and recruitment difficulties can be hard to reverse.
Early correction offers a practical way to limit those costs.
Warning Signs in a Team That Does Not Report
Reports are useful only when people can raise them.
Blame Comes First
Immediately pursuing who made the mistake encourages self-protection and silence.
Identify causes. Focusing only on individual responsibility allows the same problem to appear through someone else.
Only the Outcome Matters
“No accident occurred” can obscure an unresolved weakness.
If a misdirected message was caught just in time, examine why it nearly happened. The lucky outcome alone is insufficient reassurance.
Reporting Requires Too Much Work
Long forms, many approvals, and complicated formats discourage busy staff.
Make reports short, quick to submit, and safe from blame. Without these conditions, the process is unlikely to become routine.
Three Ways to Turn Small Mistakes Into Shared Learning
Build a working system alongside encouraging awareness.
Lower the Reporting Barrier
A short form covering time, content, and observations can be enough. Anonymous reporting can also provide an entry point.
A regular opportunity for verbal sharing helps too. Even five minutes each week can develop awareness over time.
Examine Conditions Beyond the Individual
Review procedures, training, responsibilities, checking methods, and information sharing.
Repeated mistakes indicate a need to examine the system instead of stopping at a request to be more careful.
See using KPT for practical improvement for turning reflection into a specific next trial without centering the discussion on blame.
Share the Resulting Improvements
Show what changed because someone reported a concern.
Examples include:
- Adding a check against misdirected messages
- Updating a customer-response template
- Documenting work that depended on one person
Visible benefits show that reporting helps, strengthening the reporting culture.
SpreadSite is a no-code website builder that lets you create, publish, and update a website from Google Sheets using ready-made templates.
To keep shared business information current through a website managed from a spreadsheet, give SpreadSite a try!
Build a website with SpreadSite →
About the Author
Thank you for reading!
I develop and operate SpreadSite, a service for creating websites from spreadsheets.
It helps people with limited time and money communicate what makes their work appealing. Consider it if you need a website! SpreadSite
Frequently Asked Questions
Q: Does every company follow the exact ratio?
A: No. The practical idea is that many smaller irregularities can sit behind a serious incident, rather than a universal numerical ratio.
Q: Is it relevant outside manufacturing?
A: Yes. Sales, administration, service, information management, and customer support can all contain small signs of larger risks.
Q: Will near-miss reporting make the workplace negative?
A: Treating reports as accusations can do that. Treating them as improvement material makes reporting constructive.
Q: Can a small company build this system?
A: Yes. A shared spreadsheet, simple form, or regular verbal discussion can work. Consistency matters more than scale.
