Practical frameworks for making better decisions as a team — from small groups to large organizations. Covers facilitation techniques, voting methods, consensus-building, and avoiding groupthink.
- Why Group Decisions Are Hard
- Frameworks
- Facilitation Guide
- Avoiding Groupthink
- Remote Team Decisions
- Templates
- Resources
- License
| Challenge | Description |
|---|---|
| Groupthink | Desire for harmony suppresses critical thinking |
| HiPPO effect | Highest Paid Person's Opinion dominates |
| Social loafing | Individuals contribute less in groups |
| Information cascades | Early speakers anchor the group |
| Diffusion of responsibility | "Someone else will raise the concern" |
| Status bias | Senior voices carry disproportionate weight |
| Confirmation bias | Group reinforces shared beliefs, ignores contradicting evidence |
The paradox: Groups have access to more information and perspectives than individuals, but systematic biases often prevent them from using this advantage.
Origin: Edward de Bono
Everyone wears the same hat at the same time, preventing adversarial dynamics.
| Hat | Focus | Key Question |
|---|---|---|
| Blue | Process | "What's our thinking process? What hat next?" |
| White | Facts | "What do we know? What data do we need?" |
| Red | Emotions | "What does my gut say? Initial reactions?" |
| Black | Risks | "What could go wrong? Why might this fail?" |
| Yellow | Benefits | "What are the advantages? Best case?" |
| Green | Creativity | "What alternatives exist? What else is possible?" |
Process:
- Blue: Frame the question and process
- White: Share facts and data
- Red: Quick gut reactions (no justification needed)
- Yellow: Explore benefits and opportunities
- Black: Identify risks and weaknesses
- Green: Generate alternatives and creative solutions
- Blue: Summarize and decide
Origin: RAND Corporation
Purpose: Get expert consensus without the biases of face-to-face discussion.
Process:
Round 1: Each expert provides independent estimate/opinion (anonymous)
↓
Aggregate and share results (mean, range, key arguments)
↓
Round 2: Experts revise estimates based on group feedback (still anonymous)
↓
Repeat until convergence (typically 2-4 rounds)
↓
Final: Report consensus range and key disagreements
When to use: Forecasting, strategic planning, when expertise matters and groupthink risk is high.
Process:
- Silent generation (5-10 min) — Each person writes ideas independently
- Round-robin sharing — Each person shares one idea at a time (no discussion yet)
- Clarification — Group discusses each idea briefly (understanding, not debating)
- Individual ranking — Each person privately ranks their top 5 ideas
- Tally and discuss — Aggregate rankings, discuss top-voted ideas
Why it works: Silent generation prevents anchoring. Round-robin ensures equal voice. Private ranking prevents conformity.
Origin: Intel (Andy Grove), popularized by Amazon
Protocol:
- Everyone has a voice and is expected to share their honest opinion
- Debate is vigorous, fact-based, and respectful
- Once a decision is made, everyone commits fully — even dissenters
- No passive-aggressive undermining, no "I told you so"
- The decision-maker owns the outcome
Template:
## Decision: [Topic]
**Decision-maker:** ____
**Date:** ____
### Perspectives shared:
| Person | Position | Key Argument |
|--------|---------|-------------|
| | For/Against/Alternative | |
| | | |
| | | |
### Decision: ____
### Reasoning: ____
### Commitment:
All participants commit to supporting this decision fully.
Review date: ____Origin: Intuit, Atlassian
| Role | Description | How Many |
|---|---|---|
| Driver | Drives the process, gathers input, ensures a decision is made | 1 |
| Approver | Has final decision authority | 1 (exactly one) |
| Contributors | Provide input, knowledge, expertise | Several |
| Informed | Notified after the decision | As needed |
## DACI: [Decision]
| Role | Person(s) |
|------|-----------|
| Driver | |
| Approver | |
| Contributors | |
| Informed | |
### Context: ____
### Options:
1.
2.
3.
### Recommendation: ____
### Decision: ____
### Communication plan: ____Origin: Sociocracy, Holacracy
Different from consensus: Consensus asks "Does everyone agree?" Consent asks "Can everyone live with this?"
Process:
- Proposal — Someone presents a proposal
- Clarifying questions — Only questions, no opinions yet
- Reactions — Each person shares their reaction (round-robin)
- Amend — Proposer adjusts based on reactions
- Consent round — Each person states: "I have no objection" or raises a specific objection
- Objection integration — Work through objections to modify proposal until no objections remain
An objection must be: "I believe this will harm the team/org because [specific reason]" — not "I prefer something different."
Process:
- Post all options visibly (whiteboard, sticky notes, shared doc)
- Each person gets a fixed number of dots (typically 3-5)
- Place dots on your preferred options (can stack on one or spread)
- Count dots — discuss top-voted items
Variants:
- Weighted dots: Different colors for different priorities
- Budget dots: Each dot = $10K budget allocation
- Impact/effort dots: One color for impact, another for effort
Process:
- Assign 1-2 people the explicit role of "Devil's Advocate"
- Their job: Find every flaw, risk, and weakness in the proposal
- The team must address each objection before proceeding
- Rotate the role so no one is permanently "the critic"
Rules:
- Devil's Advocate is a respected role, not a punished one
- Objections must be specific and reasoned
- The team must genuinely consider each objection
- Thank the Devil's Advocate afterward
Origin: Gary Klein
Setup: "Imagine it's one year from now. This project has failed spectacularly. Why?"
Process:
- Frame: "The project launched and failed. We're looking back."
- Silent writing (5 min): Each person lists reasons for failure
- Round-robin: Share one reason at a time
- Cluster similar items
- Vote on most likely/impactful failure modes
- Create mitigation plans for top risks
Why pre-mortem beats brainstorming risks:
- Gives permission to voice concerns
- Prospective hindsight improves prediction by 30%
- Removes stigma of being "negative"
Process:
- Define the proposition — A clear, debatable statement
- Assign sides — Randomly assign "for" and "against" (regardless of personal belief)
- Preparation (10 min) — Each side builds their case
- Opening statements (3 min each)
- Rebuttal (2 min each)
- Open discussion (10 min)
- Individual reflection — Each person writes their actual position
- Decision
Why random assignment works: It forces people to argue positions they don't hold, revealing new perspectives and weakening confirmation bias.
- Clear decision statement (what are we deciding?)
- Right people in the room (decision-maker, contributors)
- Pre-read materials sent 24-48 hours before
- Choose the right decision method for the situation
- Time-boxed agenda
| Phase | Time | Facilitator Actions |
|---|---|---|
| Frame | 5 min | State the decision, method, and time box |
| Input | 15-30 min | Ensure all voices heard; prevent HiPPO |
| Discuss | 15-20 min | Facilitate, don't dominate; ask clarifying questions |
| Decide | 5-10 min | Apply chosen method; confirm the decision |
| Commit | 5 min | State decision, owners, next steps, review date |
| Technique | When to Use |
|---|---|
| Round-robin | Ensure everyone speaks |
| Silent writing first | Prevent anchoring |
| Parking lot | Capture off-topic but valid points |
| Time-boxing | Prevent analysis paralysis |
| "What I heard" | Reflect back to confirm understanding |
Irving Janis's symptoms of groupthink:
- Illusion of invulnerability
- Collective rationalization
- Belief in inherent morality
- Stereotyping outsiders
- Pressure on dissenters
- Self-censorship
- Illusion of unanimity
- Self-appointed mind guards
Prevention strategies:
| Strategy | How |
|---|---|
| Assign Devil's Advocate | Rotate the role each meeting |
| Leader speaks last | Prevent anchoring to authority |
| Anonymous input | Use surveys or written submissions first |
| Invite outsiders | Fresh perspective breaks echo chamber |
| Split into subgroups | Independent analysis, then reconvene |
| Reward dissent | Publicly thank people who challenge the group |
| Separate idea generation from evaluation | Brainstorm first, critique later |
## Async Decision: [Topic]
**Driver:** ____ | **Approver:** ____ | **Deadline:** ____
### Context
[Background information]
### Options
1.
2.
3.
### My recommendation: ____
### Input requested from:
- @person1 — [specific question]
- @person2 — [specific question]
- @person3 — [specific question]
### Responses:
[Team members add their input below]
### Decision: ____
### Date decided: ____| Need | Tool Type |
|---|---|
| Async discussion | Shared doc with comments, Slack thread |
| Voting | Poll tool, dot voting in shared whiteboard |
| Anonymous input | Survey tool, anonymous form |
| Structured debate | Video call with timer + moderator |
## Decision Rights: [Team/Organization]
| Decision Type | Who Decides | Who's Consulted | Who's Informed |
|--------------|------------|-----------------|----------------|
| Product features | | | |
| Hiring | | | |
| Budget > $X | | | |
| Architecture | | | |
| Process changes | | | |
| Customer escalations | | | |Books:
- Decisive — Chip & Dan Heath
- Superforecasting — Philip Tetlock
- Wiser — Cass Sunstein & Reid Hastie
- The Wisdom of Crowds — James Surowiecki
- Thinking in Bets — Annie Duke
For scenario-based group decision exercises and proven decision principles, explore KeepRule Scenarios — interactive decision-making practice for individuals and teams.
Have a group decision technique to add? PRs welcome.
MIT License — see LICENSE for details.