Building Resourcefulness

Groupthink: 7 Famous Examples and How to Prevent It on Your Team

The Titanic officers knew about icebergs and chose speed anyway. The Challenger engineers knew the O-rings would fail and launched anyway. Groupthink does not look like stupidity. It looks like agreement.

April 14, 202611 min read

Groupthink Does Not Look Like Stupidity. It Looks Like Agreement.

The most expensive decisions in history were not made by incompetent people. They were made by smart, experienced professionals who agreed with each other when they should have challenged each other.

The Titanic officers knew there were icebergs in the shipping lane. They chose maximum speed anyway because questioning the captain's decision felt more dangerous than questioning the course. The Challenger engineers knew the O-ring seals would fail in cold weather. They raised concerns. Management overruled them because the launch schedule felt more important than the data. Kodak invented the digital camera in 1975. Leadership buried it because the film business was so profitable that challenging the status quo felt unnecessary.

In each case, the information to avoid disaster existed inside the organization. The team chose not to act on it. Not because they were fools. Because the group dynamics made agreement feel safer than dissent.

That is groupthink. And your team is susceptible to it right now.

What Groupthink Actually Is

Psychologist Irving Janis coined the term in 1972 after studying catastrophic government decisions. His definition: a mode of thinking where the desire for harmony in a group overrides the realistic appraisal of alternatives.

The key word is "desire." Groupthink is not about being too lazy to think critically. It is about wanting to belong more than wanting to be right. Every team has this tension. The teams that fail are the ones that let belonging win every time.

Groupthink produces three predictable outcomes: incomplete examination of alternatives, failure to examine risks of the preferred choice, and poor information search. In plain language: the team picks the first acceptable option, ignores the downsides, and stops looking for better answers.

7 Examples That Changed History

### 1. The Titanic (1912)

The officers received six ice warnings on the day of the collision. Captain Smith maintained full speed. First Officer Murdoch did not challenge the decision. The lookouts did not have binoculars because questioning the equipment allocation felt like questioning the officers' competence.

The groupthink pattern: hierarchical deference. When the leader's preference was clear (speed), every person in the chain suppressed their own judgment. The information to avoid the iceberg existed. The group dynamics prevented anyone from acting on it.

This is why we built Save the Titanic as a team simulation. When modern teams face the same scenario under time pressure, the same patterns emerge. The leader states a preference. The team defers. Critical information stays hidden because sharing it feels like insubordination. The simulation makes this pattern visible and impossible to ignore.

### 2. The Challenger Disaster (1986)

Morton Thiokol engineers told NASA the O-ring seals on the solid rocket boosters would fail below 53 degrees Fahrenheit. The launch day temperature was 36 degrees. NASA managers pressured Thiokol to reverse their recommendation. Thiokol management overruled their own engineers and approved the launch.

The groupthink pattern: pressure to conform. The engineers had the data. Management had the schedule. When the two conflicted, the group chose the outcome that pleased the authority rather than the outcome the evidence supported. Seven astronauts died.

### 3. The Bay of Pigs Invasion (1961)

President Kennedy's advisors unanimously supported a CIA plan to invade Cuba. The plan was deeply flawed — 1,400 poorly equipped exiles against 20,000 Cuban troops. Several advisors had doubts but stayed silent because the group consensus felt overwhelming. Arthur Schlesinger later wrote that he had serious concerns but suppressed them to avoid appearing soft.

The groupthink pattern: self-censorship. When everyone in the room appears to agree, the cost of disagreement feels higher than the cost of a bad decision. So the doubter stays quiet and the group mistakes silence for consensus.

### 4. Kodak and Digital Photography (1975-2012)

Kodak engineer Steve Sasson invented the first digital camera in 1975. Kodak leadership buried it. The film business generated massive profits. Questioning the core business model felt like career suicide. By the time Kodak acknowledged digital photography, the market had moved on. Kodak filed for bankruptcy in 2012.

The groupthink pattern: illusion of invulnerability. When the current strategy is working, the group believes it will always work. Challenging success feels ungrateful. So the team defends the status quo until it collapses.

### 5. Swissair Collapse (2002)

Known as "the flying bank" for its financial stability, Swissair's leadership pursued an aggressive expansion strategy that drained cash reserves. Board members who questioned the strategy were marginalized. The company ran out of cash in 2001 and grounded its entire fleet.

