home / skills / coowoolf / insighthunt-skills / nominal-group-meeting

nominal-group-meeting skill

safe

/decision-thinking/nominal-group-meeting

This skill facilitates nominal group meetings to surface diverse opinions independently before discussion, reducing bias and improving decision quality.

npx playbooks add skill coowoolf/insighthunt-skills --skill nominal-group-meeting

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

3.3 KB

---
name: nominal-group-meeting
description: Use when meetings are dominated by the loudest voices, when seeking diverse perspectives on roadmaps or forecasts, or when groupthink is hindering decision quality
---

# 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*

Overview

This skill captures the Nominal Group Meeting framework to reduce groupthink and surface independent perspectives. It structures pre-meeting independent work, leader aggregation, and a focused discussion that only covers disagreements. Use it to preserve diverse input and make meetings efficient and decision-focused.

How this skill works

Participants receive prompts or data before the meeting and generate ideas, forecasts, or rankings privately, submitting them directly to the meeting leader. The leader aggregates responses, highlights consensus and variance, and convenes a short discussion meeting that focuses solely on areas of disagreement. Decisions are often made asynchronously after the discussion.

When to use it

When meetings are dominated by the loudest or most confident voices
When you need unbiased forecasts or independent estimates
When you suspect groupthink or pressure to conform
When you want meetings to be short and decision-focused
When seeking a wide range of ideas for roadmaps, forecasts, or risk assessments

Best practices

Send clear prompts and relevant data to participants well before the meeting
Explicitly ban reply-all and public drafting; require private submissions to the leader
Have the leader aggregate responses into summarized themes, stats, or ranked lists
Use the meeting only to explore variance, ask clarifying questions, and surface trade-offs
Adopt a reflective, curious tone in discussion: confirm statements rather than argue
Decide asynchronously when possible to avoid social pressure driving the outcome

Example use cases

Product roadmap prioritization where senior voices tend to dominate
Sales or revenue forecasting that benefits from independent estimates
Hiring shortlists where interviewers’ opinions should not anchor each other
Risk assessment sessions for a major launch to surface minority concerns
Prioritizing bug fixes or feature trade-offs across distributed teams

FAQ

How long should the independent work window be?

Long enough for thoughtful input—typically 24–72 hours depending on complexity and availability.

What if people ignore the private submission rule?

Reinforce norms and, if needed, remove public drafts. Make adherence part of meeting expectations and follow up privately with repeat offenders.