How might we, reframe this problem, turn this into an opportunity, HMW questions. Reframe problems as actionable opportunity questions using the Basadur/P&G HMW technique.
Scanned 5/27/2026
Install via CLI
openskills install radesjardins/RAD-Claude-Skills---
name: how-might-we
description: >
How might we, reframe this problem, turn this into an opportunity, HMW questions.
Reframe problems as actionable opportunity questions using the Basadur/P&G HMW
technique.
argument-hint: "[problem or challenge to reframe]"
---
Generate "How Might We" questions for: **$ARGUMENTS**
The HMW technique (Min Basadur, P&G 1970s) reframes problems as actionable opportunity questions. The three words matter:
- "How" — assumes there IS a solution
- "Might" — exploring possibilities, not committing
- "We" — collaborative
## Step 1: Understand the Problem Space
Ask 2-3 clarifying questions to understand the core problem, who it affects, and what success looks like.
## Step 2: Scope Calibration
The HMW must be neither too broad nor too narrow:
- Too broad: "How might we fix healthcare?" (no direction)
- Too narrow: "How might we add a button here?" (too constrained)
- Just right: "How might we help patients find the right specialist within minutes?" (multiple solution paths possible)
## Step 3: Generate HMW Questions
Generate 8-12 HMW questions that reframe different aspects of the problem. Vary the angle:
- Different stakeholders: "HMW help [user type] to..."
- Different moments: "HMW make [experience] better at the point of..."
- Different constraints: "HMW achieve [goal] without [current limitation]..."
- Challenge assumptions: "HMW [do the opposite of current approach]..."
## Step 4: Select and Expand
Help the user pick the 2-3 most promising HMW questions, then generate 3-5 solution ideas for each.
Follow the anti-anchoring protocol from `references/facilitation-principles.md`: ask the user what aspects of the problem feel most important before generating HMW questions.
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.