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 Reverse Brainstorming |  Innovation Lotus Blossom |
|---|---|---|---|---|
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. | 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. | When a central question feels too large, the method breaks it into neighboring topic fields with their own depth of ideation. It holds structure and openness at the same time, so adjacent perspectives don't get lost. This grows an idea space out of a core problem. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30–45 min | 1-3 h | 30-60 min | 45-90 min |
Participantsdifferent | 1-10 | 2-8 | 3-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Context Map, Integration Patterns, Boundary Notes | Reverse Ideas, Risk Themes, Solution Ideas | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | FramingOpportunityIdeationQuestions | Domain-Driven DesignBoundariesStrategy | BrainstormingIdeationCreativityRisk | BrainstormingIdeationCreativityDivergenceWorkshop |