> ## Content Index
> Fetch the complete content index at: https://www.nanosava.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Everyone in the Room Knew
- URL: https://www.nanosava.com/essays/everyone-in-the-room-knew/
- Published: 2026-11-04T13:00:00.000Z
- Updated: 2026-11-04T12:59:59.000Z
- Description: Functional stupidity pays in the short run, one sensible career move at a time. The organization pays later, all at once.
- Author: Sava
- Tags: Emergent Stupidity

## The night before

On the evening of January 27, 1986, the room was really three rooms. Engineers and managers at Morton Thiokol in Utah, at NASA's Marshall Space Flight Center in Huntsville, Alabama, and at the Kennedy Space Center in Florida were joined by a telephone line and a fax machine. The next morning's launch of the shuttle Challenger was forecast to be colder than any before it.

Thiokol's engineers recommended plainly against launching below 53 degrees Fahrenheit, the coldest O-ring temperature on any previous flight. Marshall pushed back. Lawrence Mulloy, the booster project manager, objected to a new temperature rule written on the eve of a launch; with it, he said, NASA "may not be able to launch until next April." George Hardy, Marshall's deputy director of science and engineering, said he was "somewhat appalled" by Thiokol's reading of the data, and also that he would not recommend launching if Thiokol did not.

Thiokol asked for five minutes off the line. The caucus lasted about thirty, with the other sites on mute. In Utah, the engineer Arnold Thompson got up, walked up the table, and sketched the joint again on a pad in front of the managers. "When he realized he wasn't getting through," his colleague Roger Boisjoly testified, "he just stopped." Boisjoly tried once more with photographs of blackened grease from a cold flight a year earlier. "I also stopped when it was apparent that I couldn't get anybody to listen."

Then, in Boisjoly's account, the senior vice president, Jerry Mason, said they had to make a management decision and asked Bob Lund, the vice president of engineering, "to take off his engineering hat and put on his management hat." Four managers made the call. Boisjoly was "never asked nor polled."

Back on the line, Thiokol recommended launch. NASA's shuttle project manager, Stanley Reinartz, asked if there were any further comments. "To my recollection," Mulloy later testified, "there were none."

The air at launch was 36 degrees, 15 degrees colder than any previous launch. Challenger broke apart 73 seconds after liftoff. Francis Scobee, Michael Smith, Ellison Onizuka, Judith Resnik, Ronald McNair, Gregory Jarvis, and Christa McAuliffe died.

## The question

Dietrich Bonhoeffer warned that stupidity is a more dangerous enemy of the good than malice. This part follows that enemy to where most of us meet it every week: the meeting.

Did everyone in the room know? Not with certainty. Nobody ever does, the night before. But the knowledge was in the room: the data, the photographs, two engineers who had not changed their minds. So the question here is not who was stupid that night. In any ordinary sense, nobody was. The question is how a room full of capable people can hold what it needs to know and still act as if it did not.

## Smart people, narrow thinking

In 2012 the organization scholars Mats Alvesson and André Spicer gave this a name that sounds like an insult and is not: **functional stupidity**. They define it as "an absence of reflexivity, a refusal to use intellectual capacities in other than myopic ways and avoidance of justifications." It is not a shortage of brains. Organizations are full of clever people who learn, sensibly, where not to point their cleverness.

The important word is *functional*. Functional stupidity, they write, "is productive because it cuts short costly and anxiety inducing questions and creates a sense of certainty." Meetings end on time. Schedules hold. The person who stops asking awkward questions earns a reputation for being constructive. The description of their 2016 book, *The Stupidity Paradox*, states the trade in one line: "a good thing in the short term but a disaster in the longer term."

Bob Lund, the engineer who changed hats, was later asked by the presidential commission's chairman how he explained changing his mind. "We had to prove to them that we weren't ready," he said, "and so we got ourselves in the thought process that we were trying to find some way to prove to them it wouldn't work, and we were unable to do that." And then: "I should have detected that, but I did not, but the roles kind of switched."

The burden of proof had flipped, and nobody had decided to flip it. Lund and Mason remembered the final review as "an unemotional, rational discussion." I believe them. That is the unsettling part.

## The three mechanisms, here

