Success is reassuring, but it doesn’t always reveal why something worked. A project finishes on schedule, a flight lands without incident, or a mistake is caught before reaching a customer, and everyone moves on. The outcome was good, so there may seem to be little reason to examine what happened along the way.
A near miss presents a different opportunity. Something almost went wrong, yet the consequences were avoided because someone noticed the problem, a safeguard worked, or circumstances simply happened to break in the right direction.
Unlike a clear success, that moment exposes a weakness without requiring an organization to pay the full price of discovering it.
Aviation has long recognized the value of studying these events. Entrepreneur and pilot Sky Dayton has written about aviation, safety, and flying experiences on his Medium page, subjects that belong to a field where examining mistakes and close calls is deeply embedded in the culture.
Aviation’s approach offers lessons well beyond the cockpit because it treats information about what almost happened as potentially valuable evidence.
The scale of that effort is substantial. NASA’s Aviation Safety Reporting System, created in 1976, has received more than 2.3 million voluntary and confidential reports from pilots, air traffic controllers, maintenance technicians, cabin crew, dispatchers, and others.
Today, the system receives more than 350 reports a day describing safety issues, near misses, and close calls.
NASA analyzes that information to identify emerging problems and share lessons that may help prevent future accidents.
The principle behind the system is straightforward: organizations don’t have to wait for disaster before deciding that something deserves attention.
A Good Outcome Doesn’t Mean the Process Was Good
Imagine two teams completing similar projects successfully. One followed a well-tested process, identified problems early, and finished with enough time to review its work.
The other encountered repeated communication failures, discovered a serious mistake hours before the deadline, and succeeded only because an employee happened to notice it.
On paper, both projects may appear successful. In reality, they tell very different stories about the likelihood of future failure.
This is one reason outcomes can be deceptive. When something goes well, people naturally tend to focus on the result. The vulnerabilities that existed along the way are easier to overlook because they never produced visible consequences.
Near misses make those vulnerabilities harder to ignore. A missed inspection that happens not to cause a problem is still a missed inspection. An incorrect number discovered before a proposal reaches a client still reveals something about the review process.
A software problem caught immediately before deployment may point to weaknesses in testing even though customers never experience the bug.
The absence of damage shouldn’t automatically be interpreted as evidence that the underlying system worked as intended.
Aviation Created a System for Learning Before Disaster
Aviation provides an unusually clear example of what can happen when organizations deliberately collect information about close calls.
NASA’s Aviation Safety Reporting System is voluntary, confidential, and non-punitive. Reports are de-identified before being entered into the database, allowing aviation professionals to describe incidents in detail while protecting their identities. The information can then be analyzed for hazards, recurring patterns, lessons learned, and potential improvements.
That structure matters. People are less likely to disclose mistakes when they believe doing so will automatically result in punishment or embarrassment.
A system designed to learn from errors, therefore, needs a way to distinguish between information that should improve safety and conduct that genuinely warrants disciplinary action.
The FAA has built incentives around that principle as well. Subject to specific requirements and exceptions, aviation professionals who voluntarily report certain unintentional violations through the system can receive protection from penalties.
The purpose isn’t to suggest that mistakes don’t matter. It is to make information about them available while there is still an opportunity to learn from it.
Aviation organizations can use such reports to improve procedures, checklists, training, safety briefings, and even software. In other words, a close call involving one person can potentially become a lesson for thousands of people who weren’t there.
Healthcare Has Learned the Same Lesson
The value of near misses isn’t confined to airplanes. Healthcare safety researchers pay close attention to them for similar reasons.
The Agency for Healthcare Research and Quality defines a near miss as an unsafe situation that doesn’t produce patient harm because of luck or because the problem is detected in time. One example might be a medication error discovered before the medicine reaches the patient.
No one is injured, but the mistake provides evidence of a weakness that could produce a very different outcome next time.
Treating that event as irrelevant because the patient wasn’t harmed would waste useful information. The better questions concern how the error occurred, what allowed someone to catch it, and whether another person working under slightly different circumstances would be equally fortunate.
This way of thinking changes the meaning of a good outcome. Avoiding harm remains something to be grateful for, but it isn’t necessarily proof that nothing needs to change.
Near Misses Reveal the Role of Luck
One of the most useful things a close call can expose is how much an organization has been relying on favorable circumstances without realizing it.
Consider a company where an important report must be reviewed by two people before publication. One week, the second review is accidentally skipped, but the document happens to contain no errors.
If managers judge the process exclusively by the outcome, nothing appears wrong. The same oversight a month later could allow a serious mistake to reach the public.
Near misses force organizations to separate good decisions from good outcomes. The two often coincide, but not always.
A careless decision can produce a favorable result, just as a careful decision can sometimes end badly because of factors outside anyone’s control.
Organizations that learn effectively try to understand the process rather than allowing the outcome to settle the question.
This is particularly important when consequences are rare but potentially serious. If failure occurs only once in thousands of attempts, waiting for the failure itself may provide very little opportunity to improve.
The People Closest to the Work Often See the Warning Signs
Near misses also highlight the importance of frontline knowledge.
Executives see dashboards, performance indicators, financial results, and formal reports. Employees doing the work see different information.
They notice the workaround everyone uses because a system is cumbersome. They know which step in a process is routinely rushed and which piece of equipment behaves unpredictably.
Individually, those observations may seem minor. Taken together, they can reveal where a system is under strain.
Organizations lose that intelligence when employees conclude that mentioning problems will create more trouble than staying quiet.
A manager who responds defensively to every reported mistake may inadvertently create an environment where fewer mistakes become visible.
A stronger response is curiosity: What happened? Why did it make sense to the person involved at the time? Which safeguard caught the problem? What would have happened if that safeguard hadn’t been there?
Those questions turn reporting from an exercise in assigning blame into an opportunity to understand how work actually happens.
Success Still Deserves Study
None of this means organizations should stop examining what goes right. Success contains valuable information, particularly when teams can identify practices that consistently produce good results.
The danger comes from assuming the result explains the process.
A successful outcome may represent excellent execution, but it can also conceal unnecessary risk, redundant effort, or a last-minute rescue that shouldn’t have been necessary. Near misses are useful precisely because they make those distinctions easier to see.
They also provide a chance to study safeguards that worked. If an employee caught a potentially expensive mistake, the organization should examine not only how the mistake occurred but why it was detected.
Perhaps a review procedure worked exactly as intended. Maybe experience allowed someone to recognize an unusual pattern. Preserving that protective mechanism can be just as important as correcting the original problem.
Learning Before the Cost Becomes Real
Organizations understandably devote enormous attention to failures. When customers are lost, equipment is damaged, money disappears, or people are injured, investigation becomes unavoidable.
Near misses offer many of the same lessons without requiring the same consequences.
That makes them easy to dismiss and unusually valuable at the same time. Nothing terrible happened. Everyone can return to work. The temptation is to feel relieved and move on.
The better response is to preserve the relief while remaining curious about what almost happened. A close call is evidence that the distance between success and failure may have been narrower than it appeared.
Organizations that pay attention to that distance gain an opportunity others miss. They can strengthen a process while the weakness is still theoretical, adjust a safeguard before it fails, and learn from an error before someone has to absorb its full cost. Sometimes the most valuable failure is the one that never quite happened.
