View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Growth Hooked Model | ![]() Domain Modeling EventStorming | ![]() Innovation Starbursting | ![]() Knowledge Modeling Event Modeling |
|---|---|---|---|---|
Purposedifferent | The Hooked Model helps clarify engagement loops, user behavior, and experiments. It makes repeat behavior measurable and captures the result as a hooked loop, trigger map, and reward design. | 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. | Helps clarify ideas, open questions, and testable next steps in concrete terms. It opens the thinking space, collects ideas, and leads to testable options. The result is captured as a star-shaped question map, question list, and assumption list. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | Multiple workshops over several weeks | 2-8 h | 30-60 min | 2-6 h |
Participantsdifferent | 2-8 | 5-12 | 3-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Hooked loop, Trigger map, Reward design, Ethics check | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Star-Shaped Question Map, Question List, Assumption List | Event Model, UI Flow, Commands, Read Models |
Tagsno overlap | GrowthBehaviorRetention | Domain-Driven DesignEventsDiscoveryWorkshop | BrainstormingIdeationWorkshopDiscovery | EventsBlueprintDomain-Driven DesignBehavior |



