how-might-we

Reframe customer problems into How Might We statements for design sprint ideation.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/coreyone/software-maestro --skill how-might-we-coreyone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: how-might-we
Source: https://github.com/coreyone/software-maestro/tree/main/design/sprints-and-ideation/how-might-we
Command: npx skills add https://github.com/coreyone/software-maestro --skill how-might-we-coreyone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams often jump straight to solutions or get stuck on vague problem statements, killing creative exploration before ideation even begins. This Skill converts raw customer friction points into calibrated How Might We (HMW) questions that open up diverse solution spaces without prescribing specific features. ## Core Features & Use Cases - 10 Reframing Lenses: Generates HMW statements across the IDEO and Stanford d.school angles including Amplify the Good, Question an Assumption, and Cross-Domain Analogy. - Goldilocks Calibration: Tests every statement to ensure it is neither too narrow (prescriptive UI solutions) nor too broad (unactionable abstractions). - Curated Prioritization: Scores candidates on actionability, generative potential, and strategic fit, then recommends one primary HMW with rationale. - Use Case: After customer interviews reveal that users abandon tax filing due to anxiety over entering 1099 numbers, use this Skill to produce 10 distinct reframed opportunity questions before running Crazy 8s sketching in a design sprint. ## Quick Start Reframe our onboarding drop-off problem into How Might We statements using the 10 IDEO reframing lenses and recommend the top one for our sprint.

Frequently Asked Questions about how-might-we

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write good How Might We statements?▼

Start with a raw customer friction point stripped of any solution bias, then apply reframing lenses like amplifying the good or questioning assumptions. Test each statement with the Goldilocks calibration: remove UI elements if too narrow, add persona context if too broad.

How to reframe customer complaints into design sprint questions?▼

Convert each complaint into an outcome-focused challenge by removing presupposed solutions, then generate HMW variants across the 10 IDEO lenses such as exploring the opposite or breaking the problem into micro-steps. Select the top candidates by actionability and generative potential.

What is the difference between How Might We and a design sprint?▼

HMW reframing is a single ideation technique that converts problems into opportunity questions, while a design sprint is a full multi-day facilitated process. Use HMW generation as pre-sprint preparation, and route full sprint orchestration to a dedicated design sprint skill.

Why are my How Might We statements too narrow or too broad?▼

Statements are too narrow when they mention UI elements, buttons, or features, and too broad when they could apply to any company. Fix narrow ones by reframing around the user outcome, and anchor broad ones with a specific persona and emotional friction point.

When should I not use How Might We reframing?▼

Avoid HMW reframing when you need formal PRDs, BDD user stories, multi-quarter opportunity solution trees, or full sprint facilitation. It is specifically a divergent ideation tool, not a specification or planning method.