Brainwriting and the 6-3-5 method

Brainwriting gives people time to put ideas on paper before the group starts discussing them. In the 6-3-5 version, six people each write three ideas in five minutes, pass their sheets on, and continue with the ideas now in front of them. The useful result is a collection of options the team can understand and investigate—not a winner chosen by whoever makes the strongest pitch.

Imagine a small equipment-hire business trying to improve collection day. Customers sometimes arrive without knowing whether everything is ready, while staff discover missing accessories at the counter. This is a hypothetical example throughout. A workshop could quickly settle on “send more reminders.” Brainwriting provides room to explore other responses before that first suggestion becomes the whole conversation.

What 6-3-5 actually means

Penn State’s method summary attributes 6-3-5 to Bernd Rohrbach and describes the familiar six-person, three-idea, five-minute structure. Six rounds provide 108 writing spaces across all sheets: six people × three entries × six rounds. That is capacity, not a promise of 108 distinct, useful ideas.

Someone might extend an earlier suggestion, describe a similar solution, or leave a space empty. Treat those outcomes honestly. A partly filled page containing a genuinely different approach may be more valuable than a full page of small wording changes.

The Hochschule Luzern instructions describe passing worksheets between rounds so that people can add to or develop earlier ideas. This distinguishes the method from simply asking everyone to write a private list and read it aloud. Its distinctive work happens in the encounter between your thinking and somebody else’s unfinished suggestion.

Choose a question worth spending time on

Brainwriting is appropriate when the team understands a situation well enough to explore possible responses. It is less helpful when people disagree about what the problem is, lack contact with the people affected, or have no authority to do anything with the output.

For the equipment-hire example, use a bounded question: “How could customers and staff spot a collection problem before the customer travels?” This leaves room for changes to information, preparation and coordination. “How should our new reminder app work?” already assumes the solution. “How can we transform customer experience?” leaves almost every boundary open.

Prepare a short account of what is known and what remains uncertain. If the team has only internal guesses, first use customer interviews to investigate actual collection experiences. The GOV.UK research-planning guidance connects research questions to the people and methods needed to answer them. An idea-generation exercise cannot replace that investigation.

Put genuine constraints beside the question. In this example, the team might be able to change its preparation routine but not replace its inventory system this quarter. Distinguish that commitment from an assumption such as “customers will never answer a phone call.” The latter is something to investigate, not automatically a wall around the exercise.

Prepare the room and the sheets

Give each writer a sheet with the same question, three idea columns and six writing rows. Number the sheets so that suggestions remain traceable when they are later discussed. A large enough writing area matters more than a polished template. The reader needs to understand the action being proposed and whom it helps.

Before starting, explain how sheets will circulate, how time will be signalled and what happens after writing. Ask participants not to erase someone else’s entry. An extension should remain distinguishable from the idea that prompted it. Decide whether names are necessary, and do not promise anonymity: handwriting, content and the order of circulation may make authors recognizable.

Check the format with the people attending. Fast handwriting, small print or rapid switching may be a barrier. Offer readable digital text, more time or another agreed way to contribute. A changed format is an adaptation, not a failed attempt to obey the numbers. The purpose is useful participation, not demonstrating that everybody can keep up with a timer.

Run the writing rounds

First, let the group clarify the question. Ask what counts as a collection problem and which part of the experience is in scope. Resolve basic misunderstandings before silence begins; otherwise each sheet may answer a different question.

Start the first five-minute round. Each person writes up to three responses, ideally one per cell. Encourage an action and a little context: “Check accessories before sending the collection confirmation” is easier to work with than “better quality.” Do not interrupt the round to rank, defend or sell suggestions.

At the signal, pass each sheet one place in the agreed direction. Participants read what is already there, then use the next row for additions, alternatives or combinations. An idea can inspire a substantially different response; people do not need to produce three cosmetic variations of the first row.

Repeat until six rounds have been completed and each sheet has been worked on by all six writers. The writing intervals total 30 minutes. Reading, passing, clarifying the brief, breaks and discussing the result require additional time. If you need a complete meeting structure, the 90-minute idea workshop provides a broader agenda; it is not the same thing as 30 minutes of 6-3-5.

If a later entry is unclear, mark a question beside it and continue rather than silently inventing the author’s meaning. Pause the exercise if confusion affects the whole brief. The facilitator should protect the working conditions, not treat silence as more important than understanding.

Follow one idea as it changes

In our hypothetical hire business, one sheet begins with three different directions: a readiness message, an accessory check and a named collection contact. Consider how the accessory idea could develop across later rows.

The first entry proposes checking accessories when the main item is prepared. Another participant notices a practical gap: an item may be prepared in the morning but an accessory borrowed again before collection. Their addition proposes keeping the complete set together. A third participant asks what happens when the set cannot be completed and adds an exception route: contact the customer before confirming readiness.

Those are related contributions, but they are not interchangeable. One concerns a check, one concerns the physical organization of work, and one concerns an unresolved problem. Clustering all three under “checklist” would lose the most useful differences.

Now compare that chain with the readiness-message idea. Sending a message earlier could make the problem worse if the team has not established what “ready” means. This is a reason to connect the ideas and inspect their dependencies, not to conclude that messages never help. The worksheet has exposed an operational question that a quick vote might have missed.

Look for that kind of development when reviewing the sheets: a suggestion becomes more specific as other people bring different knowledge to it.

Turn the pages into a next step

After writing, leave time to read the full collection. Ask for clarification before evaluation. Give related ideas working labels, but retain their individual references so that an interesting detail does not disappear into a broad category.

For the hire business, the team could compare three options: improving readiness information, changing preparation and storage, or providing earlier personal contact. Discuss what each option would need to be true. Would staff have enough information to confirm readiness? Could a complete set remain together? Would an earlier contact reach the customer in time?

Use assumption mapping to select the consequential uncertainty, then assign a manageable investigation. A possible next step is to walk through a small set of collection preparations and examine when completeness can actually be confirmed. That is a proposed check, not evidence that the resulting service will be successful.

Keep unselected ideas with a brief reason: outside present authority, overlaps another option, depends on an unanswered question, or not relevant to the agreed problem. Tell participants who will review the next evidence and when they can expect an update. This gives the writing a destination without pretending every idea deserves development.

What the evidence does—and does not—support

Paulus and Yang’s 2000 study examined written idea exchange, including attention to others’ ideas and subsequent reflection. Its abstract reports advantages for sharing groups under the studied conditions. That supports interest in how an exchange is organized; it does not establish that a standard 6-3-5 workshop always beats other methods or produces commercially valuable innovations.

Writing simultaneously removes the need to wait for a speaking turn during that phase. It does not remove status differences, shared blind spots, fear of later judgment or poor problem framing. Nor should the method be assigned according to simplistic labels about “creative people” or “introverts.” Ask what helps the actual participants contribute.

Use brainwriting as one part of the movement from exploration to focus. The strongest sign of a useful session is not a large number at the top of a slide. It is that the team can explain its different options, see what it still does not know and take a responsible next step.