methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration of Hooked Model with its method-specific working model.
Growth
Hooked Model
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected.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.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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.
Complexitydifferent
LowMediumMediumHigh
Timedifferent
1-2 h2-6 hMultiple workshops over several weeks1-4 Wochen
Participantsdifferent
2-82-82-81-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeEvent Model, UI Flow, Commands, Read ModelsHooked loop, Trigger map, Reward design, Ethics checkExperiment results, Decision log, Learning summary
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
EventsBlueprintDomain-Driven DesignBehavior
GrowthBehaviorRetention
ExperimentsGrowthAnalyticsValidation
Add more methods