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 Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration for Flywheel.
Growth
Flywheel
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration of Hooked Model with its method-specific working model.
Growth
Hooked Model
Purposedifferent
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.Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth.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.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.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
2-6 h60-120 min1-4 WochenMultiple workshops over several weeks
Participantsdifferent
2-83-81-62-8
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsFlywheel Map, Friction Points, Growth Levers, Experiment BacklogExperiment results, Decision log, Learning summaryHooked loop, Trigger map, Reward design, Ethics check
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
GrowthRetentionConversion
ExperimentsGrowthAnalyticsValidation
GrowthBehaviorRetention
Add more methods