Brainstorming session template

TL;DR: Unstructured brainstorming sessions fail because they default to groupthink and allow dominant voices to drown out quieter contributors. To run a session that leads to shipped features, you need a structured agenda that balances individual quiet time with group collaboration. Using an AI notepad like Granola allows you to stay fully present as a facilitator while automatically capturing and organizing every idea into actionable next steps. The templates and step-by-step agenda below are ready to copy into your next session.

Most brainstorming sessions end with a whiteboard full of sticky notes and a vague agreement to "document this later." That documentation rarely happens. The core problem is structural: teams treat idea generation and idea capture as two separate jobs, and the person running the session cannot do both at once.

Why most brainstorming sessions fail

No structure means no follow-through

A session without a clear agenda devolves into circular conversation. Without a defined path from idea generation to decision-making, teams loop back to the same two or three suggestions while avoiding harder trade-offs. The whiteboard fills up, someone says "great energy in the room today," and two days later no one can remember which of those ideas was actually prioritized or why. Without a structured outlet, creative energy produces theater rather than product decisions.

Ideas get lost in the conversation

The physical capture problem is well-documented but underestimated. Whiteboards get erased before photos are taken. Sticky notes lose their surrounding context when photographed.

Typed notes miss the qualitative texture of how an idea was described, the follow-up question that sharpened it, or the moment when two separate threads merged into something useful. A facilitator who simultaneously guides discussion and types cannot capture both the idea and the conversation that gave it meaning.

Product managers running customer research each week recognize this tension from discovery work. The same note-taking versus listening tradeoff that limits interview quality also limits ideation quality. You cannot read the room and document it at the same time.

Dominant voices drown out quieter contributors

Production blocking occurs when only one person can speak at a time, which forces everyone else to wait, forget their ideas, or self-censor. Combined with evaluation apprehension, the tendency to hold back ideas when uncertain how they will land, this dynamic consistently advantages extroverts and senior voices while suppressing contributions from quieter team members. The result is a session where a small number of vocal participants generate most of the ideas while others nod along.

What makes a brainstorming session actually work

High-impact ideation sessions share four structural elements: preparation, individual ideation, group collaboration, and decision-making. Each phase solves a specific failure mode from the previous section.

Clear goals and constraints

Creativity requires boundaries. Design Sprint methodology dedicates focused time to building a shared understanding of the problem space before anyone generates solutions. The same principle applies here: define the scope of the session before opening the floor to ideas.

A clear challenge statement answers three questions:

• What problem are we solving? State it in specific, observable terms.
• What is out of scope? Constraints focus the team and prevent circular conversations.
• What does a good outcome look like? Define success so you can recognize it when the session ends.

Without these boundaries, teams generate broad ideas that are hard to evaluate against each other and even harder to assign to an owner.

Structured ideation frameworks

Frameworks force the brain out of default patterns. When teams move through structured exercises rather than free-association conversation, every participant follows the same constraints. This levels the contribution field and prevents the anchoring effect where the first idea spoken becomes the gravitational center of the discussion.

Frameworks also create equal participation by design. A silent writing phase gives quieter contributors time to develop ideas fully before any group sharing begins. Ideas arrive at the table on their own merits rather than filtered through the confidence of the person delivering them.

Automatic capture of every idea

The facilitator's primary job is to guide the energy of the room, not to act as a scribe. When a facilitator stops the discussion to type out a suggestion, they lose eye contact, miss body language, and interrupt the creative momentum that structured sessions build. The capture mechanism needs to work without demanding the facilitator's attention.

This is where AI-enhanced notes change the dynamic. When transcription happens automatically in the background, the facilitator can jot rough keywords or themes as anchors and let the tool fill in the full context afterward.

Step-by-step brainstorming session agenda

This agenda maps to the four-phase framework above. Copy it directly into your next session.

1. Set the challenge (5 minutes)

Open the session by writing the challenge statement on the shared screen or whiteboard. Read it aloud and invite one clarifying question. Do not open the floor to solutions yet. The goal of this phase is alignment, not ideation.

A well-formed challenge statement follows this structure: "We need to [solve problem] for [specific user] so that [measurable outcome]." Keep the objective visible throughout the session. When conversations drift, the written challenge statement gives you a physical anchor to redirect the group. Clear upfront objectives make a session more likely to produce actionable outcomes.

2. Individual ideation (10 minutes)

Set a timer and ask every participant to write their ideas independently, in silence. No sharing, no discussion, no reactions to what others are writing. This phase directly addresses production blocking and evaluation apprehension by ensuring every person generates their ideas before hearing anyone else's. Ask participants to aim for quantity over quality during this phase.

3. Share and build (20 minutes)

Each person shares their ideas in a round-robin format. The facilitator captures themes, not transcripts. After each share, the group looks for ideas to combine or build upon rather than immediately evaluating which are best.

