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 EventStorming |  Domain Modeling Context Map |  Innovation 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 a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 30–45 min | 2-8 h | 1-3 h | 30-60 min |
Participantsdifferent | 1-10 | 5-12 | 2-8 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Context Map, Integration Patterns, Boundary Notes | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | FramingOpportunityIdeationQuestions | Domain-Driven DesignEventsDiscoveryWorkshop | Domain-Driven DesignBoundariesStrategy | BrainstormingIdeationCreativityWorkshopDivergence |