Be Creative · Growth Library
In a Group, Write Down Ideas and Pass Them Around for Others to Build
Brainwriting
Try this
Give the group one clear question, let everyone write ideas silently, pass the ideas to another person to add or change them, and delay discussion until the group has built several options.
Check-in: Did everyone get a chance to contribute before discussion? Which idea became more useful after another person built on it, and what should the group test next?
Evidence: Practical guidance; no evidence-like claim is detected in the current source record.
Review note: Public content is replaced by a curated group ideation protocol. Unsupported idea-yield percentages, invented internal observations, and rigid timing/count prescriptions from the inherited draft are removed from the effective build.
Brainwriting separates idea generation from group discussion. Everyone writes first, then passes the written ideas so another person can add, combine, or change them. The useful part is not a magic number of people, ideas, or minutes. It is the change in sequence: parallel contribution first, evaluation later.
1. Write one clear question
Start with a question that gives the group something specific to change or create. Include the real constraint if it matters, but do not bury the question in a long briefing.
For example: How could we make the first customer setup easier without adding another meeting? is more workable than How can we improve onboarding?
2. Write before talking
Give everyone a quiet first pass. Each person writes a few short ideas independently. Use paper, cards, or separate cells in a shared document. Avoid discussion during this pass so early reactions do not become the group's default direction.
3. Pass and build
Move each set of ideas to another person. Their job is to build rather than judge. They can add a missing detail, combine two ideas, change an assumption, or suggest a smaller version that could be tested.
If an idea seems weak, add an alternative beside it instead of stopping the round to debate it.
4. Switch modes deliberately
After the group has written and built on several ideas, stop the silent rounds. Now cluster similar options and discuss them. Keep generation and evaluation as separate modes instead of sliding back and forth between them.
5. Choose a next test
Do not finish with a wall of ideas. Pick one or a few options that deserve a concrete next step. Name what will be tried, who will do it, and when the group will look at the result.
In your tracker, the useful record is the prompt, the selected option, and the next test. Idea counts are optional; shipping a next step matters more than filling the page.
Questions to consider
How many ideas should each person write?
Use a small number that fits the group and the problem. The point is to create enough material to pass and build on, not to hit a universal quota.
When should the group start discussing the ideas?
After at least one silent writing round and one build round. Keeping discussion separate at the start gives each person space to contribute before the group begins evaluating.
What should I add to someone else's idea?
Add a detail, combine it with another idea, change an assumption, or make the next test more concrete. Build first; critique can wait until the group switches into selection mode.
Maintenance record
Review history
Current status: Reviewed. An editorial or evidence review is recorded and no later event changes that conclusion.
2026-08-18 · reviewed · Brali editorial agent Source: protocol-content-overrides-brainwriting.json
Replace an inherited brainwriting draft containing unsupported idea-yield percentages, invented internal observations, and excessive timing/count prescriptions with a compact group ideation protocol.
Browse the review ledger · Challenge or update this hack
Implementation observations can trigger a review, but they cannot change an evidence conclusion by themselves. Commercial relationships do not control review status or outcomes.
Continue from here
Choose the next useful path.
Article versions
Brali keeps substantive article history visible. Later reviews may refresh wording, sources, examples, or boundaries without silently replacing the record.
- Version 2025-10-06: first recorded publication in the migrated Brali corpus.
- Evidence review 2026-08-18: reviewed by Brali editorial agent; evidence state is
practical.
Canonical source record · Evidence state: practical.