Nobody ever gets credit for fixing problems that never happened (2001) [pdf]
Preventing failures before they occur is often invisible work that rarely earns recognition, creating perverse incentives in everything from software engineering and security to public policy. Commenters cite Y2K, ozone depletion, and COVID vaccines as examples where massive preventative effort led many to later dismiss the underlying risk, while inside companies “hero” firefighters are rewarded more than those who quietly design robust systems. Many argue this misalignment stems from metric-driven management and short-term thinking, and suggest better leadership, risk-aware incentives, and explicit tracking of near-misses and mitigations as ways to value prevention on par with crisis response.
Preparedness & “Non-Events” (Y2K, ozone, climate, safety)
- Core theme: when prevention is effective, the public often concludes the threat was overblown, not that mitigation worked.
- Y2K is repeatedly cited: huge remediation efforts led to almost no visible failures, which many now misremember as “it was a scam” or “nothingburger.”
- Ozone hole / CFCs and COVID vaccination are used as analogies: problems seem to vanish after coordinated action, leading some to doubt they were ever serious.
- Climate change is contrasted with Y2K: incentives are diffuse, impacts staggered, and many actors can externalize costs; some hope for a “Y2K-style” fix, others are pessimistic.
- Concepts mentioned: preparedness paradox, organizational/“scar tissue,” and the idea that good defense (IT, security, military, safety) is invisible when it works.
Organizational Incentives, Hero Culture & Firefighting
- Many describe environments where fixing visible incidents gets praise and promotion, while quiet prevention is ignored or even punished.
- “Hero” engineers who introduce complexity or bugs and then heroically fix outages are often rewarded more than people whose work “just works.”
- Management and political dynamics:
- Overreaction to one-off incidents creates heavy, lasting bureaucracy.
- Metrics (velocity, bug counts, uptime counters) get gamed and can push people away from real risk reduction.
- Reactionary legislation / policies driven by “we must do something” are seen as parallel phenomena.
Measurement, Metrics & Management Quality
- Discussion of leading indicators and organizational observability: tracking “near misses” and validations triggered can surface the value of preventive work.
- Good managers are described as those who:
- Understand technical work enough to value prevention.
- Track and reward reliability, not just crisis response.
- Avoid over-reliance on crude metrics like story points or bug counts.
Individual Coping Strategies & Careers
- Suggestions for individuals:
- Document and periodically communicate prevented issues and resilience work.
- Practice tactful self-promotion; find managers and orgs that value it.
- Track one’s own and team productivity to build evidence of impact.
- In dysfunctional orgs, some cynically recommend letting things fail or timing fixes to maximize career credit; others reject this as unethical but acknowledge the incentive problem.
- Several note that in healthy teams, people whose work rarely causes incidents do get informally recognized over time, but large organizations often fail at this.