How to Plan a Brainstorm Session: A Practical Guide
Brainstorming has a bad reputation, and most of it is earned. Too many sessions are six people in a room for an hour, generating twelve ideas, eleven of which are forgotten by Friday. But the problem isn’t brainstorming, it’s unplanned brainstorming. A session with a clear question, the right people, a structured process, and a plan for what happens to the ideas afterwards is one of the most productive hours a team can spend.
This guide shows how to use the Brainstorm Session Planner to design sessions that produce usable ideas, not just sticky notes. It’s written for team leads, product managers, and anyone tasked with “coming up with ideas” for a real business problem.
When to Use This
Use a planned brainstorm when you need a range of ideas for a defined problem: naming a product, solving a customer complaint pattern, planning a campaign, redesigning a process. The key word is defined, brainstorming works on questions, not on vague aspirations. “How might we reduce customer support response times?” is a brainstormable question. “Let’s think about the future” is a meeting that should have been an email.
Don’t brainstorm alone what one person could decide, and don’t brainstorm what data could answer. If the question is “which supplier is cheapest?”, get quotes. Brainstorming is for problems with many possible answers where creativity and diverse perspectives genuinely help.
How to Fill It Out
Section 1: Session details. Date, time, duration, location, and facilitator. Keep it to 60–90 minutes, creative energy drops sharply after that. Name the facilitator explicitly; a brainstorm without a facilitator becomes a conversation, and conversations don’t produce ideas systematically. Six to eight participants is the sweet spot: enough diversity of thought, few enough that everyone speaks.
Section 2: The problem statement. One clear question the session must answer, written on the planner and displayed during the session. “How can we cut the average customer onboarding time from 11 days to under 5?” Test the question: is it specific enough that you’d recognise a good answer? Could the team generate at least twenty distinct ideas for it? If the answer to either is no, sharpen the question before booking the room.
Section 3: Participants and roles. List who attends and why, what perspective each person brings. “Mara (customer support, hears the complaints firsthand), Dev (engineering, knows what’s technically feasible), Lena (sales, knows what prospects ask for).” Invite at least one person from outside the immediate team; insiders share blind spots. Assign roles: facilitator (runs the process), scribe (captures every idea verbatim), and timekeeper. The scribe’s job is critical, ideas that aren’t captured don’t exist.
Section 4: Session structure. Plan the techniques and timing in advance. A reliable structure: 10 minutes of silent individual idea generation (everyone writes alone, this prevents the first loud voice from anchoring the room), 20 minutes of round-robin sharing with no criticism allowed, 15 minutes of building on the most promising ideas in pairs, then 15 minutes of grouping and preliminary voting. Write the timings into the planner and stick to them. The structure is what makes it a session rather than a chat.
Section 5: Ground rules. State them at the start of every session: no criticism during idea generation (evaluation comes later), quantity over quality at first, build on others’ ideas, stay on the question, one conversation at a time. Write the rules into the planner so the facilitator doesn’t have to improvise them. The “no criticism” rule is the one that matters most, a single “that’ll never work” in the first ten minutes can silence a room for the rest of the hour.
Section 6: Idea capture and next steps. How will ideas be recorded during the session, and what happens to them afterwards? “Scribe captures all ideas in the shared doc; within 48 hours, the facilitator groups them into themes and circulates the top ten for scoring.” The afterlife of the ideas is planned before the session, not after, including who evaluates them, by when, and how the team hears the outcome. A brainstorm whose ideas vanish into a drawer teaches the team that their creativity doesn’t matter.
Common Mistakes
1. Brainstorming without a sharp question. “Ideas for marketing” produces generic fluff. “Ideas for getting 500 signups for the June webinar with zero ad spend” produces ideas you can use. The quality of the question determines the quality of the ideas, spend real time on the problem statement.
2. Letting hierarchy into the room. When the boss’s idea gets nodded through and the junior’s gets questioned, the session is theatre. The facilitator must actively protect junior voices: silent generation first, anonymous voting where it helps, and explicit credit for built-on ideas. If the senior leader can’t resist steering, they shouldn’t attend, send them the output instead.
3. Criticising during generation. “We tried that already” and “that’s too expensive” are evaluation, and evaluation during generation kills generation. There will be time to filter, that’s what the scoring step is for. During idea generation, the only response to an idea is to write it down or build on it.
4. No follow-through on the ideas. The most common brainstorm failure isn’t a bad session, it’s a good session whose output is never evaluated, never decided on, never implemented. Plan the evaluation before the session: who scores the ideas, against what criteria, by what date. Then do it, and tell the participants what was chosen and why. The team will only brainstorm well twice if the first time led somewhere.
Who Needs to Sign Off
The person who owns the problem owns the session, usually the team lead or project manager. They approve the problem statement, the participant list, and the evaluation plan. If the brainstorm feeds into a larger project or budget decision, the project sponsor should confirm the question is the right one before the session runs. The facilitator doesn’t need to be senior, but they do need the authority to enforce the ground rules, including telling a director to hold their criticism until the evaluation phase.
How Often to Review and Update
Review the session output within a week, ideas decay fast, and a delayed evaluation signals that the ideas weren’t important. After each session, the facilitator should note what worked: which technique produced the best ideas, whether the timing held, whether the group size was right. Fold those notes into the planner for next time. There’s no fixed schedule for brainstorming itself, run sessions when you have a real question, not on a calendar cycle. A quarterly “innovation brainstorm” with no problem to solve is how the format gets its bad reputation.
Download the free Brainstorm Session Planner.