Design thinking ideation: methods for the ideate stage

Ideation is the third stage of design thinking, after Empathize and Define and before Prototype. Its job is to generate a wide range of possible solutions to the "how might we" question you framed in the Define stage, with judgment held off until later. The stage works when you split it in two: first go wide and produce many divergent options, then narrow to a few worth prototyping. Skipping the divergent half is why most design thinking workshops prototype the first idea someone liked.

Design thinking is usually drawn as five stages: Empathize, Define, Ideate, Prototype, Test. Ideation is where the process either earns its reputation or wastes it. Done well, it produces options nobody walked in with. Done badly, it is a polite meeting that ratifies the solution the lead already had in mind, dressed up in sticky notes.

What is ideation in design thinking?

Ideation is the stage where a team generates as many possible solutions as it can to a clearly defined problem, deliberately favoring quantity and range over quality at first. It sits on the hinge of the design thinking diamond: everything before it narrows toward a problem statement, and ideation opens back up into a wide field of possible answers before the process narrows again toward a prototype.

The critical input is a sharp problem statement, usually written as a "how might we" question. "How might we help new users reach their first success in under five minutes?" gives a room something to push against. A vague brief like "improve onboarding" produces vague ideas. If the Define stage was rushed, no amount of clever ideation technique will rescue the session, because the team is generating answers to a question nobody agreed on.

What are the best ideation techniques for design thinking?

The strongest techniques all do the same thing: they force angles a group would not reach by talking freely. Freeform "any ideas?" brainstorming reliably produces the obvious handful and stops. Structured methods keep the divergent phase genuinely divergent. A few that earn their place:

Two of these deserve a closer look because designers reach for them most. SCAMPER is the workhorse of the "we have a product, make it different" case: it takes what exists and forces seven transformations, which is exactly how incremental innovation actually happens. And Crazy 8s is the sprint-week favorite because the eight-minute constraint kills perfectionism and the sketching bias suits a team that will prototype next.

How do you run a design thinking ideation session?

Run it in two clearly separated halves: diverge, then converge. In the divergent half, the rule is deferred judgment: no criticism, quantity over quality, and wild ideas welcomed because they stretch the range even when they are unusable themselves. Give everyone time to generate alone before the group builds together, which captures the ideas that a fast-talking room would trample. Fifteen to twenty minutes of real divergence is plenty; the well runs dry faster than people expect, and that is fine.

In the convergent half, the mode flips. Now you cluster the ideas into themes, compare them honestly, and narrow to the two or three worth prototyping. This diverge-then-converge rhythm is the entire engine of design thinking, and our piece on divergent and convergent thinking covers why doing both in the same breath, judging as you generate, kills the range you were trying to create. The classic failure is a facilitator who lets the loudest participant evaluate ideas in real time, which quietly teaches everyone else to stop offering anything unusual.

What is the difference between brainstorming and ideation?

Brainstorming is one technique for ideation, not a synonym for it. Ideation is the whole stage of generating and then narrowing solutions; brainstorming is a specific method within it, and often not the best one. Treating the two as identical is why so many teams believe they are "doing ideation" when they are really just running an unstructured group brainstorm, which research has shown produces fewer and less original ideas than the same people working first alone.

The practical upshot is to stop defaulting to a group talking in a room. That format suffers from production blocking, where only one person speaks at a time, and from anchoring on the first idea voiced. Methods like brainwriting and silent sketching sidestep both. If you want the evidence and the specific ways verbal group brainstorming underperforms, our article on why group brainstorming fails lays it out.

How many ideas should an ideation session produce?

Aim for far more than feels reasonable, because the useful ideas usually live past the obvious ones. A rough target is 40 to 100 raw ideas from a small group in a single session, knowing that most will be discarded. The first ten ideas are almost always the ones everyone already had walking in; the range that makes ideation worth the calendar time starts after the room has exhausted the familiar and is forced to reach.

Quantity is not the goal for its own sake, it is the mechanism. A larger pool means a wider spread of approaches, and a wider spread means the converge step has something real to choose between rather than three variations on one theme. Once you have the pile, the honest work is testing which ideas survive contact with a real user, so build the two or three finalists cheaply and watch what people actually do with them instead of debating in the room which one is best.

What comes after ideation?

Prototyping comes next: you take the two or three ideas that survived the converge step and build the cheapest possible version of each to learn from. The point of narrowing during ideation is to hand Prototype a manageable shortlist, not a single predetermined winner, so the team is still learning rather than executing. Then Test puts those prototypes in front of real users, and what you learn often sends you back to Define with a sharper problem.

The step that connects ideation to prototyping cleanly is scoring, deciding which ideas earn the prototype budget. Doing it on impact against effort, with the reasoning written down, keeps the choice defensible when a stakeholder asks why their favorite got cut. Our approach to idea prioritization walks through the scoring, and the idea generator covers the front half, producing the wide, genuinely different field that makes the whole design thinking process worth running.

The short version

Ideation is the design thinking stage where you generate many possible solutions to a sharp problem, then narrow to a few worth building. It succeeds when you separate divergence from convergence: go wide with structured techniques and deferred judgment first, then cluster and score to reach a prototype-ready shortlist. Frame the problem tightly before you start, generate more ideas than feels comfortable, and never let evaluation sneak into the generating half. That separation is the whole discipline.