Group collaboration works best when it starts with additive thinking rather than critical evaluation. Phrases like "that connects to what [name] said about..." signal productive combination. Phrases like "yes, but..." signal premature convergence and slow the momentum of the sharing phase.

4. Group and prioritize (15 minutes)

Cluster similar ideas into three to five themes and give each cluster a label. Then run dot voting: each participant gets three to five dots and allocates them to the ideas they believe deliver the highest impact. Alternatively, map ideas onto a two-by-two impact-effort matrix to identify quick wins versus longer-horizon bets.

5. Define next actions (10 minutes)

Assign a clear owner, a specific deliverable, and a deadline to every prioritized idea before the session ends. No idea leaves the room as "someone should look into this." The session's value is only realized when the output maps to a person, a task, and a date.

Good action items follow the format: "[Owner] will [specific action] by [date] to [measurable outcome]." This phase connects the creative output of the session to your team's existing tracking tools, whether that is a Jira backlog, a Notion database, or a product roadmap.

Classic ideation frameworks to try

Different sessions call for different frameworks. The table below summarizes when to use each one based on your team's goals.

SCAMPER method

SCAMPER stands for Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, and Reverse. Apply each prompt to your existing product or feature to generate specific improvement ideas. "What could we substitute in our onboarding flow?" produces more targeted responses than "How could we improve onboarding?" because the constraint forces concrete thinking rather than open-ended speculation. SCAMPER ensures teams consider multiple angles systematically rather than anchoring on the most obvious solution first.

How Might We questions

How Might We (HMW) reframes a user pain point as an open-ended design challenge. Take a problem statement like "Enterprise users abandon setup on day three" and convert it to "How might we make the day-three experience feel like a natural continuation rather than a new task?" The open framing invites creative responses from wider angles than a closed problem definition allows. HMW questions work well as the framing mechanism for other techniques, including Crazy 8s.

Crazy 8s

Give each participant an eight-panel template and set a timer for eight minutes. Each panel gets one sketch or written idea. With only one minute per idea, participants do not have time to critique, refine, or overthink. They generate something in each box and move on. The time constraint forces volume over perfection and produces diverse ideas that would never surface in a standard verbal discussion.

Six Thinking Hats

Edward de Bono's framework divides brainstorming into six distinct perspectives: factual (white), emotional (red), critical (black), optimistic (yellow), creative (green), and process (blue). Each participant considers the problem through a single lens at a time, preventing the common dynamic where critical analysis shuts down creative thinking before it has room to develop.

How to capture ideas without losing momentum

Why manual note-taking breaks flow

Every time a facilitator looks down to type, they break the visual connection with the room. Participants notice the pause, and the creative momentum that structured sessions build dissipates in the gap. Manual notes from a 60-minute session also require significant time afterward to organize into a format that stakeholders can act on, which makes brainstorming feel expensive and causes teams to skip the synthesis step entirely.

Using Granola to auto-capture brainstorms

Granola takes a different approach: you guide which themes matter through your rough notes, and Granola's AI enhancement uses those anchors to fill in the full context from the transcript afterward. Type "pricing objections" and Granola finds every moment in the session where pricing came up and adds the relevant quotes. Leave the notepad blank and get a general summary. The quality of the output reflects the quality of your rough notes.

Data privacy checklist for brainstorms involving sensitive customer feedback:

• Inform participants: Use Granola's automated in-chat notification to let everyone know transcription is active at the start of the session.
• Use the watermark: Enable the Granola watermark on your video so all participants, including late joiners, can see that Granola is transcribing.
• Edit before sharing: Granola's notes are fully editable, so you can remove or rephrase any customer quotes in your enhanced notes before sharing them with stakeholders.
• Audio deletion: Granola transcribes device audio and deletes it after transcription.
• SOC 2 Type 2: Granola holds SOC 2 Type 2 certification, with third-party AI providers contractually prohibited from training on your data.

Organizing ideas into themes automatically

Because Granola uses your rough notes as anchors, the enhanced output organizes itself around the themes you identified during the session. If you typed "onboarding friction" and "notification overload" as separate headers during the meeting, the AI enhancement places transcript content under each theme rather than producing a single chronological summary. You can customize note templates to match your standard brainstorming structure so every session produces output in the same format, which makes synthesis and comparison across sessions much faster.

Customizable brainstorming templates for Granola

The three templates below are formatted for direct use in Granola. Copy them into your template library using the custom note templates feature and select the appropriate one before each session starts.

Product feature ideation template

Use this template for sessions focused on generating new features or improving existing ones.

## Session challenge
[State the specific user problem or opportunity]

## Individual ideas (silent phase)
[Participants add ideas here during the 10-minute silent phase]

