Brainstorming: ideas can disappear while everyone waits to speak
Combine individual idea generation with shared development and selection so brainstorming produces real alternatives for one business task.
Article language: English

In this article
A form idea appears on the board. Someone suggests a shorter form, someone a form with a photo, someone a form with a different button. The meeting continues, sticky notes multiply and the team has spent half an hour considering one family of solutions. At the end everyone feels they have worked hard. Perhaps they have. It is still unclear whether they considered genuinely different possibilities.
Imagine a shoe-repair workshop that wants to handle website enquiries better. It is not looking for an advertising slogan. It wants to help a person who does not know whether their case can be assessed initially at a distance. The owner, a craftsperson and the person answering messages meet to invent a solution. Each knows a different part of the task. If the first contribution immediately fixes the format, some of that knowledge may never reach the options considered.
Brainstorming should help create possibilities. They must then be developed and something chosen for further testing. These tasks are related but require different work. A conversation that invents, persuades, refines and approves simultaneously may reward the ability to speak quickly above all. A company need not abandon working together. It should know when it needs independent ideas and when it needs mutual explanation.
Start with one question worth answering in several ways
“How do we improve the website?” is broad enough to include a new button colour, a shoe collection service and a change to the whole offer. Such proposals are hard to compare meaningfully. In our example ask: “How can we help a customer provide the material needed for an initial assessment before bringing in the shoes?” This still leaves several routes but connects them to one customer task.
Do not narrow the question to “which fields should the form have?” if the company has not decided that a form is the right route. That question contains the solution before work begins. Participants may do the task well yet never consider another contact method. State honestly what is already decided and what remains open.
State important constraints separately. Suppose the workshop does not confirm repair feasibility from photographs alone. This is a condition of the example, not a claim about all repairers. Proposals should help with first contact and the next step. They should not promise automatic diagnosis or decide a case for which the craftsperson needs to inspect the item.
Shared input can contain several real kinds of enquiry, with data participants do not need removed. Distinguish what is known about enquiries from team assumptions. “Customers do not want to fill anything in” needs checking. If accepted unquestioned, it eliminates a whole group of possibilities based on an untested opinion.
Creating alternatives also differs from a premortem, which considers possible causes of future failure (in Polish). Brainstorming seeks ways to do the task. A premortem can later reveal weaknesses in a chosen direction. If from the first minute every solution receives a list of reasons it will fail, the group may never develop a new possibility.
An independent start changes the material for discussion
Ask each person to write their own proposals before hearing the others. They should be able to finish their own line of thought and record a proposal the group can later understand. An idea should explain what the customer does and receives from the workshop. The word “video” alone is not enough.
Stroebe and Nijstad's 2004 publication describes research on production blocking caused by waiting for a turn to speak. It also considers conditions in which others' proposals stimulate thinking. Shared discussion can hinder one stage and help another; it is neither creative nor unnecessary by definition.
In our fictional workshop the owner writes down showing several typical cases with information on what material to prepare. The message handler proposes asking for a photo and one question about the desired result. The craftsperson first wants to distinguish cases where a photograph helps from those where the item must be inspected immediately. The proposals may partly combine, but arise from different observations.
If everyone starts with a spoken form proposal, the third possibility can easily become another form field. With an independent start it remains a visible question about the boundary of assessment. Only later does the group decide whether different case types need one entry point or different instructions. That distinction matters more than choosing between two similar sentences above a button.
In a hybrid meeting (in Polish), independent writing helps only if everyone can actually submit a proposal. A remote participant should not lose to people at the board because they cannot open the shared file. Agree how material can be contributed before discussion. Otherwise unequal tool access may be mistaken for a lack of ideas.
Developing an idea is not defending its author
After gathering proposals, check that you understand them. Ask what problem each solves and what it requires of customer and company. At this stage explanation is more valuable than an immediate vote. Two notes labelled “photos” may mean very different things: instructions for photographing shoes and a gallery of previous work. A common label does not make a common idea.

