What is brainstorming in UX?

What a brainstorm is for

Brainstorming sits in the ideation stage, after you understand the problem and before you commit to a direction. Its job is breadth. You want a wide pile of options so that the one you eventually pick has beaten some real alternatives.

It does not replace research. If the team does not know who the users are or what is going wrong, a brainstorm just produces confident guesses. The better your problem statement, the better the ideas.

The ground rules that actually matter

Most facilitators repeat a handful of rules, and they exist for good reasons:

• Defer judgment. Criticizing an idea while it is still being spoken teaches everyone to stay quiet.
• Go for quantity. The first ideas tend to be the obvious ones, and the interesting ones show up later.
• Build on each other. "Yes, and" beats "yes, but".
• Keep one conversation at a time.
• Stay on the question. A sharp prompt such as "How might we help first-time users finish setup?" works better than "Ideas for onboarding".

The rule people skip most is the first one. Within five minutes someone starts evaluating, and the energy drains.

Running a session, step by step

Start by stating the problem in one sentence and writing it where everyone can see it. Give people a few quiet minutes to write ideas on their own first. This matters more than it sounds, because group discussion alone tends to anchor on whatever is said first.

Then share, cluster similar ideas, and build on them together. Finish by voting, with each person getting a few dots to place on the ideas they find most promising. The votes are a starting point for discussion, not a verdict.

Set a timer, keep the group small, and include someone from outside design, such as a developer or a support agent. They know constraints and complaints you do not.

Why brainstorms sometimes disappoint

Research on group ideation has long suggested that people can generate more ideas working alone and pooling them later than they do talking in a room. That is why brainwriting, where everyone writes silently and swaps papers, has a loyal following.

Other failure modes are familiar: a senior person speaking first, no clear question, no follow-up. A pile of sticky notes that is photographed and never opened again is the real graveyard of brainstorming.

When to run one and when to skip it

Use brainstorming when the problem is open, such as how to explain a complex feature or how to help people return after a month away. Skip it when the answer is already known, or when constraints are so tight that there are really only two options. In those cases, just decide, or test the two options against each other.