## Research insights referenced
[Link to relevant discovery interviews or user feedback that informed the challenge]

## Themes identified
- Theme 1:
- Theme 2:
- Theme 3:

## Prioritized ideas (post dot-voting)
1.
2.
3.

## Technical constraints noted

## Success metrics
- How will we know this worked?

## Actionable next steps
| Idea | Owner | Deadline |
|------|-------|----------|

Problem-solving session template

Use this template when the team is diagnosing a specific operational or product problem rather than generating net-new ideas.

## Problem statement
[Specific, observable description of the issue]

## Root causes identified
- Cause 1:
- Cause 2:
- Cause 3:

## Potential solutions
[Generated during the individual and group ideation phases]

## Risks and mitigation strategies
| Solution | Primary risk | Mitigation |
|----------|-------------|------------|

## Decision
[Chosen solution and rationale]

## Actionable next steps
| Action | Owner | Deadline |
|--------|-------|----------|

Strategic planning template

Use this template for quarterly planning or longer-horizon roadmap sessions.

## Long-term goal (12 months)
[Stated in measurable terms]

## Market opportunities identified

## Resource constraints
[People, time, budget limitations that shape what's feasible]

## Ideas generated

## Prioritized bets
1.
2.
3.

## Milestones
| Milestone | Target date | Owner |
|-----------|-------------|-------|

## Actionable next steps
| Action | Owner | Deadline |
|--------|-------|----------|

Turning brainstorm notes into action

Querying past sessions for patterns

Granola's folder-level queries let you search across months of past brainstorming sessions to surface patterns and retrieve specific ideas. Create a shared folder called "Ideation Sessions" or "Product Discovery" in your team space, and every session note you add to that folder joins a searchable archive. Ask "What ideas did we generate for improving enterprise onboarding last quarter?" and get source-linked citations from every relevant session rather than manually searching through individual documents.

This capability solves one of the most common and costly patterns in product development: repeat research. When a new stakeholder asks "has anyone looked at this before?", the answer is searchable rather than dependent on whoever happened to attend the original session.

Tracking which ideas got built

Measuring brainstorming ROI makes the process defensible to stakeholders who view ideation as a cost rather than an investment. Track these metrics to demonstrate the value of structured sessions over time:

• Time-to-decision: How many days elapsed between the brainstorming session and an engineering ticket being created?
• Idea-to-ticket rate: What percentage of prioritized ideas from the session became tracked work items?
• Implementation rate: Of the tickets created from brainstorming sessions, how many shipped?
• Research reuse rate: How often do past brainstorming sessions get cited in new sessions or roadmap discussions?

Try Granola for free. Download the Mac or Windows app, connect your calendar, and run your next brainstorming session using the built-in templates. Share the customizable templates with your product team to standardize your discovery and ideation workflows.

FAQs

How long should a brainstorming session be?

A 60-minute session following the agenda structure above works well for most teams. For a focused single-question session, 30 to 45 minutes is often enough, since cognitive fatigue reduces idea quality when a session extends beyond what the challenge requires.

What if the team runs out of ideas?

Introduce a new constraint or apply a framework like SCAMPER to shift perspectives by prompting specific angles like "what could we eliminate?" or "what could we reverse?" A two-minute silent writing reset, where participants write independently before rejoining the group, reliably generates a new wave of contributions.

How do I prevent groupthink in a brainstorming session?

Run the individual ideation phase before any group sharing begins. This ensures every participant documents their unique ideas before hearing anyone else's, which prevents the anchoring effect where early suggestions dominate and quieter contributors self-censor to avoid conflict with the room's perceived consensus.

Glossary

Production blocking: A group dynamics problem that occurs when only one person can speak at a time, forcing others to wait, forget ideas, or stay silent. In brainstorming sessions, it reduces the total number of ideas generated because contributors cannot share thoughts the moment they form them.

Evaluation apprehension: The tendency to hold back ideas in a group setting because of uncertainty about how others will react. It disproportionately affects quieter team members and junior contributors, leading to sessions where a small number of vocal participants generate most of the output.

Anchoring effect: A cognitive bias where the first idea raised in a group discussion becomes the reference point that shapes all subsequent thinking. Later ideas get evaluated relative to the anchor rather than on their own merits, which narrows the range of solutions the team considers.

Dot voting: A fast prioritization technique where each participant receives a fixed number of votes, represented as dots or marks, and allocates them across a set of ideas. The distribution of votes reveals group priorities quickly without extended debate, and the silent casting of votes prevents any single voice from dominating the outcome.

Groupthink: A pattern where the desire for consensus overrides independent evaluation, leading teams to converge on a comfortable idea rather than the best one. It is most common when sessions lack structure, when senior voices speak first, or when the group has strong social cohesion that discourages dissent.