View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation How Might We |  Domain Modeling Context Map |  Innovation Brainstorming |  Innovation Reverse Brainstorming |
|---|---|---|---|---|
Purposedifferent | With a stuck problem carrying many implicit assumptions, the method translates observations into open, workable questions. It sharpens the problem frame without pre-thinking the solution, turning frustration or fuzziness into a search space with clear direction. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | When a team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. | For persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30–45 min | 1-3 h | 30-60 min | 30-60 min |
Participantsdifferent | 1-10 | 2-8 | 4-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Context Map, Integration Patterns, Boundary Notes | Idea pool, Theme clusters, Shortlist | Reverse Ideas, Risk Themes, Solution Ideas |
Tagsno overlap | FramingOpportunityIdeationQuestions | Domain-Driven DesignBoundariesStrategy | BrainstormingIdeationCreativityWorkshopDivergence | BrainstormingIdeationCreativityRisk |