The Brainstorming Myth: More Ideas Do Not Always Mean Better Choices

How should your team choose what to do after a brainstorming session fills the wall with sticky notes? Brainstorming does not produce better choices simply by producing more ideas. The useful work begins when the group agrees what it is trying to choose, then selects ideas against that purpose.

A large collection can be valuable: it may reveal unexpected possibilities and give quieter contributors a way in. But generation and selection are different tasks. If you ask a group to do both at once, fast reactions, seniority and personal attachment can steer the result before the options have been understood.

There is no single selection method that suits every team. A quick sort works when the decision is modest and the group already shares its aim. A criteria-led comparison helps when ideas compete on different merits. A small trial can help when discussion cannot settle a practical uncertainty. The right choice depends on the consequence of the decision, the time available and what the group needs to learn.

Separate making options from choosing among them

During idea generation, invite possibilities without asking each contributor to defend one. Capture ideas in visible, neutral language. A facilitator can write each suggestion on a separate sticky note or in a shared document, and check that the wording reflects the contributor’s intent.

Then pause before judging. Grouping similar suggestions can help, but do not merge ideas just because they share a few words. Keep differences that might change the work: one proposal may invite customers to a conversation, while another may ask them to complete a form. Those are distinct approaches, not duplicates.

When a team moves straight from suggestion to evaluation, people often start arguing for their own contributions. A separate selection conversation gives the group room to ask what each option would involve and how well it answers the actual need. It also makes it easier to recognise a useful part of an idea without adopting the whole proposal.

Agree the selection question before inspecting the wall. “Which ideas are most exciting?” is a loose prompt; “Which changes could help new members understand how to join our project?” gives the group something concrete to assess. If the real decision is about what to try first, say so. Choosing a first trial is not the same as declaring the best possible solution.

A quick sort suits low-stakes decisions

A quick sort is useful when the team needs to narrow a manageable set of suggestions and the cost of revisiting the choice is low. Put the ideas where everyone can see them, restate the selection question, and invite each person to identify the options that appear to answer it. The group can then discuss the candidates that receive interest from more than one contributor.

This approach is easy to run with a marker and a whiteboard, paper cards, or a shared board such as Miro. It keeps the conversation moving and gives the group an initial sense of where attention lies. Use it to create a shortlist, not as an automatic verdict: the number of marks is not a measure of whether an idea is workable or fair.

A quick sort particularly suits a team choosing a theme for a low-stakes activity, or deciding which of several comparable suggestions to discuss further. It is less suitable when one person’s preference could carry much more weight than another’s. Before marking, ask whether everyone understands the question and feels able to take part. If not, give people quiet time to consider the ideas before opening the discussion.

After the sort, ask what attracted the group to the leading options. One idea may be popular because it sounds lively, while another addresses the team’s stated need more directly. That distinction helps prevent a shortlist from inheriting the same popularity bias that shaped the first reaction.

Compare ideas against agreed criteria

A criteria-led comparison suits choices where the team needs to balance several considerations. Agree a small set of criteria before ranking the options. Depending on the decision, these might include relevance to the brief, effort required, accessibility for the people affected, or whether the team can learn from the result.

Keep the criteria distinct and explain what each means in this decision. “Impact” can mean different things to different people; ask the group to describe the observable change it has in mind. If the team cannot say how a criterion would affect its choice, it may be too vague to help.

Put the options and criteria in a simple table on paper or in a shared spreadsheet. Discuss each idea in turn, noting what the team knows and what it is assuming. A score can help organise a conversation, but it should not conceal uncertainty or turn an impression into a precise verdict. Leave space for comments when two ideas have different strengths.

This approach is useful when a decision involves trade-offs. An idea could be appealing but take substantial coordination; another could be modest yet directly address the brief. The comparison makes those differences discussable instead of allowing one attractive feature to dominate. It also gives the group a reason to revisit its choice if the brief changes.

Criteria-led comparison takes more attention than a quick sort. Avoid it when the options are already alike and the decision is easily reversible. It can also become cumbersome if the team keeps adding criteria to defend a preferred idea. Settle the criteria first, and add one only if the group can explain why it changes the decision.

Use a small trial when discussion cannot settle a question

Sometimes the team is not divided because people have different values; they are making different predictions. One person expects a new format to make a workshop easier to follow. Another thinks it will make participation harder. If the disputed point can be observed safely and fairly, a small trial may be more useful than a longer argument.

Define the question the trial is meant to answer, who will take part and what the team will notice. Keep the trial limited enough that the group can learn without committing to a full change. Decide in advance what would count as a reason to keep, adapt or stop the idea. Those are practical decision cues, not proof that the approach will work in every setting.

This option suits decisions where the team can make a reversible, low-risk trial and observe a relevant outcome. It does not suit choices that affect people’s safety, rights or essential access, or situations where a poor trial would create harm. In those cases, use appropriate professional judgement and the relevant organisational processes rather than experimenting informally.

A trial also needs a fair comparison. If one option gets clearer instructions, more support or a more convenient setting, the team may learn more about those conditions than about the idea itself. Keep the test focused, invite feedback from the people affected and record what remains uncertain. The group can then make a more informed next decision without pretending it has resolved every question.

Choose a selection approach that fits the decision

Say your team has collected ideas for helping new volunteers find their first task. One suggestion is a welcome message with links; another is a short conversation with a returning volunteer. The group’s selection question is: “Which first contact helps a new volunteer know what to do next?”

If the team only needs a shortlist for discussion, a quick sort may be enough. If it must weigh staff effort against the clarity of each option, agreed criteria will make the trade-off visible. If members disagree about whether a conversation actually clarifies the next task, a small trial with willing participants could help answer that question. These are different routes to a decision, not a ladder that every team has to climb.

Before choosing, ask whether the decision can be changed later, how much is at stake and what information is missing. Use the lightest approach that answers those needs. A choice that is easy to reverse rarely needs elaborate scoring. A decision with significant consequences deserves a clearer process and input from the people it affects.

What should your team ask after brainstorming?

Make the decision visible to the group

Once the team chooses, record the selection question, the approach used and the reason for the decision in a place contributors can find, such as the project board or shared notes. Note who is responsible for the next action and what would prompt the group to reconsider. This prevents a shortlist or vote from being mistaken for an unchangeable commitment.

Brainstorming serves the team when it expands what the group can consider; it does not decide which option deserves the work. A clear selection question gives the team a common standard, while a suitable method helps it use that standard without mistaking noise, enthusiasm or apparent precision for a better choice. When the options are still close, keep the uncertainty visible and make the next decision deliberately.