What it is
A technique that turns an insight or problem into a “How might we…” question, phrased broadly enough to invite many ideas but narrowly enough to stay actionable. It bridges synthesis and ideation.
When to use it
At the handoff from Synthesize to Ideate, once you have insights or problem statements and are ready to generate solutions.
Why (value)
Converts problems into generative prompts, keeps ideation optimistic and open, and prevents jumping to a single solution too early.
How to run it
- Start from a key insight or problem statement.
- Rephrase it as “How might we [enable outcome] for [user]?”
- Check the scope, too broad yields vague ideas, too narrow smuggles in a solution.
- Generate several HMW questions and pick the most promising.
- Use them as prompts for ideation.
Inputs and outputs
- Inputs: Insights, problem statements, or research findings.
- Outputs: A set of well-scoped HMW questions to drive ideation.
Time and effort
Low. Minutes, often part of a workshop.
Evidence and limitations
A framing device, not evidence. The insight behind the HMW should be evidence-based; the question itself only shapes ideation. See Evidence and limitations.
Tips and pitfalls
- Avoid embedding a solution in the question.
- Tune the scope so it is neither vague nor prescriptive.
- Generate several and choose, do not settle on the first.
Variations
Point-of-view to HMW pipelines, amplify/remove/challenge reframes.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Problem statements — A crisp, shared articulation of the problem worth solving, before anyone jumps to solutions.
- Brainstorming — Generate a large volume of ideas quickly by deferring judgment.
- Opportunity solution trees — Connect a desired outcome to the opportunities that drive it and the solutions that address them.
