01 · Purpose and boundaries
Purpose and boundaries
Brainwriting is written idea generation. Participants record ideas independently, then may pass them to others for elaboration before discussion. It reduces the need to compete for speaking turns and can reveal contributions from people who hesitate in an open meeting. It does not automatically make ideas anonymous or remove organizational power differences.
Use it when groups are large, verbal discussion is dominated, language confidence varies, or participants benefit from reflection. Establish a focused question and shared facts. Choose a format that fits accessibility and literacy needs; typed contributions, dictation to a neutral facilitator, or translated prompts may be appropriate. The method should expand participation rather than exclude those who write slowly.
02 · How the method works
How the method works
Explain the problem, operating boundaries, and generation rules. Ask participants to write separate ideas with enough detail to understand the proposed mechanism. Keep evaluation out of the initial writing stage. Allow a short silent period so ideas arise independently rather than being anchored to the first speaker.
In a circulating format, pass contributions to another participant, who adds a variation or builds on the original. Clearly distinguish the original concept from elaborations. A familiar 6-3-5 variation uses six participants, three ideas per round, and roughly five minutes per round; these numbers are a facilitation option, not a mandatory definition or a quality guarantee.
Collect ideas, clarify ambiguous wording, and combine true duplicates without erasing useful differences. Discuss mechanisms and assumptions before evaluation. Apply agreed gates and comparison criteria, then select concepts for investigation. Preserve a route for contributors to clarify privately if public attribution would discourage participation.
03 · Worked logistics example
Worked logistics example
Fictional MoorBridge's picking team wants to reduce replenishment interruptions. A previous verbal meeting generated nine ideas, mostly from two senior employees. The new session includes six participants from picking, stock control, replenishment, and the late shift. Shared data show 24 interrupted picks per 480 daily order lines.
Each person initially writes three ideas, creating 18 contributions. Two circulation rounds create 21 elaborations, but these are not counted as 21 entirely independent concepts. After clarification and merging, 16 distinct ideas remain. A late-shift colleague proposes a visible reserve trigger before the pick face empties; another participant adds a replenishment-round confirmation.
The selected pilot runs on ten high-use locations for five days. These locations account for 200 lines per day and ten baseline interruptions. During 1,000 pilot lines, interruptions total 19 rather than the expected 50. Replenishment labor rises by 20 minutes daily because rounds become more regular. The team measures this additional work rather than calling the idea free.
04 · Interpretation and decisions
Interpretation and decisions
Written participation exposed an overlooked operating condition, but the difference from the earlier meeting is not a controlled comparison of creativity methods. The participants, prompt, and shared facts also changed. Judge the method by useful participation and developed concepts rather than raw idea counts.
The pilot interruption rate falls from 5% to 1.9% for the selected locations. Determine whether the saved picking time and improved service justify the extra replenishment effort. If each avoided interruption previously consumed three minutes, 31 avoided events over five days save an illustrative 93 minutes; the additional replenishment work is 100 minutes. The service effect may still justify the change, but labor saving alone does not.
05 · Common misapplications
Common misapplications
Brainwriting can produce unreadable fragments that cannot be interpreted later. Encourage descriptions of actions and mechanisms rather than single-word suggestions. Excessively strict timing can disadvantage people who need more processing time or language support.
Do not assume anonymity when handwriting, role-specific knowledge, or digital metadata reveals identity. Passing ideas can create anchoring if every participant merely modifies the same initial concept. Preserve an independent generation stage. Avoid counting each wording variation as an original solution. Written collection must still lead to clarification, evaluation, and evidence-based testing.
06 · Advanced adaptation
Advanced adaptation
For distributed teams, use asynchronous generation followed by a scheduled clarification discussion. Set a submission window that includes all shifts and time zones. Prevent early visibility from anchoring everyone if independent ideas are desired; reveal contributions after the initial period.
Use prompts targeted at different dimensions—information availability, physical access, timing, replenishment, and exceptions—while keeping the common objective. Rotate ideas among roles to build operational depth, but do not require every idea to receive a fixed number of additions. A mature process tracks concepts through development and testing so quieter contributors can see how their input influenced real work.
07 · Implementing and sustaining the change
Implementing and sustaining the change
Introduce brainwriting 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.