Brainstorming is useful when you need more than one plausible answer to a problem. The difficulty is that unstructured idea generation often produces repetition, dominant voices, and obvious suggestions. Better brainstorming techniques for problem solving give people a method for generating alternatives before they start judging them.
This guide covers ten techniques and explains when each one is useful. For a broader framework, see our creative thinking and problem solving guide.
First define the problem clearly
Brainstorming quality depends on the question. “How do we improve the business?” is too broad. “How might we reduce the time between a customer request and the first useful response?” gives the group something concrete to work on.
- Define who experiences the problem.
- Describe the current state.
- State the desired outcome.
- List important constraints.
- Avoid embedding your preferred solution into the question.
1. Classic free brainstorming
Set a short time limit and generate ideas without evaluating them. This works best when participants already understand the problem and psychological safety is high enough that people will share unfinished ideas.
2. Brainwriting
Instead of speaking immediately, each person writes ideas independently for a few minutes. Then the group shares or builds on them. Brainwriting helps when a few people normally dominate the conversation or when quieter participants need thinking time.
3. Round-robin brainstorming
Go around the group and ask each person to contribute one idea before anyone contributes a second. Participants can pass if needed. The structure distributes airtime and reduces the chance that the first confident speaker defines the whole discussion.
4. Mind mapping
Write the problem in the center and branch outward into causes, users, constraints, opportunities, and solution directions. Mind mapping is useful when the problem contains several connected parts and you want to see relationships rather than only a flat list of ideas.
5. SCAMPER
SCAMPER uses seven prompts—Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, and Reverse—to force different ways of looking at an existing process, product, or idea. See our full SCAMPER examples guide for a step-by-step version.
6. Reverse brainstorming
Ask the opposite question: “How could we make this problem worse?” or “What would guarantee failure?” The answers expose risk factors and hidden assumptions. Reverse those answers to generate practical prevention ideas.
7. Constraint removal
Temporarily remove one major constraint and ask what you would do if it did not exist. For example: “If budget were not the problem, what would solve this?” Then bring the constraint back and look for smaller versions of the strongest ideas.
8. Analogy brainstorming
Ask how another industry, profession, or system solves a similar problem. A restaurant handles queues differently from a software company, but the underlying principles of flow, prioritization, and visibility may transfer.
9. Role-storming
Generate ideas from another person’s perspective: a new customer, a competitor, a skeptical manager, a child, or an expert in another field. This helps break habitual assumptions about what “we normally do.”
10. Crazy 8s
Divide a page into eight spaces and create eight rough ideas in a short period. The pressure to produce multiple options quickly prevents people from stopping at the first acceptable solution. It is especially useful for visual, workflow, product, and service-design problems.
Which brainstorming technique should you choose?
| Situation | Good starting technique |
|---|---|
| Dominant voices in a group | Brainwriting or round-robin |
| Need many fast alternatives | Crazy 8s |
| Stuck with an existing process | SCAMPER |
| Problem has many connected causes | Mind mapping |
| Group is trapped by assumptions | Reverse or analogy brainstorming |
| Need customer-centered ideas | Role-storming |
Separate idea generation from evaluation
One of the biggest brainstorming mistakes is judging each idea the moment it appears. Early evaluation narrows the range too quickly. Generate first, then switch modes.
- Generate a broad set of ideas.
- Remove duplicates.
- Group similar ideas.
- Define evaluation criteria.
- Score or compare the strongest options.
- Choose what to test next.
If you are unsure whether the problem itself is correctly diagnosed, use the 5 Whys method before brainstorming solutions.
Example: brainstorming a late-delivery problem
Suppose a small team repeatedly delivers projects late. The first instinct might be “work faster.” A better session could begin with the question: “How might we reduce avoidable delays between project approval and final delivery without increasing overtime?”
- Brainwriting might reveal unclear handoffs.
- Reverse brainstorming might expose behaviors that guarantee delay, such as starting without required files.
- SCAMPER might suggest eliminating redundant approvals.
- Role-storming from the client’s perspective might reveal slow feedback loops.
- Mind mapping might show that the real issue is not production speed but dependency management.
Common brainstorming mistakes
- Using a vague problem statement.
- Letting the first idea anchor the group.
- Combining generation and evaluation too early.
- Inviting too many people without clear roles.
- Recording ideas but never choosing a next experiment.
- Confusing quantity with quality after the session ends.
A 30-minute brainstorming workflow
- Minutes 1–5: clarify the problem, desired outcome, and major constraints.
- Minutes 6–15: generate ideas using one technique, with no detailed evaluation.
- Minutes 16–20: group duplicates and related ideas.
- Minutes 21–25: evaluate the strongest options against two or three criteria.
- Minutes 26–30: choose one next experiment, owner, and review point.
This structure prevents the session from becoming a long conversation with no decision. If the issue is complex, run more than one short session rather than stretching one meeting indefinitely.
Use a simple scoring matrix after brainstorming
Once idea generation ends, compare the strongest options using the same criteria. For example, score each idea from 1 to 5 on expected impact, effort, speed to test, and reversibility.
| Idea | Impact | Effort | Speed to test | Next step |
|---|---|---|---|---|
| A | 5 | 4 | 2 | Prototype |
| B | 3 | 2 | 5 | Test this week |
| C | 4 | 5 | 1 | Hold |
Do not treat the total score as automatic truth. The matrix simply makes the trade-offs visible so the group can explain why one option deserves a test.
Solo brainstorming vs. group brainstorming
Solo brainstorming is faster, protects independent thinking, and works well for writing, planning, and early exploration. Group brainstorming adds more experiences and perspectives but can create anchoring, conformity, and unequal participation. A strong hybrid is to let everyone generate ideas alone first, then combine them in a group session.
For high-stakes problems, consider repeating the exercise after new evidence arrives. The first brainstorming session should not become a commitment to defend its favorite idea forever.
Frequently asked questions
What is the best brainstorming technique for a team?
There is no single best method. Brainwriting is a strong default when you want independent thinking before discussion, while round-robin works when equal participation is the main concern.
How long should a brainstorming session last?
Keep the idea-generation phase short enough to maintain energy. Many focused sessions can work in 15 to 30 minutes, followed by a separate evaluation phase.
Can brainstorming be done alone?
Yes. Mind mapping, SCAMPER, reverse brainstorming, analogy prompts, and Crazy 8s all work individually. The key is to force multiple perspectives rather than stopping at your first idea.
Final takeaway
Good brainstorming is structured divergence followed by deliberate selection. Choose a technique that fits the problem and group, generate enough alternatives to escape the obvious answer, and finish by deciding what deserves testing.