Why Leaders Should Rethink Near Miss Reporting

Near miss reporting gives leaders a sense that weak signals are being captured. The harder question is whether those signals are helping the organisation understand how work is changing.

This is the executive reading of the near miss problem. Leaders do not need to manage every report. They do need to understand what confidence the reporting system deserves, and where that confidence may be overstated.

The near miss is attractive as a management concept because it appears to offer foresight. It seems to show where something nearly went wrong before an actual outcome occurs. But as a metric, it is unstable. It reflects reporting behaviour as much as operational risk.

Why the metric needs care

A rising near miss count can be a good sign. It may mean trust is increasing and workers are more willing to speak up. It can also mean exposure is increasing. A falling count may indicate better control, or it may indicate fatigue, fear, or silence.

That ambiguity matters for leaders. If the organisation treats the number as the performance signal, it can reward the wrong behaviour. Teams may chase volume, suppress noise, or over-process minor reports to satisfy the system.

The better leadership question is whether near miss information is improving the organisation's understanding of work. Does it show where standards are hard to follow? Does it reveal where controls are thin? Does it identify repeated conditions that deserve investment?

Where leadership should narrow

Near miss reporting becomes more useful when leaders stop treating it as a count of almost-events and start treating it as a source of information about operational variation.

That is why Deviation from Standards is a stronger strategic lens. It focuses on what actually happened: where work departed from the intended method, whether reliability decreased, whether vulnerability increased, whether resilience was demonstrated, or whether a better way of working appeared.

This matters because leaders make decisions that shape the conditions of work: resourcing, time pressure, contractor strategy, system complexity, supervision capacity, and the appetite for redesigning standards that no longer fit the task.

What leaders should ask

Leaders do not need a longer dashboard. They need better questions around the dashboard they already have. Which reports show repeated deviation from the same standard? Which controls are being worked around? Which sites report very little despite complex work? Which actions keep closing records without changing the condition?

Those questions move the conversation away from reporting volume and toward organisational learning. They also make the metric harder to game, because the focus shifts from how many reports were submitted to what the organisation understood and changed.

A good executive review should not simply ask whether near miss reporting is increasing or decreasing. It should ask what the pattern says about the way work is being planned, supervised, adapted, and resourced.

What this changes

Near miss reporting still has a role. It can draw attention to weak signals and invite people into the safety conversation. But it should not be allowed to become a proxy for risk intelligence.

For leaders, the opportunity is to reposition near miss reporting as one input into a broader understanding of work. The strongest signal may not be that something almost happened. It may be that the work departed from the standard in a way the organisation needs to understand before the same condition appears again.