The groupthink pattern: stereotyping outsiders. When internal critics raised concerns, the leadership dismissed them as pessimists who did not understand the vision. When external analysts issued warnings, leadership treated them as uninformed. The group created an insular reality that could not survive contact with the market.

### 6. Nokia and the Smartphone (2007-2013)

Nokia controlled 50% of the global mobile phone market in 2007. When the iPhone launched, Nokia's leadership dismissed it as a niche product for tech enthusiasts. Internal teams who advocated for touchscreen development were overruled because the group consensus held that physical keyboards were superior. Nokia's market share collapsed to 3% by 2013.

The groupthink pattern: collective rationalization. The team constructed logical-sounding arguments for why the threat was not real. "Our customers prefer keyboards." "Apple does not understand the mass market." Each rationalization reinforced the group's existing belief and prevented genuine examination of the evidence.

### 7. Enron (1996-2001)

Enron's leadership created a culture where questioning the financial strategy was career-ending. Employees who raised concerns about accounting practices were transferred, marginalized, or fired. The board approved increasingly complex financial instruments because challenging the executives who designed them felt impossible. The company collapsed in the largest bankruptcy in American history at that time.

The groupthink pattern: direct pressure on dissenters. When the group actively punishes disagreement, critical thinking does not just fade — it is eliminated. The remaining voices all agree because the disagreeing voices have been removed.

The Pattern Behind Every Example

Every case follows the same sequence:

