25 questions that open a brainstorm, and 5 that kill it

Run this method in IdeaHone
Creates a space with the entities and scoring criteria of this method, ready for your next session.
The question the facilitator asks decides what the room produces. "Any ideas?" produces silence, or the same three ideas the loudest person brought into the meeting. This is a list to bookmark: 25 questions in five sets that open a brainstorm, five that quietly close it, and a short routine for using them.
Why the question matters
A brainstorm is a series of prompts, and each one points the team at a different corner of the problem. A vague prompt gets vague answers. A specific one, left on the wall, gets twelve answers from twelve people in two minutes.
25 questions that open a brainstorm
1. Start from the customer
Use it when the team talks more about the product than about the people who use it.
- What does the customer do the minute before they need us?
- What does the customer do the minute after they are done with us?
- What do they say to a colleague when it goes wrong?
- Which step do they skip when nobody is watching?
- What would they pay to never have to do again?
2. Remove constraints
Use it when every idea arrives with a "but" attached.
- If it had to cost nothing, how would we do it?
- If we had to ship it by Friday, what would we leave out?
- If we had ten times the budget, what would we do first?
- If the current rules did not exist, what would we try tomorrow?
- If only one person could work on it, what would that person do?
3. Flip it
Use it when the room is polite and the ideas are safe.
- How would we make this worse on purpose?
- How would we guarantee that nobody uses it?
- What are we doing today that makes the problem bigger?
- What would we have to stop doing for the problem to solve itself?
- What would a competitor have to do to make us look slow?
4. Borrow from elsewhere
Use it when the team has run out of its own answers.
- How would a hotel solve this?
- How would an airline solve this at the gate?
- How would a video game keep people coming back to this?
- How would a hospital make this safe?
- How would a street market handle this with no software at all?
5. Go concrete
Use it last, when the wall is full and nothing is small enough to start.
- What could we test next Tuesday?
- What is the smallest version a single customer would notice?
- Who could we call this afternoon to find out?
- What would we build if we had only paper and a phone?
- Which of these could one person finish before lunch?
5 questions that kill a brainstorm
- "Any ideas?" No edge. The usual voices speak and everyone else waits.
- "Who has a better idea?" You have just told the last speaker their idea was not good enough. The next three people keep theirs to themselves.
- "How much would that cost?" Fair, but three hours too early. During generation it turns every idea into a budget discussion, and the small ideas win by default.
- "Has anyone done this before?" If yes, the idea is not original. If no, it is risky. It loses either way.
- "Are we sure that's realistic?" Nobody is sure. Asked to defend a five-minute-old idea, most people drop it instead.
How to use them
- Pick two sets that fit the problem. A customer problem gets sets 1 and 4, a stuck team gets 2 and 3. Set 5 always comes last. Choose before the session, not in it.
- Ask one question at a time and give two minutes of silent writing. Say it out loud, write it on the wall, then say nothing. The quiet people get the same two minutes as the loud ones.
- Write every answer down with the name. Not for credit, for the follow-up: three weeks later you need to know whom to ask what it meant.
- Move on before the energy drops. When the writing slows, ask the next question. Do not wait for the last person to finish.
- Park the evaluation until the end. Any "that will not work" goes on a separate sheet and the session continues. Evaluate everything at once at the end, for example with an impact and effort matrix.
Write the question on the wall in large letters and leave it there for the whole round. People look up mid-sentence to check what they were asked. A spoken question is forgotten after the second answer.
Three ways to waste a good question
- Asking all 25. The list is a menu, not a script. Two sets, well chosen, beat five sets rushed.
- Reading the question from a slide. The next slide replaces it and the room loses its anchor.
- Answering your own question first. Your example becomes the template and the next ten answers are variations of it.
The 90-minute ideation workshop agenda has a slot for exactly this.
Capture every idea while people talk
IdeaHone listens in your session and turns what people say into idea cards, questions and decisions, live on a shared board.
What is a good question to start a brainstorm?
One about the customer, not the solution. "What does the customer do the minute before they need us?" gives everyone something concrete to write, and the first answers set the level for the session.
How many questions should I ask in a brainstorm?
Between five and ten, in one or two sets, each with two minutes of silent writing. More than that and the answers get shorter and vaguer with every round.
Why does my team go quiet in brainstorms?
Usually the question is too open, the evaluation starts too early, or one person answers first and everyone else waits. One specific question, two minutes of silent writing and evaluation parked until the end fix most of it.