Brainwriting
Brainwriting is a facilitated, written ideation technique where participants collect ideas individually and pass them around in rounds for iterative development.
Classification
- ComplexityLow
- Impact areaOrganizational
- Decision typeOrganizational
- Organizational maturityIntermediate
Technical context
Principles & goals
Use cases & scenarios
Compromises
- Unclear rules lead to low participation.
- Too short timeboxes prevent depth.
- Poor documentation loses idea history.
- Adhere to and communicate timeboxes clearly.
- Use anonymity to lower social inhibitions.
- Document results and structure them for follow-up.
I/O & resources
- Clear problem or task statement
- Facilitation script and schedule
- Working materials (paper, whiteboard, digital board)
- Collection of raw ideas
- Categorized idea clusters
- Selection of prioritized concepts
Description
Brainwriting is a structured creativity technique where participants first write ideas individually and then iteratively pass and develop them in rounds. It reduces dominance effects, increases idea diversity, and works well for distributed or quieter teams. Facilitation, timeboxing and participant mix influence outcomes.
✔Benefits
- Increased idea volume through parallel individual work.
- Reduced influence of dominant participants.
- Well suited for distributed or quiet teams.
✖Limitations
- Requires clear facilitation and structure.
- May produce less spontaneous interaction.
- Not all ideas are immediately contextualized.
Trade-offs
Metrics
- Number of submitted ideas
Measures volume of contributions per session and per participant.
- Share of actionable ideas
Percentage of ideas that can be tested or implemented quickly.
- Participation rate
Share of invited people who actively contribute.
Examples & implementations
Product team increases idea count
A product team replaced open brainstorming with brainwriting and doubled submitted ideas because quieter members contributed more.
Remote design sprint
During a remote design sprint a team used digital brainwriting to collect ideas asynchronously across time zones.
Cross-functional problem solving
In a strategy workshop brainwriting helped surface diverse perspectives equally and identify hidden assumptions.
Implementation steps
Define objective and briefly state the problem.
Set participants and timeboxes.
Explain rules (written, anonymous/named, number of rounds).
First writing round: individual idea collection.
Further rounds: pass and extend ideas.
Cluster, evaluate and follow up.
⚠️ Technical debt & bottlenecks
Technical debt
- Non-standardized templates hinder reuse.
- No central idea repository causes knowledge loss.
- Missing tool integrations hamper follow-up.
Known bottlenecks
Misuse examples
- Using brainwriting as the sole validation instead of ideation.
- Time pressure so high that only superficial ideas emerge.
- No facilitation: rules are ignored and chaos ensues.
Typical traps
- Excessive structure kills creative impulses.
- Early evaluation reduces inventiveness.
- Unclear documentation prevents traceability.
Required skills
Architectural drivers
Constraints
- • Limited workshop duration
- • Need for documented templates
- • Accessibility for remote participants