SUMMARY
Purpose: To reframe user problems or insights into open-ended design opportunities that encourage creative exploration.
Design Thinking Phase: Define
Time: 45â60 min session + 1â2 hours analysis
Difficulty: ââ
When to use: After synthesising research into clear findings To align cross-functional teams around actionable problem statements Before ideation or sprint planning
What it is
âHow Might Weâ (HMW) is a problem framing technique used to translate user insights into structured prompts for ideation. It reframes challenges as opportunities by asking, âHow might weâŚâ followed by a targeted problem or potential.
đş Video by DAN Innovation Council. Embedded for educational reference.
Why it matters
HMW questions enable product teams to shift from problem-focused mindsets to solution-focused thinking. By framing insights in an open but bounded way, teams can spark collaborative ideation without jumping to solutions too early. It aligns everyoneâfrom stakeholders to engineersâaround purposeful design problems.
When to use
- Right after affinity mapping or thematic research synthesis
- When reframing vague stakeholder problems into user-centred opportunity areas
- Before ideation workshops, sprints, or co-design sessions
Benefits
- Rich Insights: Helps uncover user needs that arenât visible in metrics.
- Flexibility: Works across various project types and timelines.
- User Empathy: Deepens understanding of behaviours and motivations.
How to use it
- Gather key user insights or pain points from research (e.g., interview quotes, usability data).
- Identify the core challenge behind each insight â what problem is it pointing to?
- Reframe that problem into a question using âHow might weâŚâ language. Keep it optimistic and open-ended, but specific enough to tackle in ideation.
- Write multiple variations if needed â different angles can lead to different solution spaces.
- Cluster or prioritise HMW questions based on feasibility, impact, or strategic fit before moving into ideation.
Example Output
From the insight âUsers abandon the checkout when shipping options are unclear,â we might generate:
- How might we help users feel more confident about shipping timelines?
- How might we make delivery expectations clearer during checkout?
- How might we reduce uncertainty around shipping costs early in the journey?
Common Pitfalls
- Too vague: âHow might we improve the experience?â lacks direction and wonât guide ideation effectively.
- Too narrow: âHow might we add a chatbot?â forces a specific solution, limiting creative options.
- Not rooted in research: Skipping the insight phase can result in poorly framed or irrelevant questions.
10 Design-Ready AI Prompts for How Might We â UX/UI Edition
How These Prompts Work (C.S.I.R. Framework)
Each of the templates below follows the C.S.I.R. method â a proven structure for writing clear, effective prompts that get better results from ChatGPT, Claude, Copilot, or any other LLM.
C.S.I.R. stands for:
- Context: Who you are and the UX situation you're working in
- Specific Info: Key design inputs, tasks, or constraints the AI should consider
- Intent: What you want the AI to help you achieve
- Response Format: The structure or format you want the AI to return (e.g. checklist, table, journey map)
Level up your career with smarter AI prompts. Get templates used by UX leaders â no guesswork, just results. Design faster, research smarter, and ship with confidence. First oneâs free. Unlock all 10 by becoming a member.
Prompt Template 1: âGenerate How Might We questions from a research insightâ
Generate How Might We questions from a research insight
Context: You are a Product Designer synthesising findings from a usability study on [checkout experience].
Specific Info: One key insight shows that users [abandon the process] when they encounter [surprise costs at the final step].
Intent: Transform this insight into a variety of HMW prompts suitable for a design sprint.
Response Format: Return a list of 5â7 âHow might weâŚâ questions with a note on what aspect each one frames (e.g., clarity, trust, timing).
Ask for clarification if the insight lacks user behaviour detail.
Offer one idea for reframing the insight if better HMW questions could emerge.