What This Template Is For
Most brainstorming sessions fail. The typical format (gather people in a room, say "let's come up with ideas," and start talking) produces predictable results: the loudest person dominates, the first idea anchors everyone else, and the group converges too early on a mediocre solution. Research from organizational psychology confirms this. Unstructured group brainstorming consistently underperforms individuals working alone and then combining their ideas.
This template fixes the structural problems. It uses a diverge-then-converge format with silent ideation, timed rounds, and structured evaluation. The approach draws from the Design Thinking tradition, where ideation is a distinct phase with its own rules, separated from problem definition and solution evaluation.
The template works for any product ideation challenge: generating feature ideas, exploring solutions to a customer problem, finding new market opportunities, or reimagining an existing workflow. For problems that need rapid visual prototyping alongside ideation, pair this with the Crazy Eights template. If you are running a broader discovery process, this brainstorming session fits naturally into the divergent phase of the Double Diamond framework.
How to Use This Template
- Define a clear problem statement before the session. The single biggest determinant of brainstorming quality is the prompt. "How might we improve onboarding?" is too broad. "How might we reduce the 40% drop-off between account creation and first project setup?" is specific enough to generate useful ideas.
- Invite 4-8 participants. Include diverse perspectives: PM, design, engineering, customer-facing roles. Avoid inviting more than 8 people. Beyond that number, social loafing increases and individual contribution decreases.
- Block 60-90 minutes. The session has four phases: framing (10 min), silent ideation (20 min), sharing and building (20 min), and voting and discussion (20-30 min).
- Prepare materials. Sticky notes (physical or digital), markers, a timer, and a voting mechanism (dot stickers or digital votes). Each participant needs their own stack of notes.
- The facilitator does not ideate. The facilitator's job is to keep time, enforce rules, and manage the sharing process. If the facilitator also generates ideas, they tend to unconsciously steer the group toward their own concepts.
- Set quantity over quality as the explicit goal. Tell the group: "We want 50+ ideas. Bad ideas are welcome. Judgment comes later."
The Template
Session Setup
| Field | Details |
|---|---|
| Problem statement | [Clear, specific How Might We question] |
| Date | [Date] |
| Facilitator | [Name] |
| Participants | [Names and roles, 4-8 people] |
| Context shared in advance? | [Yes / No. Link to brief if Yes] |
| Tools | [Sticky notes + markers / Miro / FigJam] |
Phase 1: Framing (10 minutes)
Goal: Ensure everyone understands the problem and the constraints.
Facilitator script:
- ☐ Welcome and state the session goal: "We are here to generate as many ideas as possible for [problem statement]."
- ☐ Share 2-3 minutes of context: the user problem, relevant data, and any constraints (budget, timeline, technical)
- ☐ Read the brainstorming rules aloud:
- Defer judgment. No critiquing ideas during ideation.
- Go for quantity. 50+ ideas is the target.
- Build on others' ideas. "Yes, and..." not "Yes, but..."
- One idea per sticky note.
- Encourage wild ideas. They can be refined later.
- ☐ Confirm the problem statement is visible to everyone
- ☐ Answer clarifying questions about the problem (not about potential solutions)
Problem Statement:
How might we [specific challenge]?
Context Summary:
| Context | Details |
|---|---|
| User segment | [Who are we solving for?] |
| Current pain | [What is broken or missing?] |
| Key data | [Relevant metric, quote, or finding] |
| Constraints | [Budget, timeline, technical limits] |
Phase 2: Silent Ideation (20 minutes)
Goal: Each participant generates ideas independently, without influence from others.
Rules:
- No talking during this phase
- One idea per sticky note
- Write a short title + 1-2 sentence description on each note
- Sketches are encouraged (even rough ones communicate better than text alone)
- Set a timer. At the 10-minute mark, announce "halfway" to keep energy up
- Target: 8-15 ideas per person
Facilitator notes:
- ☐ Start the 20-minute timer
- ☐ Announce "halfway" at 10 minutes
- ☐ If energy drops, suggest a quick prompt: "Think about ideas that would be impossible with today's technology" or "What would a competitor never do?"
- ☐ Call time at 20 minutes
Idea Count:
| Participant | Ideas Generated |
|---|---|
| [Name] | |
| [Name] | |
| [Name] | |
| [Name] | |
| [Name] | |
| Total |
Phase 3: Sharing and Building (20 minutes)
Goal: Make all ideas visible to the group and generate new ideas by combining or extending existing ones.
- ☐ Each participant places their sticky notes on the board (30 seconds each to post, no presenting)
- ☐ Facilitator reads through ideas one by one (5-10 seconds per idea, no discussion yet)
- ☐ After the read-through, open a 10-minute "build" round: participants write new ideas inspired by what they saw
- ☐ Group similar ideas together as they emerge (light clustering, not formal affinity mapping)
Clustering Notes:
| Cluster Theme | Idea Count | Notable Ideas |
|---|---|---|
| [Theme] | [Standout ideas in this group] | |
| [Theme] | ||
| [Theme] | ||
| [Theme] | ||
| [Theme] |
Phase 4: Voting and Discussion (20-30 minutes)
Goal: Narrow the field to the most promising ideas for further exploration.
Voting round:
- ☐ Each participant gets 5 votes (dot stickers or digital votes)
- ☐ Votes can be distributed however the participant chooses (all 5 on one idea, or spread across 5)
- ☐ Vote silently. No lobbying or explaining before voting.
- ☐ Tally votes. Identify the top 5-8 ideas by vote count.
Discussion round:
- ☐ For each top-voted idea, the original author explains it in 60 seconds
- ☐ Group discusses feasibility, impact, and effort for each
- ☐ Rate each idea on two dimensions: User Impact (H/M/L) and Feasibility (H/M/L)
- ☐ Select 2-3 ideas to move into validation or prototyping
Top Ideas:
| Rank | Idea | Votes | Impact | Feasibility | Next Step |
|---|---|---|---|---|---|
| 1 | [Idea] | H/M/L | H/M/L | [Prototype / Research / Spike] | |
| 2 | [Idea] | H/M/L | H/M/L | ||
| 3 | [Idea] | H/M/L | H/M/L | ||
| 4 | [Idea] | H/M/L | H/M/L | ||
| 5 | [Idea] | H/M/L | H/M/L |
Action Items
| Action | Owner | Deadline |
|---|---|---|
| Write up top ideas with full descriptions | [Name] | [Date] |
| Create prototypes for the top 2-3 ideas | [Name] | [Date] |
| Share results with stakeholders not in the session | [Name] | [Date] |
| Schedule validation sessions for top ideas | [Name] | [Date] |
Filled Example: TaskFlow Onboarding Ideation
Session Setup
| Field | Details |
|---|---|
| Problem statement | How might we reduce the 40% drop-off between account creation and first project setup in TaskFlow? |
| Date | March 5, 2026 |
| Facilitator | Sonia Park (Design Lead) |
| Participants | Raj (PM), Maya (Research), Luke (Eng), Kim (CS), Dev (Designer) |
| Context | Heap data shows 40% of new users abandon after account creation. Interviews reveal users feel overwhelmed by the empty dashboard. |
Phase 2 Results
| Participant | Ideas Generated |
|---|---|
| Raj | 11 |
| Maya | 14 |
| Luke | 9 |
| Kim | 12 |
| Dev | 13 |
| Total | 59 |
Top Ideas After Voting
| Rank | Idea | Votes | Impact | Feasibility | Next Step |
|---|---|---|---|---|---|
| 1 | "First project wizard" with 3 pre-built templates | 9 | H | H | Prototype this week |
| 2 | Interactive product tour with tooltips on key actions | 7 | H | M | Design spike |
| 3 | "Copy a demo project" button on empty dashboard | 6 | H | H | Prototype this week |
| 4 | Onboarding checklist sidebar (complete 5 steps, earn a badge) | 5 | M | H | Backlog for Q2 |
| 5 | AI-generated project based on user's industry during signup | 4 | H | L | Research feasibility |
The team moved ideas #1 and #3 into prototyping immediately because both scored High on impact and feasibility. Idea #5 was flagged as a potential Q3 initiative pending an engineering feasibility spike.
Key Takeaways
- Silent ideation before group sharing prevents anchoring and produces more unique ideas
- Define a specific problem statement before the session. Vague prompts produce vague ideas.
- Target 50+ ideas across the group. Quantity leads to quality in brainstorming
- Vote silently, then discuss. This prevents the loudest voice from dominating evaluation
- Move the top 2-3 ideas into prototyping or validation within the same week to maintain momentum
About This Template
Created by: Tim Adair
Last Updated: 3/5/2026
Version: 1.0.0
License: Free for personal and commercial use
