The officers on the Titanic weren't incompetent. They were the most experienced maritime professionals available. They received iceberg warnings. They discussed speed. And they chose to keep going.
Two hours later, 1,514 people were dead.
What happened wasn't a lack of information or skill. It was a group of capable people, in a room under pressure, collectively suppressing the doubts they each held privately. That's groupthink. And if you've ever watched a room full of smart people ratify a bad decision because nobody wanted to be the one to push back — you've seen it too.
What Groupthink Actually Is
Groupthink isn't stupidity. It's social pressure winning over individual judgment.
Psychologist Irving Janis identified the pattern in 1972 after studying disasters like the Bay of Pigs invasion. He found that the common thread wasn't a lack of smart people in the room. It was a set of social dynamics that made disagreement feel more dangerous than silence.
Five conditions appear in every groupthink situation. First, a strong team identity that values harmony over truth — the desire to stay cohesive overrides the willingness to dissent. Second, a leader who signals the preferred answer before the discussion ends — whether deliberately or not. Third, external pressure — a deadline, a competitor, a crisis — that makes speed feel more important than accuracy. Fourth, insulation from outside perspectives — the same group, in the same room, making the same assumptions. Fifth, no formal mechanism for dissent — no process that makes it safe to say "I think we're wrong."
When all five conditions are present, smart teams produce catastrophically bad decisions. Consistently.
Four Groupthink Examples That Changed Industries
The Titanic (1912). The ship received six iceberg warnings the night of April 14th. The crew was aware of the ice fields ahead. The Titanic pressed on at near-full speed. The belief that the ship was unsinkable — reinforced by ownership, press, and the crew's own confidence — made it socially impossible for anyone to successfully challenge the decision to maintain speed. The warnings were rationalized away. The dissenters deferred. The collision was, in many ways, predetermined by the room's social dynamics, not the iceberg.
Leadership Lessons from the Titanic That Still Apply explores five specific failure patterns from the real disaster that still show up in modern organizations every week.
NASA Challenger (1986). Engineers at Morton Thiokol knew the O-ring seals on the solid rocket boosters failed in cold temperatures. The night before launch, they recommended delaying. NASA managers pushed back. Under pressure, the recommendation was reversed. The launch went forward. The shuttle broke apart 73 seconds after liftoff. The post-disaster investigation found that the technical evidence against launch was available and was suppressed by organizational pressure to proceed.
Kodak (1975). Kodak engineer Steve Sasson invented the first digital camera. His team presented it to management. The response: "That's cute, but don't tell anyone about it." Kodak's leadership knew digital photography would disrupt film. Their solution was to suppress it internally while their core business existed. By the time they responded seriously to digital, the market had moved past them. The team that built the future couldn't get the present to hear them.
Blockbuster (2000). Netflix approached Blockbuster with an acquisition offer for $50 million. Blockbuster's leadership team laughed them out of the room. The decision wasn't irrational given what they knew — but the room lacked anyone with standing to credibly challenge the assumption that the video rental model was durable. Dissenting voices existed; they simply couldn't be heard in that room at that moment.
The Conditions Your Team Is Already Creating
You don't need to be crewing a ship or running a billion-dollar company to create groupthink conditions. They form naturally in any team under pressure.
Think about your last major decision meeting. Did the most senior person share their view first? Did anyone push back after that? Did the discussion feel like genuine deliberation, or like a process of arriving at the obvious conclusion together?
Most teams confuse agreement with alignment. Agreement is when people stop arguing. Alignment is when people genuinely share the same understanding. Groupthink produces agreement. It rarely produces alignment.
Why Your People Won't Speak Up and How to Fix It addresses the psychological safety dimension of this — the individual-level experience of what it costs to be the voice in the room that disagrees.
How the Save the Titanic Experience Breaks Groupthink
The Save the Titanic simulation is, at its core, a live groupthink experiment.
It creates all five groupthink conditions deliberately. There's a tight, cohesive team. There's a Captain character who represents authority. There's extreme time pressure. The team is insulated — no outside input beyond the scenario. And there's no formal dissent mechanism at the start.
Then it forces teams to confront the consequences.
Information in the simulation is distributed across roles. No one participant has the full picture. The only way to get the right answer is to share information across the group — which means someone has to speak up even when what they know contradicts the current direction.
The Stop Killing Ideas technique changes the dynamic. When every idea gets a physical acknowledgment before evaluation — a clap, a table slap — the social cost of contributing drops. Ideas reach the surface that would otherwise stay buried.
The debrief makes the invisible visible. "Who in this room had the idea that could have changed the outcome? When did you decide not to say it? What stopped you?" These are questions that rarely get asked in corporate settings. Teams that go through this experience start asking them at their real meetings.
ArcelorMittal ran 710 leaders through the experience in partnership with Duke Corporate Education. The result: 30-40% faster decisions. That speed came from building teams that could surface and act on dissenting information instead of suppressing it.
What Breaking Groupthink Actually Requires
Breaking groupthink isn't about telling people to speak up. People already know they should speak up. The problem is the social architecture of most teams makes silence safer than speaking.
What breaks groupthink is changing the conditions. Explicit process that normalizes challenge to authority. Information structures that require cross-sharing rather than allowing hoarding. A debrief practice that asks what was heard and what was suppressed. And a leader who models genuine uncertainty — who shows the team what it looks like to hold an idea loosely and invite contradiction.
See how we build these conditions into a 3.5-hour team experience and what teams look like on the other side.
Read next: Why Your Team Waits for Permission to Act