01 · Purpose and boundaries
Purpose and boundaries
Brainstorming is a group method for generating multiple ideas around a clearly stated problem or opportunity. Its useful discipline is postponing evaluation during generation so participants can explore possibilities and build on one another. It produces candidate ideas, not proof of effectiveness or a final decision.
Prepare a bounded question using the actual situation and required outcome. “How can we reduce waiting for a loading bay while keeping vehicle and pedestrian separation?” is more useful than “How can logistics improve?” Give participants enough shared facts to avoid guessing, but avoid prescribing the favored answer. Include different roles and experience levels. Participation should not depend on speaking speed, confidence, or seniority.
02 · How the method works
How the method works
Explain the problem, constraints, session duration, and the distinction between generating and evaluating. Establish ground rules: record ideas without ridicule, defer feasibility judgment, invite unusual suggestions, and encourage constructive combinations. Give participants a short period of independent thinking before open exchange if it improves participation.
Capture each idea in language specific enough to preserve its meaning. Ask clarifying questions without converting them into criticism. A round-robin format can help distribute airtime; an open format can encourage spontaneous connections. Allow people to pass. The facilitator should prevent interruptions, repeated dominance, and premature defense of proposals.
After generation closes, group related ideas while preserving meaningful differences. Clarify the operating mechanism, remove true duplicates, and evaluate with agreed requirements and evidence needs. Use must-pass safety and customer conditions before ranking preferences. Select a manageable number of concepts for investigation, and state who develops them. The list alone is not an improvement.
03 · Worked logistics example
Worked logistics example
Fictional BeaconCross has six loading bays and handles 60 trucks per day. Twenty trucks wait more than 30 minutes, and eight late departures threaten customer windows. The session includes dispatch, forklift operators, yard control, customer service, and maintenance. The question focuses on waiting before bay access, rather than all transport delay.
The group generates 28 ideas in 25 minutes. These include arrival appointments, separating document checks from bay occupation, a ready-load signal, flexible bay assignment, and a risky suggestion to share a bay between pedestrian packing and loading. The latter is recorded during generation but fails the safety gate during evaluation.
After clarification, 17 distinct ideas remain. The team develops three concepts. A one-week pilot of pre-arrival document checks and a ready-load signal covers 300 trucks. Trucks waiting over 30 minutes fall from a baseline expectation of 100 to 66. Late departures fall from an expected 40 to 28; staffing and daily volume are recorded to support comparison.
04 · Interpretation and decisions
Interpretation and decisions
Twenty-eight ideas do not establish success; the quality of mechanisms and subsequent tests matters. The pilot's reduction in long waits is about 34%, while late departures reduce by 30% under the illustrative comparable baseline. These outcomes are related but different. Determine whether arrival mix, carrier behavior, or staffing influenced the result.
The appointment concept may still be worth exploring, but it should not receive credit for a pilot that did not implement it. Retain deferred ideas with their assumptions. Ask whether the chosen concepts remove causes or merely redistribute waiting. If document checking shifts work earlier, verify customer service has the capacity and accurate information to perform it.
05 · Common misapplications
Common misapplications
Brainstorming often becomes a debate after the first suggestion, suppressing alternatives. Another failure is treating the most popular idea as the best supported. Voting reflects preferences, not feasibility or causal effectiveness. Do not let the manager announce a solution before the group begins.
A broad question produces vague answers and wasted time. A narrow question that embeds a technology excludes alternatives. Avoid confusing criticism of a process with criticism of a colleague. Do not discard ideas because they sound unfamiliar; clarify their mechanism first. Equally, do not excuse unsafe or noncompliant implementation because the idea arose in a creative session.
06 · Advanced adaptation
Advanced adaptation
Use smaller groups or rotating topic stations when a single large discussion reduces participation. Combine independent generation with group elaboration to reduce production blocking, where people forget ideas while waiting to speak. Remote sessions need a visible shared record and an explicit turn-taking approach.
Change perspectives deliberately: ask what the downstream customer experiences, what maintenance sees, or what happens during a system outage. If ideas cluster around small adjustments, switch to SCAMPER or reversal prompts to broaden the design space. Return to evidence after divergence; creativity and operational testing perform different, complementary functions.
07 · Implementing and sustaining the change
Implementing and sustaining the change
Introduce brainstorming within a clearly named operating boundary. Identify the product family, shift, equipment, and handoffs affected; record what happens immediately before and after that boundary. A change that improves one task while exporting its delay to another department has not established an improvement. Agree who can stop the trial, who handles exceptions, and which customer commitment takes priority when the normal rule cannot be followed.
Establish a baseline from actual work rather than a single demonstration. Include normal variation in order mix, replenishment timing, staffing, and workload. Keep the denominator visible: minutes per order, defects per shipment, or completed lines per available hour answer different questions. Record the workload and conditions alongside each observation so that a quiet trial period cannot masquerade as better performance. Observe the process with the people who do it; their explanation of interruptions often changes the proposed design.
Start with a reversible pilot large enough to expose handoff problems. Explain the expected mechanism before launch: which action changes, which delay or failure it removes, and which result should respond. Train all affected shifts and support roles using the same operating definition. During the pilot, capture exceptions as information about the design. Do not conceal them through unofficial stock, unrecorded overtime, or a specialist who quietly repairs every failure.
Review customer service, safety, quality, work content, and inventory together. A faster average with more severe late orders may be unacceptable; a lower inventory level with repeated emergency deliveries may have displaced the cost. Investigate variation before declaring success. If the expected mechanism does not appear, revise the design or return to the baseline rather than defending the idea. A promising observation is a reason to test more conditions, not proof that every operating context will behave identically.
After a successful trial, make the new rule part of daily work. Give an accountable owner responsibility for the operating standard, change control, training, and periodic review. Specify the abnormal condition that requires escalation and the person who responds. Check whether the improvement remains effective when a trained colleague is absent or demand changes. Sustain the mechanism through routine management and learning; documentation is useful only when it describes the process people actually follow.
Connections
Related methods and phase use
Placed under Improve because of the outcome it supports. Use the method in other phases when its purpose and assumptions fit the work; the phase list is a guide to selection, not a compulsory sequence.
Sources
Professional foundations and further reading
The explanation and fictional teaching examples are written for LeanTrainingLab. Linked primary sources provide professional foundations; example values and local conventions are stated in the guide. The accepted toolset draws on Six Sigma+Lean Toolset, second edition (Lunau, editor; Springer, 2013). No book text or examples are reproduced here.