Not the constraint itself determines the search, but its reframing as an open question. Grammatical inversion turns deterministic limits into solution-agnostic inquiry, while systemic expansion operators widen the search space, supporting product-capability discovery in regulated settings and analysis of trade-offs between delivery speed and fault tolerance.
Based on: Basadur / Design Sprint
How Might We (HMW) is a cognitive reframing framework designed to convert intractable functional deadlocks into generative exploration vectors. Originally pioneered by Min Basadur at Procter & Gamble in the 1970s and subsequently formalized by IDEO and Google Design Sprints, the technique leverages grammatical syntax to dissolve institutional fixation. Stating that "users abandon the onboarding flow due to burdensome identity verification" reinforces helplessness. Recasting the friction as "How might we..." repositions the constraint as an architectural surface for novel capability design.
Each term within the construct serves an intentional cognitive function: "How" assumes solvability. "Might" eliminates the pressure of immediate operational viability, granting permission to explore unorthodox hypotheses. "We" establishes shared agency and interdisciplinary ownership.
The framework functions as an algorithmic transformation pipeline:
1. Friction Isolation: Identify six concrete, verified systemic constraints or user frictions across the target domain.
2. Interrogative Inversion: Convert each obstacle into a solution-agnostic inquiry vector introduced by "How might we." The framing must neither dictate a specific feature nor dissipate into vague generalities.
3. Operator-Driven Variation (Amplify & Invert): Subject each baseline question to dual divergent operators:
4. Leverage Filtering: Rank and select the top three questions based on structural leverage (Potential Impact vs. Technical Feasibility).
In human ideation settings, HMW exercises routinely degenerate into trivial, risk-averse inquiries. Workshop participants unconsciously bake their preferred implementations into the question, masquerading existing roadmap items as fresh explorations.
The Brainstorm Reactor executes syntactic transformations with zero cognitive bias. The engine strictly rejects embedded solutions and enforces rigorous structural orthogonality across both Amplify and Invert vectors. By algorithmically scaling divergent framing options, it uncovers non-obvious solution corridors that cross-functional teams fail to identify.
HMW is exclusively a divergent problem-framing tool. It does not output deterministic engineering specifications or validation proofs. Deploying HMW questions downstream during operational execution risks severe scope instability and derailed sprint momentum.
Furthermore, grammatical reframing can foster naive optimism. Linguistic restructuring cannot bypass hard physical limitations or non-negotiable legal compliance mandates. When fundamental computational or capital boundaries are reached, algebraic modeling must supersede divergent phrasing.
Start from physical invariants. Separating irreducible physical constraints from inherited industry conventions enables bottom-up architectural synthesis grounded in measurable limits rather than historical precedent. Stress-test feasibility and cost before committing capital to research.
Fixing a visible failure is not the same as resolving its cause: Five Whys traces the causal chain beneath the symptom. As each answer becomes the next question’s premise, it exposes systemic origins and lets Brainstorm Reactor drive preventive action with measurable indicators.
Turn user needs into intervention points. UX research grounds the method, linking requirements to friction points and classifying causes across technical, process, and ergonomic levers. Prioritise verified fixes in procurement flows and complex software.
Symptom-level fixes seem direct, yet the real leverage lies in testing product, planning, potential and human dimensions. Because Michael Morgan’s four-perspective matrix exposes assumptions across these frames, it yields sharper problem formulations for Brainstorm Reactor to convert into strategic decisions, cross-functional alignment and risk review.
Select this method, describe your challenge, and let the structured AI pipeline do the rest.
Open Now