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 |  Knowledge Modeling Event Modeling |  Domain Modeling EventStorming |
|---|---|---|---|
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. | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | 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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 30–45 min | 2-6 h | 2-8 h |
Participantsdifferent | 1-10 | 2-8 | 5-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Event Model, UI Flow, Commands, Read Models | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | FramingOpportunityIdeationQuestions | EventsBlueprintDomain-Driven DesignBehavior | Domain-Driven DesignEventsDiscoveryWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
