UPI Study › Courses › Project Management › Free lessons › Lesson 11.4 Free with a free account
Groupthink: Causes, Examples, and Prevention
Project Management · Chapter 11: Team Dynamics and Conflict ResolutionSection 11.4 · lesson 70 of 7312 min · free with a free account
Free preview
Create a free account to keep watching
It takes a minute and costs nothing. Your free account unlocks all of Chapter 1 and 3 more lessons of Project Management.
Lesson complete
Earn the 3 college credits for Project Management
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: Conflict Management and Resolution Strategies →← Stages of Team Development and Group BehaviorNext lesson: Conflict Management and Resolution Strategies →
In this lesson
Spot groupthink's conditions and symptoms and build safeguards into decisions.
- Define groupthink and the conditions Irving Janis linked to it
- Recognize symptoms such as self-censorship, rationalization and mindguards
- Match prevention techniques and governance safeguards to specific warning signs
- Evaluate the evidence for groupthink and keep safeguards proportionate
Free study notes
Get this lesson's notes by email
The key points and 4 practice questions with answers, in your inbox. One email, free.
One email. Unsubscribe in one click.
Transcript
Everything said in the video, section by section (1,641 words). Read along, or search it.
Opening Question
A Ten-Week Plan Approved in One Session
Meridian's review panel meets to approve a release plan, for the next version of its booking app. Omar, the sponsor, opens the meeting. The team has used this plan four times, he says, and he's completely confident in it. The plan allows five weeks to build, two to integrate the parts, two to test, and one to fix defects. Ten weeks. The clinics' deadline allows exactly ten. Rosa, the quality lead, has noticed that this release touches more components than earlier ones. She hesitates. The panel approves the plan in one session. How does a group of capable, friendly people approve a plan with no spare time at all?
Definition
Agreement Overriding Realistic Appraisal
Dana, Meridian's project manager, wasn't on the panel. Reading its record a week later, she recognizes a pattern. The name for it is groupthink: a pattern in which a cohesive group's drive for agreement overrides realistic appraisal of alternatives. Realistic appraisal means weighing a plan honestly against evidence: its costs, its risks, and the options that were set aside. The psychologist Irving Janis proposed the idea, drawing on case studies of group decisions. Groupthink isn't the same as agreement. Teams often agree because the plan is good. The concern is agreement sought for its own sake, ahead of the appraisal. And it's a proposed explanation, not a law of group behavior. Treat it as a set of warning signs.
Conditions
Cohesion, Insulation, Directive Leaders and Pressure
Janis described conditions that make the pattern more likely, without guaranteeing it. Four are easy to spot in a project meeting. High cohesion: members value the group's harmony, so disagreement feels like a threat to the relationship. This panel has worked together for years. Insulation from outside views: the group decides without hearing from people with different information, like testers, users, or other teams. Nobody outside the panel has seen this plan. Directive leadership: a leader signals the preferred answer early. Omar's confident opening turned the meeting into a search for support. He didn't intend that. But a remark like his changes what each member risks by speaking. Pressure or stress: a fixed deadline, or an announced commitment, makes a quick consensus feel like relief. Here, it's the clinics' date. Conditions aren't verdicts. A cohesive team under a deadline can still decide well. But each condition raises the importance of the checks.
Symptoms
Six Observable Warning Signs
Then come the symptoms: behaviors you can observe. Here are six that Janis described, and this meeting shows several. The illusion of invulnerability is a shared belief the plan can't seriously fail, resting on past success. Victor, the release manager, says: we've pulled this plan off four times. Rationalization explains doubts away with untested reasons. When Rosa starts to say integration might run long, someone answers: surely Omar has accounted for that. Shared stereotypes of outsiders are fixed, simple views of people outside the group, like calling reviewers slow, or critics negative, so their objections go unanswered. Self-censorship is keeping a doubt to yourself, to avoid friction. Rosa stops, and her silence is recorded as agreement. Pressure on dissenters means teasing, disapproval, or warnings of blame. Jun jokes that Rosa is worrying again, and the panel laughs. Mindguards shield the group from disturbing information. Afterward, Victor tells Rosa it would be unhelpful to raise schedule doubts before Omar meets the clinics. The symptoms feed each other. Silence looks like unanimity, which supports the illusion, and teasing teaches the rest to stay quiet. One quiet member may mean nothing. Several symptoms, with several conditions present, is a stronger signal.
Evidence
How Well Groupthink Is Supported
How well supported is groupthink? The evidence is mixed. Later research supports parts: cohesion combined with directive leadership matters, and members do withhold doubts. But the full chain, from conditions to symptoms to bad decisions, hasn't been consistently confirmed. Some studies don't find the links the model predicts. There's also a trap. After a decision goes badly, it's easy to find symptoms in the record, and call them the cause. Use the idea while a decision is still under way. In practice, one view says a checklist from an imperfect model is still worth using, because the checks are cheap, and honest challenge is defensible anyway. The other says treating it as settled can label ordinary agreement a disorder, and add rituals that waste time better spent on evidence about the plan. This lesson takes neither side. It teaches the warning signs, and holds the claims about cause lightly.
Quick Check
Dismissing the Test Lab's Findings
Quick check, with a different meeting. At a phase gate for a new handheld device, the test engineer reports that the battery tests are only half finished. The chair says the launch date is fixed. Another member adds: the test lab always finds problems, and is never satisfied. Which symptom is that remark? Pause, and decide. Shared stereotypes of outsiders. It dismisses the lab's findings by describing the people, not the results. Rationalization would be a line like: the remaining tests can be absorbed later. Self-censorship would be the engineer quietly dropping her concern. A decision to proceed with conditions would have kept the open tests visible.
Prevention Techniques
From Devil's Advocate to Pre-Mortem
Prevention techniques share one purpose: to make honest appraisal the default, not an act of courage. A devil's advocate is assigned to argue against the proposal, whatever their own view. Objections become a duty of the role. The cost: it can be played weakly, or resented. Independent sub-groups appraise the same question separately, then compare. One dominant view, or one mindguard, can't reach everyone. The cost is time and duplicated effort. Anonymous input collects views or estimates without names, before discussion begins. It protects against self-censorship and pressure on dissenters. In a very small team, though, phrasing can give the writer away. An outside challenge invites someone with no stake in the group's harmony to find weaknesses. It counters insulation and stereotypes, but only if the group takes the answers seriously. A pre-mortem is a session before approval, where everyone imagines the plan has already failed, and writes down why. It counters the illusion of invulnerability, for the cost of one short session.
Governance Safeguards
Rotating Critics, Minority Reports, Leaders Last
Techniques used by choice tend to fade under pressure, exactly when they're needed most. Governance changes make the safeguard the default. Rotating critic roles pass the duty of challenge from member to member, so nobody is cast as the permanent objector. A minority report is a short written dissent, attached to the decision record, so the objection survives, and can be reviewed later. And leaders speak last: the sponsor or chair gives a view only after everyone else, which removes the early signal behind directive leadership. Safeguards have limits too. Dissent can stall every decision. A devil's advocate can become a ritual everyone discounts. And a minority report nobody reads is just filing. So keep them proportionate to the stakes. The test of a safeguard is whether it brought new information or a better reason, not whether it produced an objection. And good process improves the odds of honest appraisal. It can't guarantee a good result.
Quick Check
Doubts Voiced Only in the Hallway
Quick check. On another Meridian team, doubts about a vendor's plan come up over coffee and in the hallway, but never once in the review meeting. Which technique answers that most directly? Pause, and decide. Anonymous input. Hallway doubts that never reach the meeting are self-censorship, and collecting concerns without names, before discussion, puts them on the table. A pre-mortem targets overconfidence, and an outside challenge brings in views from beyond the group. Both help, but neither removes the personal risk of speaking up.
Testing Assumptions
How Ten Weeks Became Twelve
Back to the release plan, and what actually happened. Integration took three weeks, and testing needed a second fix round. In words: total duration equals build, plus integration, plus test, plus fix time for every round. As planned: five plus two plus two plus one. Ten weeks, with zero spare. Testing an assumption means asking what happens if it's wrong. Integration at three weeks gives eleven: one week late. A second fix round alone also gives eleven. Both together give five plus three plus two plus two: twelve weeks, two weeks late. That's exactly what happened. The calculation takes minutes, but nobody was positioned to ask.
Prevention Plan
Three Days of Checks Against Two Weeks Late
Dana drafts a prevention plan for the next review, matching each technique to something the record showed. Anonymous input: each member writes concerns and phase estimates, unsigned, before the meeting. It answers Rosa's silence, and takes about half a working day. Independent sub-groups: two pairs estimate the schedule separately, and compare. It answers cohesion and the mindguard. About one day. A pre-mortem: imagine the release has already shipped late, and list why. It answers the illusion of invulnerability. Half a day. An outside challenge: a quality lead from another product team reviews the plan's assumptions. It answers insulation. One day. A rotating devil's advocate adds no extra time. The governance change: Omar speaks last, and any member may attach a minority report. Added time: half, plus one, plus half, plus one. Three working days. Against that stood two weeks late: ten working days. That's no promise the plan would have prevented the delay. It shows a small, known cost against a larger, unknown one. For a cheap, reversible decision, lighter checks would do.
Case Resolved
The Sponsor Speaks Last
Back to the question from the start. How do capable, friendly people approve a plan with no spare time? Not through bad intent. Cohesion, a confident sponsor, a fixed date, and no outside eyes made agreement easy, and appraisal hard. At the next review, Omar waits, and speaks last. The first thing on the table is Rosa's written estimate.
Key Takeaways
Spotting and Preventing Groupthink
To recap: groupthink is a cohesive group's drive for agreement overriding realistic appraisal. Watch for the conditions, like cohesion, insulation, a directive leader, and pressure, and for symptoms like self-censorship and mindguards. Match a technique to each warning sign, and make the main ones default through governance, like leaders speaking last. And keep safeguards proportionate: their test is whether they brought new information into the decision.
About Project Management at UPI Study
Project Management (Business 230) is a self-paced online course of 73 video lessons in 12 chapters, from starting and defining a project to planning, budgets, scheduling tools, proposals, contracts, execution, monitoring, closure, teams and certification. It carries a NCCRS credit recommendation for 3 semester credits.
Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Enroll now → Course details Download the syllabus All Business courses Every course with PRO →
Why take it here
Why students take Project Management with UPI Study
Where the credit goes
Universities that work with NCCRS
Project Management carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Thomas Edison State UniversitySigned partner
University of the PeopleSigned partner
Charter Oak State CollegeSigned partner
Strayer UniversitySigned partner
Columbia Southern UniversitySigned partner
Indiana TechSigned partner
Penn StateWorks with NCCRS
Southern New Hampshire UniversityWorks with NCCRS
SUNYWorks with NCCRS
+many more cooperating universitiesFind my college →Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.
FAQ
Questions students ask us
About Groupthink: Causes, Examples, and Prevention
What is groupthink in project decision-making?
What are mindguards in groupthink?
How does a pre-mortem help prevent groupthink?
Why should leaders speak last in a decision meeting?
About the Project Management course
How many college credits is Project Management?
How much does Project Management cost and what is included?
Which universities accept UPI Study credits?
How long does Project Management take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in Project Management.
73 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →