nominal-group-meeting
Nominal Group Meeting Framework
Overview
A meeting structure designed to eliminate groupthink and coercion by separating the discovery of ideas from the discussion of them. It ensures independent thinking and focuses meeting time solely on areas of disagreement.
Core principle: The best way to get someone's opinion is independently of other people's opinions.
The Process
┌─────────────────────────────────────────────────────────────────┐
│ 1. ASYNCHRONOUS DISCOVERY │
│ Send prompt/data to participants BEFORE the meeting │
│ No reply-all allowed │
├─────────────────────────────────────────────────────────────────┤
│ 2. INDEPENDENT OUTPUT │
│ Participants generate ideas/forecasts/ranks ALONE │
│ Submit directly to leader │
├─────────────────────────────────────────────────────────────────┤
│ 3. AGGREGATION │
│ Leader collates responses │
│ Identifies areas of AGREEMENT (skip) and DISAGREEMENT │
├─────────────────────────────────────────────────────────────────┤
│ 4. DISCUSSION ONLY MEETING │
│ Group convenes SOLELY to discuss variance in opinions │
│ Reflect back what people say (curiosity over coercion) │
├─────────────────────────────────────────────────────────────────┤
│ 5. DECISION │
│ Often asynchronous, after discussion │
└─────────────────────────────────────────────────────────────────┘
Key Principles
| Do | Don't |
|---|---|
| Get opinions independently | Brainstorm live in the room |
| Use meetings for discussion only | Use meetings for discovery |
| Focus on disagreements | Seek "alignment" as primary goal |
| Reflect back to ensure heard | Let people interrupt |
Common Mistakes
- Brainstorming live in the room (allows anchoring)
- Letting confident people dominate
- Seeking consensus as the goal (breeds coercion)
Source: Annie Duke (First Round Capital, Decision Science Expert) via Lenny's Podcast
More from coowoolf/insighthunt-skills
gardening-mindset
Use when dealing with ecosystems, network effects, or high-uncertainty environments where the right answer cannot be known in advance, when rigid planning consumes more value than it creates
45gamification-triad
Use when designing retention mechanisms, habit loops, or auditing why users drop off despite engaging with core features, to structure gamification beyond superficial badges
44three-layer-agent-stack
Use when building AI-powered products or agents, when raw model intelligence isn't enough to solve user problems, or when designing the architecture for agentic workflows
15minimum lovable product (mlp)
In an era where AI lowers the cost of building software, viability is obsolete. The differentiator is joy and emotional connection. Prioritize "Wow" over "Aha"—brand is product interaction.
14curiosity-loops
Use when facing a significant decision (career pivot, product direction, technical choice) and feeling stuck or indecisive, when seeking contextual advice rather than generic recommendations
13pre-mortem-kill-criteria
Use before launching products or signing contracts, when needing to combat sunk cost fallacy, or when standard pre-mortems fail to change behavior
13