Why Most Designers Fail at the Ideate Stage (A Product Designer’s Perspective)
Ideation stalls because teams generate ideas instead of framing them. A practical structure for getting to solutions that are actually worth testing.
Most design teams do not have an ideation problem. They have a framing problem. They arrive at the ideate stage with a solution-shaped brief, and so they generate variations on a decision that was never consciously made.
Framing before generating
A useful How Might We question is not a paraphrase of the feature request. It has to hold the constraints loosely enough that a genuinely different answer survives, and tightly enough that it still points at a real user problem.
If your questions all contain words like "screen", "flow", or "feature", you have already chosen the answer. The test is whether two people in the room could reasonably propose opposite solutions.
Diverge by constraint, not by volume
Thirty ideas in ten minutes produces thirty variations of whatever the loudest person said. A better approach is to force a different lens on each round.
- Invert the assumption. If we assume users will not read this, what would we build?
- Change the actor. What would a first-time user need that a returning one would not?
- Remove a constraint. What is possible if we had no technical limitation at all?
- Push the timeframe. What would this look like if it only had to work in five years?
Converge on a bet, not a favourite
The failure mode at convergence is selecting the idea the team enjoyed most, or the one the most senior person defended hardest. Instead, converge on the cheapest thing that would teach you the most.
That usually means a prototype rough enough to be embarrassing. Its roughness is the point: it forces the conversation onto whether the assumption holds, rather than whether the craft is good.