One Reason Why Employees Stop Reporting Near-Misses

Episode 309 explains that when leaders and the system fail to close the loop on reports or respond with blame, employees learn that reporting near‑misses is futile or dangerous, so they stop doing it. Dr. Ayers illustrates this with a personal near‑miss from 35 years ago that was met with suspicion rather than support, showing how cultural signals can shut down reporting for decades.

Key points (what the episode emphasizes)

• Lack of visible action kills reporting. When reports produce no fix, no follow‑up, and no communication, employees conclude reporting doesn’t matter.

• Blame and negative reactions create fear. Even subtle responses—eye‑rolling, questioning motives, or lecturing—teach workers that reporting carries personal risk.

• Mixed signals from supervisors matter more than policy. Phrases like “we don’t have time” or “just be careful” communicate that production beats safety, so workers self‑silence.

• Assumptions and friction reduce reports. Employees sometimes assume leadership already knows about hazards or find the reporting process too cumbersome, so they don’t bother.

Three leader actions the episode recommends (ready to use today)

1. Close the loop every time. Acknowledge reports immediately, explain next steps, and follow up with outcomes—even if the fix is delayed. Visible follow‑through rebuilds trust. (ca://s?q=Close_the_loop_on_reports)

2. Respond with curiosity, not blame. Train supervisors to ask “What happened?” and “How can we prevent it?” instead of assigning fault; this reduces fear and increases psychological safety. (ca://s?q=Curiosity_not_blame)

3. Make reporting easy and visible. Simplify the process, remove paperwork friction, and publicly recognize reporters so reporting is seen as contribution, not complaining.

Why this matters

Reporting is a leadership and system problem, not an employee problem. When leaders model safety, act visibly on reports, and remove blame, reporting returns—and hazards get fixed before they become incidents. The episode’s practical examples show that small, consistent leader behaviors change culture faster than more rules or forms.