Step 1: The group forms a preference (usually the leader's preference or the status quo).

Step 2: Dissenting information exists within the group.

Step 3: The group dynamics make sharing that information feel risky (career risk, social risk, or perceived disloyalty).

Step 4: Silence is interpreted as agreement.

Step 5: The group acts on incomplete information with full confidence.

Step 6: The consequences arrive.

Your team runs this sequence in some form every week. Not at the scale of the Titanic or Challenger. At the scale of product decisions, hiring decisions, strategy decisions, and budget allocations. The cumulative cost is enormous. You just do not see it because the consequences arrive slowly, not catastrophically.

<div style="background: #f0f4f8; border-left: 4px solid #c41e3a; padding: 20px; margin: 30px 0;"> <strong>The Titanic sank because of groupthink. Save the Titanic is the simulation where your team discovers whether they fall into the same trap.</strong> Over 6 million participants have faced the same decisions the Titanic officers faced — under real time pressure, with real consequences for every choice. The behaviors that emerge are the same behaviors that show up in your team's meetings. The difference is that in the simulation, the consequences are visible and the debrief changes the pattern. <a href="https://save-the-titanic.com/contact/">See a demo and find out how your team actually decides under pressure</a>. </div>

8 Signs of Groupthink in Your Team

You do not need a disaster to detect groupthink. Look for these patterns in your next team meeting:

1. Decisions happen too fast. When a complex decision gets made in minutes with no debate, the team is not efficient. They are conforming.

2. The same person speaks first every time. Whoever speaks first anchors the conversation. If the leader always opens, the team is optimizing for the leader's preference, not the best answer.

3. Silence is treated as agreement. When the leader says "Any concerns?" and nobody speaks, that is not consensus. That is fear of dissent masquerading as alignment.

4. Objections are treated as disloyalty. When someone raises a concern and gets labeled as "not a team player" or "negative," the group is punishing critical thinking.

5. The team has never reversed a decision. Every team should occasionally say "we were wrong, let us change course." If that has never happened, the team is protecting past decisions rather than examining them.

6. New information does not change the plan. When the team receives data that contradicts their approach and continues unchanged, they are rationalizing rather than analyzing.

7. Outside perspectives are dismissed. When consultants, customers, or cross-functional partners offer different views and the team dismisses them as "not understanding our context," that is collective rationalization.

8. Everyone leaves the meeting feeling good. Productive meetings involve tension. If every meeting feels comfortable and harmonious, the team is avoiding the hard conversations, not resolving them.

Five Practices That Prevent Groupthink

### Practice 1: Assign a Devil's Advocate (And Rotate the Role)

In every significant decision, one person's explicit job is to argue against the preferred option. Not to be difficult. To surface what the group is not seeing. Rotate the role so it does not become one person's identity.

The Stop Killing Ideas framework addresses this directly: create a space where dissent is expected, not tolerated.

### Practice 2: Leaders Speak Last

When the leader shares their opinion first, the team calibrates to it. When the leader speaks last, the team has already generated independent perspectives. The leader hears the full range of thinking before adding their own. This single change reduces conformity pressure more than any other intervention.

### Practice 3: Require Pre-Meeting Positions

Before the meeting, each participant writes down their position and reasoning independently. Share these in writing before the discussion. This prevents anchoring to the first voice and ensures every perspective enters the room, including the perspectives of people who would have stayed silent.

### Practice 4: Invite Outside Challengers

Bring someone from a different department, a different level, or outside the organization to the decision meeting. Their job is to ask the questions the insiders have stopped asking. The Creating Context framework helps outsiders understand enough context to ask meaningful questions without needing months of background.

### Practice 5: Pressure-Test Decisions in a Simulation

The most effective groupthink prevention is experiencing the consequences of groupthink in a safe environment. When a team watches their simulation decisions fail because critical information stayed hidden, they develop a visceral resistance to the same pattern in real work.

This is not theoretical. At ArcelorMittal, 710 leaders went through Save the Titanic via Duke Corporate Education. Decision speed improved 30-40% afterward. Not because leaders became faster. Because they stopped deferring to the loudest voice and started surfacing the information that mattered.

Frequently Asked Questions About Groupthink

### How do you bring up groupthink concerns without being labeled as difficult? Frame it as process, not personality. Instead of "I think we have a groupthink problem," say "I noticed we made this decision in 3 minutes with no debate. Could we spend 5 minutes listing the risks before we commit?" Process-level observations feel constructive. Personality-level observations feel accusatory. The Yes And approach helps: acknowledge the team's direction, then add the concern.

### Can groupthink happen in small teams? Yes. Research shows groupthink intensifies in small, cohesive teams because the social bonds are stronger. A three-person leadership team where two members agree can silence the third more effectively than a twenty-person committee. Small teams need explicit dissent structures even more than large ones because there are fewer natural challengers.

### What is the difference between groupthink and consensus? Consensus means everyone genuinely agrees after examining alternatives. Groupthink means everyone appears to agree because the examination was suppressed. The test: can every person in the room name the strongest argument against the decision? If they can, the agreement is real. If they cannot, the agreement is conformity.

### How do you measure whether your team has a groupthink problem? Track three things over 30 days: How many decisions were made with zero counterarguments raised? How many times did new information change a plan already in motion? How many times did a non-leader speak before the leader in a decision discussion? If the answers are "most," "never," and "rarely," your team has a groupthink problem.

### Can a team simulation actually prevent groupthink? Yes, and here is why: groupthink persists because teams never see the consequences. In daily work, the cost of suppressed dissent arrives months later and gets attributed to "market conditions" or "execution challenges." In a simulation, the cost arrives in minutes and gets attributed to exactly what caused it: "We did not share the information. We deferred to the loudest voice. We rushed to consensus." That direct cause-and-effect experience rewires how teams approach real decisions.

### Is groupthink always bad? In emergencies requiring instant coordinated action, rapid agreement can save time. But those situations are rare. In strategic decisions, product decisions, hiring decisions, and resource allocation — which is where teams spend 95% of their decision-making energy — groupthink produces consistently inferior outcomes. The speed of agreement is not worth the cost of poor analysis.

Read more about why your team defaults to the first idea for the anchoring bias that feeds groupthink. See how to get ideas from people who do not speak up for engaging the silent voices that groupthink suppresses. And explore why fast teams make better decisions, not worse for the difference between speed through alignment and speed through conformity.

Stop reading about groupthink. Experience it. Book a Save the Titanic simulation and find out how your team actually makes decisions under pressure. Over 6 million participants have faced the same choices the Titanic officers faced. The patterns that emerge will tell you everything you need to know about your team's susceptibility to groupthink — and exactly how to fix it.

**See a demo of Save the Titanic** →

**View results from organizations that broke the pattern** →

**Email us to discuss a groupthink simulation for your team** →

See What Your Team Does Under Real Pressure

3.5 hours. No slides. No lectures. Your team becomes Senior Officers on the Titanic and discovers how they actually work together. Book a demo to see how it works.