Brainstorming Methods help teams produce better ideas by separating idea generation from evaluation, giving quiet voices room, and moving from raw ideas to prioritized action.
Definition
Brainstorming Methods are structured approaches for generating and developing ideas. In continuous improvement, brainstorming is used for root cause hypotheses, countermeasure ideas, risk identification, customer needs, process redesign, failure modes, and implementation planning.
Effective brainstorming is not an unstructured meeting where the loudest person wins. It uses facilitation rules, prompts, time boxes, silent idea generation, grouping, clarification, and selection methods so the team can move from divergent thinking to useful action.
History
Brainstorming became widely known through creative problem-solving practice in the twentieth century. The core idea was to defer judgment during idea generation so participants could produce more and broader ideas before evaluating them.
Quality and Lean teams adapted brainstorming into structured problem-solving routines. Methods such as brainwriting, round-robin brainstorming, affinity grouping, nominal group technique, and cause-and-effect brainstorming help teams avoid bias and organize complex input.
When to Use
Use brainstorming when the team needs multiple possible causes, solutions, risks, customer needs, failure modes, or improvement ideas. It is useful in DMAIC, Kaizen events, A3 problem solving, FMEA, Fishbone diagrams, process redesign, control planning, and change management.
Do not use brainstorming as a substitute for evidence. Ideas generated during brainstorming are hypotheses until verified with data, process observation, experimentation, or subject-matter review.
Step-by-Step
- Define the prompt. State the question clearly, such as "What could cause late shipments?" or "How might we reduce setup time?"
- Select the method. Choose open brainstorming, silent brainwriting, round-robin, nominal group technique, affinity brainstorming, or reverse brainstorming.
- Set ground rules. Defer judgment, build on ideas, be specific, keep the pace moving, and separate generation from evaluation.
- Generate ideas. Use silence first when power dynamics or groupthink are concerns.
- Clarify without debating. Ask short questions so everyone understands each idea.
- Group related ideas. Use affinity grouping, cause categories, process steps, or theme clusters.
- Prioritize. Use voting, impact-effort, data availability, risk, customer impact, or feasibility criteria.
- Convert to action. Assign owners for verification, data collection, trials, or implementation planning.
Examples
- Fishbone session: A team brainstorms possible causes of seal leaks under machine, method, material, measurement, people, and environment categories.
- Kaizen event: Operators silently write ideas for reducing walking distance, then group them into layout, tooling, material, and information-flow themes.
- FMEA workshop: A cross-functional team brainstorms failure modes before scoring severity, occurrence, and detection.
- Change planning: Leaders brainstorm possible resistance points before building stakeholder communication and coaching plans.
- Service improvement: A support team uses reverse brainstorming by asking, "How could we make response time worse?" then reverses the answers into improvement ideas.
Common Pitfalls
- Judging too early. Early criticism narrows thinking and reduces participation.
- Letting hierarchy dominate. Silent methods and structured turns help reduce power bias.
- No clear prompt. Vague questions produce vague ideas.
- Stopping at ideas. Brainstorming must lead to verification, prioritization, or action.
- Confusing opinion with root cause. Brainstormed causes need evidence.
- Too many participants without structure. Large groups need stronger facilitation and grouping methods.