When a major incident occurs, like a fatality, a life-changing injury, or significant asset damage, organisations mobilise. Senior leaders get involved, resources are allocated, and the investigation is thorough, detailed, and well-documented.
The assumption is that serious consequences must yield richer learning. After all, more was at risk, so surely there's more to uncover.
What causes major incidents in the workplace?
Major incidents very rarely appear out of nowhere. The conditions that led to a serious outcome were almost certainly present long before it turned catastrophic. They were there when similar tasks resulted in minor injuries, when near misses went unreported, and they were there during normal work, every single day.
The difference between a major incident and a minor one is often nothing more than luck; it was the way someone fell, a vehicle that was passing at that moment or how a load shifted. The systemic issues, the error traps, the performance influencing factors? They don't change based on the severity of the outcome.
Why most organisations focus on the big events
There are far more near misses and minor incidents than serious ones, and investigating each with the same intensity as a fatality is impossible. Resources are finite, and teams are stretched, so it's easier to reserve the full investigative effort for the events that demand it.
But this misses the point. You don't need to investigate every minor event with the same level of detail. What you need is a system that captures them consistently, categorises their causes using a common language, and still allows you to conduct an investigation that surfaces patterns before they converge into something catastrophic.
How do you learn from minor incidents?
Organisations that invest serious effort into investigating lower-consequence events often outperform those that reserve their attention for the big ones. Five smaller investigations, conducted with discipline and rigour, will typically surface the same root causes that would eventually combine to produce something catastrophic, but at a fraction of the human cost.
Organisations that learn from minor incidents share a few common habits:
• Using a structured root cause taxonomy across all investigations, regardless of severity
• Treating near misses as data points rather than lucky escapes
• Reviewing trends quarterly rather than incident by incident
• Identifying which contributing factors keep appearing across multiple events
Organisations that do this stop chasing individual failures and start fixing systemic weaknesses.
Minor incidents are signals, not noise
Minor incidents and near misses are not noise to be filtered out. They are signals, early warnings that the conditions for failure are present. Act on them, and you address the reasons why before the consequences become severe.
Ask yourself: how does your organisation currently triage investigations? Are your near-miss reports being analysed for patterns, or simply filed and forgotten? The answers might tell you whether you're learning from all of the small fish, or waiting for the big one.
Want to learn more?
.webp)
.webp)
.webp)