Your 'Aligned' Product Team Is Showing All 8 Symptoms of Groupthink
Irving Janis published his groupthink theory in 1972 after studying foreign policy disasters: Bay of Pigs, Pearl Harbor, Vietnam. His finding: highly cohesive groups suppress dissent, overestimate their own competence, and rationalize warning signs. The stronger the group identity, the stronger the pressure to conform.
Janis wasn’t writing about product teams.
The 8 Symptoms, Translated
Illusion of invulnerability. “Our competitor can’t catch us. We have a two-year head start.” Excessive optimism that blinds the team to risk.
Collective rationalization. “The beta users complained about onboarding, but they’re not our target persona.” Dismissing contradictory evidence.
Belief in inherent morality. “We’re making the world more open and connected.” Assuming the mission justifies any decision.
Stereotyping outsiders. “They just don’t get the vision.” Dismissing critics as uninformed rather than informative.
Direct pressure on dissenters. “Are you not a team player?” The PM who questions the roadmap gets sidelined.
Self-censorship. The PM who has doubts stays quiet because everyone else seems aligned. Silence mistaken for agreement.
Illusion of unanimity. “Everyone’s on board.” Nobody objected, so there must be consensus. Silence isn’t consent.
Mindguards. Certain team members protect the group from contrary information. “I wouldn’t bring that up — it’ll derail the conversation.”
The “Strong Culture” Trap
Strong product cultures are especially vulnerable. The things that make a team effective — shared values, trust, identity — also make dissent costly. When everyone believes in the mission, questioning it feels like betrayal.
“Disagree and commit” became a mantra, but most orgs only do the second half.
Antidotes That Actually Work
Janis proposed structural fixes, not cultural ones. They translate cleanly:
- Assign a devil’s advocate — and rotate the role. One person per planning cycle whose job is to argue against consensus. Rotate it so nobody gets typecast.
- Bring in an outside voice. Someone from a different team or domain. Show them the plan and ask: “What are we missing?”
- Separate generation from evaluation. Don’t brainstorm solutions and evaluate them in the same meeting.
- Make dissent structured. A prioritization matrix that forces explicit tradeoffs is an anti-groupthink device. Groupthink hates forced choices.
At Comcast, I reduced scope creep by 25%. Not by saying “no” harder. By making tradeoffs explicit in a forum where dissent was structured. The biweekly demo made silent disagreement unsustainable. When a stakeholder saw working software that didn’t match expectations, they had to speak up.
Groupthink and AI Agents
AI agents introduce a new risk: the agent is the ultimate conformist. It doesn’t have dissenting instincts. It won’t push back on a bad plan unless explicitly prompted. A human team with groupthink tendencies, augmented by agents that amplify consensus, is a decision-making disaster waiting.
The fix: instrument agents to surface uncertainty and alternatives. “Here’s the proposal. Now give me three reasons it might fail.” If your agent can’t do that, it’s part of the problem.
Your team might be aligned. It might also be in groupthink. The difference is invisible from inside. I help product orgs tell which one they’re in — before the roadmap pays for the answer. s@spencervaradi.com.