Framework · Facilitation techniques · 2 min read
How Might We
Reframe pain points as "How might we…?" questions: narrow enough to act on, broad enough to allow options.
- 1Pain point
Start from one real problem, with evidence from research or data.
"Planners re-enter the same order twice." - 2Reframe
Rewrite it as "How might we…?". One question per sticky.
"How might we enter an order once?" - 3Check scope
Narrow enough to act on, broad enough to allow several ideas.
Not "a button", not "fix planning" - 4Vote
Dot-vote the strongest questions and use the winners as ideation prompts.
Next: Crazy 8s on the top two
Use it when
- You have research findings or a list of pain points and the group wants to jump straight to solutions.
- You need ideation prompts for a session with Crazy 8s or Brainwriting 6-3-5.
- Stakeholders describe the problem as a feature request ("we need a dashboard") and you want to open the question again.
How to use it
- Start from real pain points. Put the findings on the board: quotes, observations, data. Each pain point should come from evidence, not opinion. Output: a list of pain points the group agrees are real.
- Write HMW questions, one per sticky. Everyone writes alone and in silence. Turn each pain point into "How might we…?", for example "Planners enter the same order twice" becomes "How might we let planners enter an order only once?". Output: many HMW stickies. 5–10 minutes.
- Check the scope of each question. Remove the solution from questions that contain one ("…add a copy button?"). Narrow down questions that are too wide ("…improve planning?"). Output: questions that allow several different ideas.
- Cluster and vote. Group similar questions, then dot-vote the ones the group most wants to work on. Output: the top two or three HMW questions.
- Use the winners as ideation prompts. Write each winning question at the top of the next activity. Output: the prompts for ideation. About 20 minutes for the whole HMW step.
Worked example
A UX lead facilitates a session with a product manager, two designers and three developers on an internal operations platform. Research showed planners lose time switching between apps.
| Pain point (from research) | First HMW (written) | Improved HMW |
|---|---|---|
| "I copy the order number into three apps." | How might we add a copy button? | How might we let planners enter an order only once? |
| Planners miss urgent changes. | How might we improve planning? | How might we make urgent changes impossible to miss? |
| New planners ask colleagues which app to use. | How might we help new planners know where each task happens? | (kept as written) |
The group votes for the first two questions and runs Crazy 8s on each.
Watch out for
- A solution hidden in the question. "How might we add a filter?" allows only one answer. Ask "why would they want a filter?" and write that instead.
- Questions that are too broad. "How might we make users happy?" gives no direction. Anchor each question in one user and one pain point.
- Skipping the evidence. HMW questions built on guesses produce ideas for problems nobody has. Link each question to a finding.
- Too many winners. Ten questions dilute the ideation. Pick two or three.
Template
Use one line per sticky and check each question before you vote.
HOW MIGHT WE
Pain point (with evidence): _______________________________
How might we ______________________________________________?
Check:
[ ] It does not name a solution
[ ] It is about one user and one problem
[ ] At least three different ideas could answer it
Votes: ____ Used as prompt for: ______________ (e.g. Crazy 8s)
- SprintJake Knapp, John Zeratsky & Braden KowitzBook · 2016
Saved only on this device.