Command Analysis Group
Case walkthrough
The Challenger launch decision
Axiom 0 Terminology FirewallFM-6 Information Latency Failure
The night before the launch, an engineering answer changed without the engineering data changing. The framework has a name for what happened in that sentence.
The record
On the night of January 27, 1986, engineers at Morton Thiokol argued against launching the space shuttle Challenger in record cold. They had o-ring erosion data from previous flights. They had a recommendation: do not fly below 53 degrees Fahrenheit.
On the teleconference with NASA that evening, with NASA pushing back on the recommendation, a Thiokol executive told his engineering vice president to set aside his engineering hat and put on his management hat. The exchange is preserved in the Rogers Commission record. The recommendation reversed after it.
Challenger launched the next morning, January 28, 1986. Seven crew members died.
The structural read
Axiom 0 of Structural Command Theory, the Terminology Firewall, holds that structural questions, conduct questions, and instrument questions are different categories, and that collapsing the categories invalidates the analysis that follows. "Is this joint safe below 53 degrees" is an engineering question. It did not stop being an engineering question when the hat changed.
The hat swap added no information. It swapped the category so the answer could change without the data changing. That is what category collapse looks like inside a live decision: the question gets reassigned to a domain where a different answer is available.
The published catalog carries a second read on the same record. FM-6, Information Latency Failure, covers the case where the decision-relevant signal exists but arrives suppressed at the decision boundary. The o-ring data existed. The recommendation existed. What failed was the structure that should have kept the engineering answer bound to the engineering question all the way through the decision.
The Rogers Commission put the documents in the public record. Read the teleconference testimony and watch the category swap happen in real time.
On your workfront
Where I work we'd say it plainer: the pipe doesn't care what hat you're wearing. A load calculation doesn't change when a manager restates it, and a torque spec doesn't loosen because the schedule got tight.
The carryable test: when an answer changes, ask what new data arrived. If the answer changed because the category changed, the structure did the deciding. The framework's move is to go look at the structure.
The pattern this case illustrates also has an entry in the misdiagnosis lookup, indexed by what workplaces usually call it.
Sources
- Report of the Presidential Commission on the Space Shuttle Challenger Accident (the Rogers Commission report), 1986, including the pre-launch teleconference testimony in the Commission's hearing record.
- Diane Vaughan, The Challenger Launch Decision (University of Chicago Press, 1996), for the fullest documentary reconstruction of the decision environment.
The hat statement is paraphrased here. The exact wording is in the Commission's hearing record; read it there.
Framework reference: Goe 2026a, Structural Command Theory (Axiom 0; failure-mode taxonomy). Free to read, CC-BY 4.0. Full citation formats are in the citation kit.