NASA
NASA Space Shuttle Challenger Disaster
Estimated impact: $3.2B (shuttle replacement cost); 7 lives
The Space Shuttle Challenger broke apart 73 seconds after launch, killing all seven crew members. Morton Thiokol engineers had warned that O-ring seals in the solid rocket boosters would fail in cold temperatures, but NASA management overrode their objections due to schedule pressure and political considerations.
Decision context
Whether to proceed with the Challenger launch on January 28, 1986, despite engineer warnings that cold temperatures could cause O-ring failure in the solid rocket booster joints.
Decision anatomy
Red = risk factor present · Green = protective factor present
The analysis below was produced from the pre-decision document only. No hindsight. This is what the platform would have surfaced if it had been running at the time.
“On January 27, 1986 (the evening before the Challenger launch), Morton Thiokol engineers held a teleconference with NASA's Marshall Space Flight Center management. Thiokol engineers Roger Boisjoly and Arnie Thompson presented data showing O-ring erosion correlated with low launch-pad temperatures. Their recommendation was NO LAUNCH below 53°F. Forecast for January 28 was 29-36°F at launch time. NASA Marshall management pushed back, asking Thiokol to reconsider. After Thiokol management caucused away from the engineering team, they reversed the no-launch recommendation and cleared the launch. Boisjoly and Thompson were not polled in the reversed recommendation.”
Source: Rogers Commission Report (1986), Chapter V; Diane Vaughan, "The Challenger Launch Decision" (1996)
Red flags detectable at decision time
- Engineering recommendation: NO LAUNCH below 53°F. Forecast: 29-36°F at launch.
- Burden of proof inverted — "prove it is unsafe" rather than "prove it is safe"
- Thiokol management caucused WITHOUT the engineers who raised the objection
- Prior launches had shown O-ring erosion — treated as successes rather than warning signs
- Schedule pressure from State of the Union address and "Teacher in Space" political commitment
Cognitive biases the platform would have flagged
Hypothetical analysis
DI would flag the Challenger launch decision as the canonical groupthink + availability heuristic failure. The availability heuristic is operative in 'prior flights with O-ring erosion were successful, therefore the problem is tolerable' — a decision-process where a bright-line engineering specification (NO LAUNCH below 53°F) was treated as a negotiable threshold. Vaughan termed this 'normalization of deviance' — incremental acceptance of out-of-spec conditions. A bias-adjusted review would have treated the engineering recommendation as a non-negotiable constraint, not a starting position for managerial negotiation.
Biases present in the decision
★ Primary driver · Severity estimated from bias type and decision outcome
Toxic combinations
Reference class base rates
Across all 143 curated case studies in our library:
Lessons learned
- When engineers raise safety objections and management demands they "prove it is unsafe" rather than "prove it is safe," the burden of proof has been fatally inverted.
- Authority bias caused Thiokol engineers to reverse their no-launch recommendation when pressured by NASA management.
- Availability heuristic led NASA to treat prior successful launches with O-ring erosion as evidence of safety rather than warning signs.
Source: Presidential Commission on the Space Shuttle Challenger Accident (Rogers Commission Report, 1986); NASA Report RSC-86-0137 (NTSB Report)
We caught these patterns in NASA's own record — before the outcome.
See the full hindsight-stripped auditwe ran — no login, no card. Then run the same 60-second audit on your own next memo.
Or leave your email, we'll run a strategic memo of your choosing and send the readout within a business day.
Workflows that fire on decisions like NASA’s
The same Recognition-Rigor Framework that documents this case audits memos in the same shape — before the outcome forces the lesson.