Every business runs the same meeting. Someone books a room, writes a problem on the whiteboard, and says the fatal words: “Okay — ideas?”
You know what happens next, because it happens everywhere. Silence. Then the boss floats a suggestion, and suddenly every “idea” for the next hour is a variation of the boss’s. The loudest person talks the most. The quiet analyst who actually understands the customers says nothing. Somebody shoots down the one genuinely interesting idea with “we tried something like that in 2019.” The meeting ends with three safe, forgettable options and a vague plan to “circle back.”
That’s not brainstorming. That’s a politeness ritual. And the reason design teams consistently out-ideate ordinary businesses isn’t talent — it’s that they’ve fixed the specific, predictable ways group idea-generation breaks. Here’s what breaks it, and the fixes you can run in your very next meeting.
Why normal brainstorms fail
Three quiet killers, all human nature:
Anchoring. The first idea spoken sets the gravity for the whole session. Everything after orbits it. If the boss speaks first — and the boss usually does — the room spends an hour decorating the boss’s idea.
Judging while generating. The instant someone responds to an idea with “yeah, but…” — cost, feasibility, “we tried it” — everyone else quietly edits themselves. The wild ideas, which are the raw material for the good ones, never get said at all. You can generate ideas or evaluate them, but doing both at once produces neither.
The loudness lottery. Talking in a group rewards confidence, not insight. The best ideas in your company are frequently in the heads least likely to fight for airtime.
Fix those three and the same people, in the same room, produce dramatically better raw material. Here’s how design teams do it.
Fix 1: Frame the problem as “How might we…”
Before generating anything, rewrite your problem as a question starting with “How might we…?” Not “our checkout has a 70% abandonment rate” (a complaint), and not “should we rebuild the checkout?” (a yes/no trap) — but “How might we make paying us feel effortless?”
The three words do real work. How presumes solutions exist. Might gives permission to be wrong, which is what lets unusual ideas out. We makes it collective rather than someone’s departmental problem. Get the altitude right, too: too narrow (“how might we shrink the checkout button copy”) strangles the session; too broad (“how might we be more innovative”) means nothing. Aim for a question your team could attack from five different directions.
Fix 2: Silence first — everyone writes before anyone speaks
This is the single highest-impact change, and it directly kills anchoring and the loudness lottery. Once the How Might We is on the wall, nobody talks. Everyone writes their own ideas on sticky notes — or sketches them — alone, for five to ten minutes.
Design teams often run this as Crazy 8s: fold a sheet of paper into eight panels and sketch eight different ideas in eight minutes, one a minute. The absurd time pressure is the point — it outruns your inner editor. Nobody’s judging the drawing; the sketch just forces an idea to become concrete enough to share.
Only when time’s up does anyone speak, and even then: each person presents their notes without interruption, and ideas go on the wall unattributed. The room reacts to ideas, not to who said them.
Fix 3: Chase quantity, and welcome the terrible
During generation, the only score that matters is how many. Not because volume is good in itself, but because the tenth idea is where the obvious ones run out and the interesting ones begin — and you can’t get to idea ten while the room is busy litigating idea two. So the rule is absolute: no evaluating, no “yeah but,” not even praise (praising one idea quietly judges the rest). Build on ideas — “yes, and…” — don’t weigh them.
Two tricks when the room stalls:
The worst possible idea. Ask everyone for the worst way to solve the problem — actively harmful, embarrassing, ridiculous. It’s funny, it destroys the fear of looking stupid, and then you flip it: invert each terrible idea and you’ll often find a genuinely fresh direction hiding inside. (“Make customers queue twice” flips into “what would make a second visit feel like a privilege?”)
SCAMPER the existing thing. Run your current product or process through seven blunt prompts — Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse. “What if we eliminated the quotation step entirely?” is the kind of question nobody asks unprompted and everyone should.
Fix 4: Converge like an adult — after, and only after
Generating wide is half the job; choosing well is the other half, and it needs different rules. Now judgement is welcome — but structured, so it isn’t the boss’s taste or the room’s fatigue deciding.
Dot-vote first: everyone gets three sticker-dots to place on the wall, silently, on the ideas they believe in. (If hierarchy is strong, the boss votes last.) Then take the leading handful and place them on a simple impact vs effort grid. High impact, low effort — do these. High impact, high effort — these are candidates for a proper look. Low impact — thank them and move on, whoever suggested them.
And the honest final step: the winning idea from even a great session is still a guess. The next move isn’t to build it — it’s to test it cheaply, which is a whole discipline of its own (we’ve written a full guide to prototype-first testing, including the Singapore grant that helps pay for it).
The whole recipe on one page
Next time, run it like this: one sharp How Might We on the wall → silent writing or Crazy 8s, ten minutes, no talking → post everything unattributed, no judging, build only → stuck? play worst idea or SCAMPER → then converge: dot-vote, boss last → impact/effort grid → and take the winner to a cheap prototype, not a build order.
Same team, same hour, same whiteboard. The only thing you’ve changed is the process — and the process was always the problem.
Where Oasis Web Asia comes in
We run exactly these sessions with clients at the start of projects — because the difference between a website, app, or AI tool that performs and one that just exists usually traces back to the quality of thinking before anything was built. If your team has a problem worth solving and a history of brainstorms that go nowhere, we can facilitate the session, bring the customer research that grounds it, and then test the winning ideas before you commit real budget. Understand first, ideate properly, prototype cheap, build once — that’s the whole philosophy.
If you’ve got a whiteboard full of the same three safe ideas, that’s exactly the conversation we like to have.
Start a conversation → — get a free consultation with our Singapore-based team.