Question
Ask what stopped the near miss from becoming harm
A good ending can hide whether the system was protected or merely lucky.
Before you use it
- Use when
- A near miss ended safely and the team is tempted to close it because 'the control worked.'
Keep this limit in mind
- A single near miss cannot establish a control's failure probability. Use the analysis to choose what to verify, redesign or measure next.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
A question to ask
An error reached the final step but happened to be noticed because a colleague walked past the screen. Was the process protected?
Why it matters
Identify the last thing that interrupted the failure path. Was it a designed safeguard, an independent human check, an unrelated circumstance or pure timing? Then ask whether the same catch would still exist under a different operator, higher load or slightly different sequence. The aim is not to praise or blame the final catcher; it is to understand how much protection actually exists.
An example
A reviewer notices a wrong customer before activation. If review was optional and happened only because that person had spare time, the system should not count it as a reliable barrier.
Check your result
The review names the actual catching mechanism and whether it is designed, repeatable and independent enough to rely on.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingAsk what stopped the near miss from becoming harm
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaCapture the near miss while the evidence still exists
Evidence and sources
AHRQ safety-engineering guidance recommends combining prospective and retrospective analysis with ongoing surveillance, and notes that workarounds can signal that a process is not functioning well.
The guidance is written for healthcare systems; transfer to knowledge work is at the general system-design level.
Engineering Safe Practices Affinity Group · Strategy 1 rationale and opportunities
OSHA recommends investigating close calls and near misses to identify underlying hazards, contributing causes and program shortcomings, and grouping similar events to find trends.
The guidance concerns occupational safety. The same record structure may be useful elsewhere, but the regulatory context does not transfer.
Safety Management - Hazard Identification and Assessment · Hazard Identification and Assessment; Conduct incident investigations
A 2022 scoping review found limited evidence that near-miss reporting and learning itself improves patient safety, so reporting should not be treated as proof that risk has fallen.
The review concerns patient safety and does not test every type of operational near-miss program.
The value of learning from near misses to improve patient safety: a scoping review · PSNet summary
Edition and review
Version 0.1.0
No review details are supplied for this edition.