# Brainstorming Techniques: How to Run a Session That Actually Produces Ideas Canonical URL: https://headwayskills.com/knowledge/decision-making/brainstorming-techniques/ Markdown URL: https://headwayskills.com/knowledge/decision-making/brainstorming-techniques.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving decision-making at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer The best brainstorming techniques all do one thing: get people generating ideas alone before the group talks. A seven-step process for running a session that works. ## Key facts - Title: Brainstorming Techniques: How to Run a Session That Actually Produces Ideas - Category: Decision Making - Primary skill: Decision-Making - Related skills: Communication, Teamwork - Primary keyword: brainstorming techniques - Source page: https://headwayskills.com/knowledge/decision-making/brainstorming-techniques/ ## What this page covers - The best brainstorming techniques all do one thing: get people generating ideas alone before the group talks. A seven-step process for running a session that works. - Practical guidance for brainstorming techniques - How this topic connects to Decision-Making ## Detailed explanation The most reliable brainstorming technique isn't a game — it's a rule about when people are allowed to talk. Brainstorming techniques are structured methods for generating ideas as a group: brainwriting, round-robin, starbursting, reverse brainstorming, Crazy Eights, SCAMPER. What separates the ones that work from the ones that fizzle is whether they make people generate ideas independently before the group starts discussing them. That sounds backwards, because the picture most of us carry of brainstorming is a room, a whiteboard, and people building on each other out loud. Sixty years of research says that picture is the problem — and it explains why your last session produced four ideas, three of them from the same person. ## Why most brainstorming sessions underdeliver The comparison that started it all sets "real" groups against "nominal" groups: the same number of people working alone, with their ideas pooled afterward. A 1958 Yale study, and follow-up work in 1970, found the nominal groups generated more ideas — and the gap widened as the group got bigger. Pooling what people produce separately beats putting them in a room together. Three mechanisms explain the loss, and research has singled out one as the largest. Production blocking is the plain fact that only one person can speak at a time: while you wait your turn, you're also holding your idea in your head, where it decays. Diehl and Stroebe's work on productivity loss in brainstorming groups concluded that production blocking accounts for most of the shortfall. The second is evaluation apprehension — people fear looking foolish in front of colleagues, so they quietly filter out their least conventional ideas, which are exactly the ones a brainstorm exists to surface. The third is social loafing: in a group, individual effort is invisible, so it drops. None of this makes group work pointless. It means the group is the wrong tool for generating and the right tool for building and choosing. The Nominal Group Technique was designed around that split — independent generation first, then group discussion to evaluate — and it reliably yields more ideas, often better ones, than open brainstorming. Nearly every method below is a variation on the same structural fix. Electronic brainstorming, where everyone types into a shared board at once, is simply the digital version: nobody waits, so nobody is blocked. ## Brainstorming techniques, step by step The sequence below assumes a single session of about an hour. Each step depends on the one before it, and the order matters more than which technique you pick. ### 1. Write the question down as a single sentence A session fails before it starts if people are quietly working on different problems. [Before you book anything](/knowledge/communication/effective-meetings/), put the question on one line — specific enough that an answer would be recognizable, open enough that there's more than one. "How do we cut onboarding from three weeks to one?" works. "Improve onboarding" doesn't. Note the constraints in the same breath: budget, timeline, anything genuinely off the table. Constraints stated up front focus divergence; constraints revealed halfway through kill it. ### 2. Decide what a good idea looks like — before anyone has one Agree your evaluation criteria while the room is still empty of ideas. Impact, feasibility, cost, speed, risk, fit with what you're already doing — pick the three or four that matter here. This has to happen now rather than later, for one reason: once ideas exist, criteria stop being neutral, and people argue for the standard that happens to favor the idea they already like. Written-down criteria also make the final step fast instead of political. ### 3. Choose the technique that fits your group's failure mode Techniques aren't interchangeable; each is engineered against a specific failure. Brainwriting — everyone writes ideas on a sheet, then passes it along to be built on — attacks production blocking and the dominance of the [loudest voice](/knowledge/decision-making/group-decision-making/) directly. Round-robin gives each person a turn in strict rotation, which is what you want when one or two people usually absorb the airtime. Starbursting generates questions instead of answers (who, what, where, when, why, how), useful when the group doesn't yet understand the problem well enough to solve it. Reverse brainstorming asks how you could make the problem worse, which unsticks a self-conscious room fast. Crazy Eights demands eight ideas in eight minutes, one a minute, when the enemy is over-editing. SCAMPER — Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse — suits improving something that already exists rather than inventing from nothing. Diagnose, then choose. ### 4. Brief people in advance, then start alone and silent Send the question, the constraints, and the criteria before the session; it costs nothing and lets slower, more considered thinkers arrive with something. Then open with silent individual generation — everyone writes for five to ten minutes, no discussion. This single move is what buys you the nominal-group advantage inside a real meeting. Aim for volume rather than quality: twenty to fifty raw ideas across the group is a realistic first pass, and the generating phase deserves roughly half a one-hour session. ### 5. Share in rotation, and build instead of judging Now bring the group in, because this is the part groups are genuinely good at. Go around in order, one idea each, until every list is exhausted; rotation stops the session collapsing into a conversation between the two most confident people. The single rule is that nothing gets evaluated yet — no "we tried that," no "that's out of budget." Even mild criticism here restarts the [self-censorship](/knowledge/teamwork/psychological-safety-in-the-workplace/) you just designed around. When someone's idea sparks a new one, that's the whole payoff for having a group: write it down and keep going. ### 6. Cluster before you cut With everything visible, group the ideas into themes rather than ranking them straight away. Clustering does two useful things: it shows which parts of the problem attracted a lot of thinking and which were quietly ignored, and it lets near-duplicates merge without anyone's contribution being publicly rejected. It also slows the room at the exact moment it wants to leap to a favorite. Ten minutes is usually enough — you're organizing, not deciding. ### 7. Converge against the criteria, then name who does what Only now do you evaluate, and you evaluate against step 2's criteria rather than against enthusiasm. [Score the clusters](/knowledge/decision-making/weighted-decision-matrix/), rank them, carry three to five forward, and record what you set aside and why; that record is what stops the same idea being re-litigated next month. Converging normally takes less time than generating — around twenty minutes. Then the step most sessions skip: every surviving idea gets a name attached and a next action. A brainstorm that ends in a photographed whiteboard and no owner has produced nothing. If your sessions tend to stall right here — plenty of options, no decision — it's worth seeing [where your decision habits stand](https://assessment.headwayskills.com/), because the bottleneck usually isn't a shortage of ideas. ## The skills that decide whether the ideas go anywhere Read back over those seven steps and notice how little of the work is creative. Almost all of it is running a fair process, keeping people talking honestly, and holding a group together long enough to choose. Those are habits, and the people who have them learned them somewhere. **Decision-Making** is what the whole sequence rests on, because a brainstorm is the front half of a decision rather than an event in its own right. It covers the moves this article keeps returning to: gathering input independently before any discussion, recruiting differing opinions on purpose, appointing someone to argue against the emerging favorite, splitting a large group into subgroups, drawing quieter people in by name, and calling time out when the room is circling. It also names the trap the technique lists rarely mention — anchoring, where the first option spoken silently sets the range everyone else works inside. **Communication** is what makes the session itself function, and a brainstorm is a recognizable meeting type: the problem-solving meeting. That brings its own basics — prepare, state the purpose, hold the discussion to it, capture what was said. In the room the decisive behaviors are unglamorous: listening with real attention instead of waiting for your turn, moderating how long you talk, and managing interruptions so a half-formed idea gets finished. Most of the ideas you never hear were lost to someone talking over them. **Teamwork** determines whether people will say the odd thing at all. A technique can protect someone from being interrupted; it can't manufacture the trust that makes them risk an unfinished thought in front of colleagues. That comes from ordinary reliability — meaning what you say, doing what you committed to, letting a bad idea be a bad idea without it becoming a verdict on the person. It also covers what happens after the choice: voicing your disagreement while the decision is still open, then backing what the group decided instead of relitigating it in the corridor. If you want to know which of the three is actually costing you, the free Work Skills Test will show you [which skill to build first](https://assessment.headwayskills.com/) — process, listening, and trust are three of the twelve work skills it maps, and not one of them is a talent you either have or don't. Some of this may already sound like how you work: you're the one who jots a few options down before the meeting, or who notices when the room has quietly settled on the first suggestion. Those aren't fixed traits. They're habits, and the ones that don't come naturally yet are simply the ones you haven't practiced — you can strengthen them without becoming a different person in meetings. It also counts for more over time, not less. Early on, someone usually hands you the question already framed. The further you go, the more often you're the one framing it, and the more expensive it gets when a group generates twenty options and commits to none. You've already done the part most people skip: reading this far means you're treating a flat session as a process you can fix rather than a bad day. What's left is finding out which part of that process is yours. ## Find out which part of the process is yours So the only thing left is to see where you actually stand. The Work Skills Test is a **free**, seven-minute self-assessment that maps you across all twelve work skills — including the decision-making, communication, and teamwork habits that decide whether a session ends in a decision or a photograph of a whiteboard — and shows you which ones will make the biggest difference to how you work with a group. It won't hand you another technique. It'll do something more useful: show you which of the ones you already know you aren't actually using. **[Take the test](https://assessment.headwayskills.com/)** *Free to take, and about seven minutes from start to results.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? The best brainstorming techniques all do one thing: get people generating ideas alone before the group talks. A seven-step process for running a session that works. ### Which Headway skill does this connect to? This guide connects primarily to Decision-Making. It also relates to Communication, Teamwork. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/decision-making.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/knowledge/teamwork.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/decision-making/brainstorming-techniques/ Preferred summary: "The best brainstorming techniques all do one thing: get people generating ideas alone before the group talks. A seven-step process for running a session that works." ## Change log - 2026-07-07: Content collection version published.