methodatlas
RunsheetInnovation

Brainstorming

ComplexityLow
Time30-60 min
Participants4-12
FormatWorkshop
MaturityCanonical
01

Prerequisite

What needs to be finished first

Complete firstChallenge formulation

A concrete challenge or How-Might-We question exists that is open enough for many ideas but narrow enough to keep focus.

Without: Without a clear challenge, brainstorming drifts in all directions and produces no usable output.
Complete firstShared contextnot in catalog

All participants share a basic understanding of the problem or domain, ideally through a prior research session or briefing.

Without: Without context, ideas emerge from different backgrounds and cannot be compared.
02

Preparation

What needs to be ready before start

Materials

Whiteboard or digital board (Miro, FigJam); sticky notes in one color for ideas; markers; timer; challenge question clearly visible.

People / roles

One facilitator to hold the rules and timer; 4-12 participants from different functions; optionally a scribe for notes or combinations.

Pre-read

Challenge question; domain context (1-2 slides or briefing document); examples of good and bad idea stickies; constraints that ideas must not violate.

Time needed

30-60 min

Setup

Put the challenge at the top of the wall. Make the rules visible: 1) quantity before quality, 2) wild ideas welcome, 3) build on ideas, 4) no criticism. Set the timer to 15 min ideation. Lay out the sticky notes.

03

Core question

The one question this method answers

What range of solution ideas can we generate for the challenge before we converge and choose?

04

Flow

Marker: Phase

StepDurationActionHint
1Phase 1: Briefing and rules
5-10 minRead the challenge aloud and recap the context (3-5 min). Explain the four brainstorming rules and post them on the wall. Show example stickies.Simply reading the rules is not enough. If someone breaks them (criticism, veto), redirect to the rule immediately. Otherwise the method tips over.
2Phase 2: Solo warm-up
5 minEach person writes first ideas alone on sticky notes (at least 5). Silence. Do not share yet.Starting solo avoids anchor bias from loud voices. If you start in plenary right away, you get groupthink.
3Phase 3: Group ideation
15-25 minPlace stickies on the wall and briefly describe them. Others build on them ('Yes-and' stickies). The facilitator keeps the pace high and pushes for wild variants.If energy drops, offer a new prompt variant ('How would Apple solve this?', 'What would be the most absurd solution?'). Provocations create leaps.
4Phase 4: Cluster and review
10-15 minGroup similar ideas. Consolidate duplicates. Add a label per cluster. If there are too many clusters, narrow them down to 5-8 main themes.Affinity mapping is for condensation, not evaluation. Evaluation comes in the next phase.
5Phase 5: Converge (voting or shortlist)
10-15 minUse dot voting (3-5 dots per person) or a structured discussion. Mark the top 5 or top 3 ideas. Name an owner per top idea for follow-up detail work.Voting is not a decision. It is a preselection for detailing. The final decision comes later from the decider with criteria.
05

Artifact

What comes out at the end

Form

Brainstorming board (photo or export) with all ideas, clustered themes, and the top selection; shortlist as a separate list with owner and next step (prototyping, experiment, detailing).

Versioning / ownership

Create a separate snapshot per session with date and challenge. If the shortlist is later discarded or expanded, link it in the follow-up document. Compare versions for repeated challenges across sessions.

Tool alternatives
  • Miro or FigJam with a sticky-note board
  • Mural with a brainstorming template
  • Physical wall with sticky notes and photo
  • Notion list for asynchronous brainstorming
  • Slack channel thread for distributed collection

brainstorming-working-template.md

Compact working template for Brainstorming with context, input, output artifacts, and next step.

Brainstorming Working Template

Goal

Generates many ideas quickly in a judgment-free space.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Idea Pool:
  • Theme Clusters:
  • Shortlist:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

06

Example output

Concrete filled scenario, fictional example

brainstorming-beispiel.md

Concrete filled scenario, fictional example

Brainstorming — Activation Q3 (CW 19/2026)

Challenge (HMW): "How might we get solo tax advisors to experience an aha moment in the first session?"

Participants: 7 people (Product Triad + Sales + Support + 2 designers)

Output: 67 idea stickies in 20 min ideation

Clusters (8 themes)

  1. "Pre-fill demo data" (12 stickies)
  2. "Make DATEV export more prominent" (10 stickies)
  3. "First steps wizard" (9 stickies)
  4. "Personalized onboarding after signup question" (8 stickies)
  5. "Live coach session included" (7 stickies)
  6. "Interactive tutorial on site" (6 stickies)
  7. "Migration magic from old software" (6 stickies)
  8. "Aha moment video as trailer" (3 stickies)

Top 3 after voting (5 dots/person)

  1. "Pre-fill demo data" (15 dots) - owner @lisa, prototype in CW 22
  2. "Make DATEV export more prominent" (12 dots) - owner @anna, solution sprint in CW 21
  3. "Migration magic" (9 dots) - owner @ben, discovery spike in CW 22 (feasibility unclear)

Parked (wild ideas for the backlog)

  • "Aha moment video as trailer" (creative, but low votes)
  • "Live coach session included" (potentially high effort, discuss separately)
07

Pitfalls

Recognize symptoms and steer against them

Trap

Criticism during ideation

Symptom

"That won't work because ..." stops the idea flow and quantity collapses.

What to do

State the no-criticism rule explicitly and repeatedly. The facilitator interrupts immediately. Park skeptical voices in a separate "risks" column, not in discussion.

Trap

Loud voices dominate

Symptom

Two or three people produce 80% of the ideas and the rest stays quiet.

What to do

Use a solo phase first, add a brainwriting element, and do round robin with one idea per person. Make sure every voice gets space.

Trap

Challenge is too narrow

Symptom

The challenge is effectively a solution question ('How do we build feature X?'), so the ideas are redundant.

What to do

Reformulate the challenge as an open HMW question about outcome, not solution. 'How do we help users with Y?' instead of 'How do we build X?'

Trap

Forgetting convergence

Symptom

100 ideas are generated, nobody chooses, and everything stays open.

What to do

Plan a convergence phase as mandatory. Brainstorming without a shortlist is just busywork. Vote or let the decider choose in the same session.

Trap

No shared context

Symptom

Ideas come from completely different mental models and cannot be compared.

What to do

Run a briefing or research walkthrough before brainstorming. At minimum, surface a shared persona, pain points, and constraints.

08

Stop criteria

Done signals checkable in under a minute

The challenge is not clearly formulated or keeps changing.
Participants have no domain understanding, so ideas would be ungrounded.
The political climate makes the no-criticism rule impossible to hold.
Convergence is excluded (the stakeholder wants to pursue all ideas).
The group has fewer than 3 people, so the method becomes one-sided.
The stakeholder expects a decision, not options. Wrong method.

Finished the runsheet?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.