[Part I](https://www.nanosava.com/essays/the-stupidity-no-one-chose/) set out three mechanisms that systems run: delegation, insulation, and alignment. Organizations run all three. In a meeting, alignment leads, and insulation has usually done its work before anyone sits down.

**Alignment: what the organization rewards.** Look at what the teleconference rewarded. Nobody was punished that night for dissent; dissent was simply made expensive. A launch might slip to April. The customer was "appalled." The question moved from engineering to management, where the engineers were not polled. The commission's finding is blunt: Thiokol's management reversed its position "at the urging of Marshall and contrary to the views of its engineers in order to accommodate a major customer."

Irving Janis called one version of this pull groupthink (1972); later reviews found few empirical tests and many criticisms, so I treat it as a lens, not a law. Seventeen years after Challenger, the board that investigated the loss of Columbia wrote that people who are marginal and powerless in an organization may hold useful information, and "even when these people are encouraged to speak, they find it intimidating to contradict a leader's strategy or a group consensus." One NASA engineer, Rodney Rocha, drafted an email calling the decision not to request outside images of the foam strike "the wrong (and bordering on irresponsible) answer," and ended with the agency's own safety poster: "If it's not safe, say so." He never sent it. Asked why, he said he did not want to jump the chain of command.

**Insulation: what the organization provides.** The second mechanism is distance between a decision and the inconvenient fact, and organizations supply it as format. In early 1985, an 18-page flight readiness briefing noted that "low temperature enhanced probability of blow-by." At the top-level review it shrank to a one-page chart: "acceptable risk." That July, Boisjoly warned Lund in a memo that if a field joint failed, "the result would be a catastrophe of the highest order," and named it: "loss of human life." Three weeks later, a briefing to NASA Headquarters, in the commission's words, "concluded that the O-ring seal was a critical matter, but it was safe to fly." Nothing was hidden. It was known, and filed under acceptable. The Columbia board later found the crucial number at the bottom of a PowerPoint slide and observed that as information climbs a hierarchy, "key explanations and supporting information is filtered out."

The sociologist Diane Vaughan, in *The Challenger Launch Decision* (1996), named the acceptance of events that are not supposed to happen: the normalization of deviance. Each flight that survived a warning made the next warning easier to file. At Boeing, the House committee's majority staff listed a "Culture of Concealment" among its central themes: "In several critical instances, Boeing withheld crucial information from the FAA, its customers, and 737 MAX pilots," including, from pilots, the very existence of MCAS, software designed to push the airplane's nose down automatically in certain conditions.

**Delegation: what the process offers.** The chain of command, the sign-off, the delegated check: each offers a default authority, and lets each person believe someone else is doing the looking. In the 737 MAX program, Boeing employees called Authorized Representatives were supposed to represent the interests of the regulator, the FAA. "Excessive FAA delegation to Boeing has eroded FAA's oversight capabilities," the report found, citing a 2016 Boeing internal survey in which 39 percent of the representatives who responded perceived "undue pressure," and 29 percent were concerned about the consequences if they reported it. The structure said an independent eye was watching. The people inside the structure had careers.

## Why nobody chose it

The clearest study of how this adds up is about Nokia, and it shows alignment and insulation feeding each other. Timo Vuori and Quy Huy studied its fall from 2005 to 2010, from world dominance to losing the smartphone battle. They found fear, but not one fear. Top managers were afraid of external competitors and shareholders, and put pressure on middle managers "without fully revealing the severity of the external threats." Middle managers were afraid of internal groups, "including superiors and peers," so they shared less bad news. The top developed "an overly optimistic perception of their organization's technological capabilities" and neglected the long-term work. Fear rewarded silence below, and the silence insulated the top.

Now look at the individual steps, in any company. Rounding a forecast up a little. Not forwarding an awkward email. Not asking a question that would make a boss look uninformed. Each is defensible. Each protects a career for one more quarter. Add them up across a company and you get an organization that believes something none of its people believe. That is emergent stupidity: a property of the whole, owned by none of the parts.

The savings are collected every day. The bill arrives later, all at once. The House committee's report concluded that the two 737 MAX crashes, which killed 346 people, "were not the result of a singular failure, technical mistake, or mismanaged event," but "the horrific culmination" of faulty technical assumptions, a lack of transparency, and grossly insufficient oversight. The Columbia board heard "echoes" of Challenger and concluded that flawed practices had "continued for 20 years and made substantial contributions to both accidents."

## More and more

The shrinking of an 18-page briefing into one comfortable chart used to take people and meetings. Now it takes seconds. AI dashboards summarize the quarter. Meeting assistants summarize the meeting. Models draft the status report, and the summary of it. Each is useful, and each is delegation in its newest form: a summary is a decision about what you do not need to know, made by someone, or something, you did not choose.

There is a sharper worry. In a 2023 preprint, a team of AI researchers reported that five leading AI assistants of the time "consistently exhibit sycophancy," tending to give answers that match the user's views, and that the human preference data used to train such systems tends to favor answers that agree with the person judging them. Nokia's middle managers learned to tell the top what it wanted to hear because they were afraid. We are now putting a layer between the analyst and the executive that can learn something similar from our approval, with no fear required.

Here is my risk ladder, as judgment rather than finding. If this compounds for five or ten years, we get organizations where fewer people have read anything raw, where every dashboard is a little greener than the floor beneath it, and where the cost of looking keeps rising because nobody around you looks. Nothing breaks for a long time. Then something does, all at once, the way it did for NASA twice.

None of this is fate. The same tools can be told to surface the outlier, the dissent, the line at the bottom of the slide. Whether they do is a choice about culture, made one meeting at a time.

## Noticing it in a meeting

The counterweight has a name. Amy Edmondson's research defines team psychological safety as "a shared belief that the team is safe for interpersonal risk taking": confidence that the team "will not embarrass, reject, or punish someone for speaking up." Among hospital teams she studied, one nurse said of medication errors, "You get put on trial! People get blamed for mistakes . . . you don't want to have made one." On other teams in the same hospital, errors were openly acknowledged and discussed. Same building, different rooms.

So, the Three Checks and the Scale Question, to carry into your next decision meeting:

1. **The delegation check.** Who in this room has read the underlying report, not the slide, not the summary, not the AI digest? If nobody has, the decision is being made by whoever wrote the summary.
2. **The insulation check.** What would we rather not find out before we decide, and what format, schedule, or chain is keeping it out of the room? Name the document nobody has opened, and open it.
3. **The alignment check.** Who in this room is paid to disagree, and what happens to them when they do? The Challenger commission noted that "no one thought to invite a safety representative" to the teleconference. And do not fake it: in one experiment, an authentic dissenter produced better solutions than any form of assigned devil's advocate.
4. **The Scale Question.** If every team in this organization handled bad news the way we are about to handle this one, what would the organization know a year from now?

One practice: **say out loud where the burden of proof sits.** In a separate finding, about ice on the launch pad that morning, the Challenger commission wrote that NASA "appeared to be requiring a contractor to prove that it was not safe to launch, rather than proving it was safe." Lund saw that switch only afterward. Before any go or no-go, name it for the room. Then let the most junior person speak first.

## Any further comments?

That night, the engineers had already said everything they could and been overruled. The managers had made a judgment call they believed was rational. Two of the three rooms had been on mute. When the question came, nobody on the line answered, and no single silence was the cause.

The next time someone ends a meeting with "any further comments?", hear it for what it is: the last exit.

**This week's ask: one sighting.** Where did you see a room know something and decide not to? A forecast nobody believed, a risk nobody raised, a report nobody opened. No names, no companies, no shaming. Leave it in the comments (free subscribers can comment) or send it to hello@nanosava.com. I read every sighting, and the best ones, anonymous unless you say otherwise, will shape later parts.

## Sources

1. Presidential Commission on the Space Shuttle Challenger Accident, "Chapter V: The Contributing Cause of The Accident," *Report to the President*, Vol. 1, 1986\. Teleconference timeline, testimony of Mulloy, Hardy, Boisjoly, Lund, and Mason, and Findings 1 to 4\. [https://www.nasa.gov/history/rogersrep/v1ch5.htm](https://www.nasa.gov/history/rogersrep/v1ch5.htm?ref=nanosava.com)
2. Presidential Commission on the Space Shuttle Challenger Accident, "Chapter III: The Accident," *Report to the President*, Vol. 1, 1986\. Launch time, 36 degrees, 73 seconds. [https://www.nasa.gov/history/rogersrep/v1ch3.htm](https://www.nasa.gov/history/rogersrep/v1ch3.htm?ref=nanosava.com)
3. Presidential Commission on the Space Shuttle Challenger Accident, "Chapter VI: An Accident Rooted in History," *Report to the President*, Vol. 1, 1986\. Boisjoly memo of July 31, 1985; the 18-page briefing and one-page chart. [https://www.nasa.gov/history/rogersrep/v1ch6.htm](https://www.nasa.gov/history/rogersrep/v1ch6.htm?ref=nanosava.com)
4. Presidential Commission on the Space Shuttle Challenger Accident, "Chapter VII: The Silent Safety Program," *Report to the President*, Vol. 1, 1986\. [https://www.nasa.gov/history/rogersrep/v1ch7.htm](https://www.nasa.gov/history/rogersrep/v1ch7.htm?ref=nanosava.com)
5. Columbia Accident Investigation Board, *Report*, Volume I, August 2003\. Rocha email (Ch. 6), PowerPoint slide (Ch. 7), "Echoes of Challenger" and normalization of deviance (Ch. 8). [https://s3.amazonaws.com/akamai.netstorage/anon.nasa-global/CAIB/CAIB\_lowres\_full.pdf](https://s3.amazonaws.com/akamai.netstorage/anon.nasa-global/CAIB/CAIB%5Flowres%5Ffull.pdf?ref=nanosava.com)
6. Mats Alvesson and André Spicer, "A Stupidity-Based Theory of Organizations," *Journal of Management Studies* 49(7), 2012\. Quoted from the accepted manuscript at City, University of London, which may differ slightly from the published version. [https://openaccess.city.ac.uk/id/eprint/15604/](https://openaccess.city.ac.uk/id/eprint/15604/?ref=nanosava.com) (published version: [https://doi.org/10.1111/j.1467-6486.2012.01072.x](https://doi.org/10.1111/j.1467-6486.2012.01072.x?ref=nanosava.com))
7. Mats Alvesson and André Spicer, *The Stupidity Paradox: The Power and Pitfalls of Functional Stupidity at Work*, Profile Books, 2016\. Publisher's description. [https://profilebooks.com/work/the-stupidity-paradox/](https://profilebooks.com/work/the-stupidity-paradox/?ref=nanosava.com)
8. Diane Vaughan, *The Challenger Launch Decision: Risky Technology, Culture, and Deviance at NASA*, University of Chicago Press, 1996 (enlarged edition with a new preface, 2016). [https://press.uchicago.edu/ucp/books/book/chicago/C/bo22781921.html](https://press.uchicago.edu/ucp/books/book/chicago/C/bo22781921.html?ref=nanosava.com)
9. Timo O. Vuori and Quy N. Huy, "Distributed Attention and Shared Emotions in the Innovation Process: How Nokia Lost the Smartphone Battle," *Administrative Science Quarterly* 61(1), 2016\. Quotations from the published abstract. [https://doi.org/10.1177/0001839215606951](https://doi.org/10.1177/0001839215606951?ref=nanosava.com)
10. Committee on Transportation and Infrastructure, US House of Representatives, majority staff, "Final Committee Report: The Design, Development & Certification of the Boeing 737 MAX," September 2020\. [https://democrats-transportation.house.gov/imo/media/doc/2020.09.15%20FINAL%20737%20MAX%20Report%20for%20Public%20Release.pdf](https://democrats-transportation.house.gov/imo/media/doc/2020.09.15%20FINAL%20737%20MAX%20Report%20for%20Public%20Release.pdf?ref=nanosava.com)
11. Irving L. Janis, *Victims of Groupthink*, Houghton Mifflin, 1972.
12. Won-Woo Park, "A Review of Research on Groupthink," *Journal of Behavioral Decision Making* 3(4), 1990\. [https://doi.org/10.1002/bdm.3960030402](https://doi.org/10.1002/bdm.3960030402?ref=nanosava.com)
13. Mrinank Sharma et al., "Towards Understanding Sycophancy in Language Models," arXiv preprint, 2023\. [https://arxiv.org/abs/2310.13548](https://arxiv.org/abs/2310.13548?ref=nanosava.com)
14. Amy C. Edmondson, "Psychological Safety and Learning Behavior in Work Teams," *Administrative Science Quarterly* 44(2), 1999\. [https://doi.org/10.2307/2666999](https://doi.org/10.2307/2666999?ref=nanosava.com)
15. Charlan Nemeth, Keith Brown, and John Rogers, "Devil's Advocate versus Authentic Dissent: Stimulating Quantity and Quality," *European Journal of Social Psychology* 31(6), 2001\. [https://doi.org/10.1002/ejsp.58](https://doi.org/10.1002/ejsp.58?ref=nanosava.com)