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
Paper illustration of Hooked Model with its method-specific working model.
Growth
Hooked Model
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Paper illustration for Flywheel.
Growth
Flywheel
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.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 business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
Multiple workshops over several weeks2-6 h1-3 h60-120 min
Participantsdifferent
2-82-83-83-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Hooked loop, Trigger map, Reward design, Ethics checkEvent Model, UI Flow, Commands, Read ModelsContext Canvas, Glossary, Integration NotesFlywheel Map, Friction Points, Growth Levers, Experiment Backlog
Tagsno overlap
GrowthBehaviorRetention
EventsBlueprintDomain-Driven DesignBehavior
Domain-Driven DesignBoundariesModeling
GrowthRetentionConversion
Add more methods