Likewise ten variants of one contact method are not automatically ten distinct possibilities. They can be grouped into one family while retaining meaningful differences. But do not flatten proposals merely because they use the same medium. A short video explaining how to prepare an enquiry and a video call with a craftsperson require different resources and create different contact.
Try developing a proposal you did not submit. The owner might add how to present the assessment boundary without sounding dismissive. The message handler can show which wording prompts unnecessary exchanges. The author still explains the intent but need not defend every original part as though their professional competence were at stake.
Keep a rejected branch with a short reason. If a video call is rejected because the workshop has nobody to run it, the reason concerns resources. If it cannot perform the needed assessment, the reason concerns usefulness. These can lead to different future decisions. “Too difficult” explains neither.
A company can invite its own customer advisory group to develop ideas when it wants to understand a particular audience's experience. The guide to a customer advisory group (in Polish) explains the role and limits of such a group. Do not treat a few favourable reactions as proof of demand or hand the group the whole decision. Customer opinion supplies knowledge about their task. The company still assesses feasibility and purpose.
Pause at an idea that answers a different question. Suppose someone proposes collecting shoes from home. It may be interesting, but changes the service itself rather than only preparation of the first enquiry. It should not compete with photo-submission instructions without explanation. It would require assessment of extra tasks and resources the group was not considering.
Keep it with the new question: “Does the company want to serve people who cannot deliver an item in person?” This preserves the idea while allowing the present work to finish. Moving a proposal to a separate discussion needs a concrete reason, not a way to remove an inconvenient opinion. If that need proves crucial, the team can consciously change scope rather than pretend it is still comparing small website changes.
Another case is automatic photo assessment. The craftsperson might say: “We cannot confirm repair feasibility from a photograph alone.” Separate helping prepare material from issuing an assessment. The first function may fit the original task; the second exceeds the agreed boundary. Keeping the useful part requires naming the difference, not smoothing the promise until it sounds more cautious.
These branches show why counting ideas and voting is insufficient. Some can be developed now; others need a prior service decision; others rely on a capability the company has not demonstrated. Recording the differences gives the decision-maker useful material. A list of names alone cannot distinguish a ready possibility from one dependent on several untested assumptions.
A full board still requires a choice
A 2006 study by Rietzschel, Nijstad and Stroebe compared generating and selecting ideas in different working arrangements. An advantage in the number generated did not translate into an advantage in the quality of selected solutions. This is a reason to prepare selection separately rather than treat a full board as a ready business answer.
Selection begins with a criterion tied to the task. For the workshop it might be whether a customer can provide useful material and understands what follows submission. The company's ability to handle the enquiry matters too. Presentation flair, affection for the author and the number of annotations around a note do not yet show whether a solution meets those conditions.
Choose two distinct proposals for preliminary versions. One presents case types and the subsequent contact method. The other guides preparation of a short enquiry. Entire functions need not be built immediately. First compare how an audience understands the task and what they intend to do. Comparing prototypes without a beauty contest (in Polish) helps keep attention on that difference.
Once the company has a direction and an unknown, it can prepare its own experiment with an explicit hypothesis. The guide to an experiment with an explicit hypothesis (in Polish) explains how to plan a test. That is the next stage. Brainstorming alone does not prove a new contact route will reduce messages or win more orders. It can provide sensible possibilities the company had not considered and reveal conditions for testing them.
For such work, Aeneia Design can connect content direction with website design: clarify the service, arrange necessary information and prepare contact suited to the audience's task. A starting point can be one difficulty in receiving enquiries, the existing offer and a few example cases. These materials can support real alternatives.
After the meeting, be able to name three things: which different possibilities emerged, which were developed and what justifies further work on the chosen proposal. Interesting branches that disappeared can still be revisited. An unclear chosen direction needs clarification. The number of sticky notes may remain a pleasant meeting memory. The substance of the recorded possibilities determines what the team can use.








