n o ren
Systems & Organizations

Safer Designs, More Disasters

NASA’s engineers knew the O-rings would fail in cold weather, but the push to meet launch schedules made them silent in 1986.

When organizations prioritize predictability over real-time adaptability, they create a hidden incentive to downplay risks that threaten timelines or budgets. In the Challenger disaster (1986), engineers argued against launching in freezing temperatures due to O-ring vulnerabilities. But NASA managers, bound by political and financial deadlines, dismissed the warnings. The fatal flaw wasn’t the design—it was the culture that treated dissent as a delay, not a safeguard. This dynamic repeats in organizations where “no surprises” policies punish proactive problems, forcing teams to choose between honesty and career risk. The solution? Build systems where red flags are rewarded, not penalized.

Deadlines become blinders when accountability for delays outpaces accountability for failures.
Engineers don’t cause disasters—they signal them. Systems that silence signaling cause disasters.
“No surprises” cultures trade transparency for predictability, assuming risks are cheaper to fix later. They aren’t.

If you ignore the friction between scheduling pressures and safety, your next crisis won’t be a technical failure—it’ll be an organizational one.

Teams learn to hide risks when leadership frames delays as personal failures, not as early warnings.

1
Audit your team’s communication: in the last 30 days, note any time a “concern” was dismissed with “we can’t afford delays.” List them in your next retrospective.
2
Add a “red flag” column to your project tracking. Require every team member to log one risk per week, with no penalty for overreporting.

The Challenger disaster wasn’t just a systems failure—it was a textbook case of “normalization of deviance.” Engineers had data showing O-rings degraded in cold weather, but since past launches succeeded, management assumed risk had been mitigated. The lesson: safety margins shrink when success is defined as “no deviations from plan,” not “no deviations from reality.”

This same dynamic explains Boeing’s 737 MAX crashes and Toyota’s “production over people” recalls. In all cases, hierarchical pressure to meet targets flattened hierarchical responsibility, creating a gap between known risks and organizational action.