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 for Flywheel.
Growth
Flywheel
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
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
Purposedifferent
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 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.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
60-120 min1-3 h2-6 hMultiple workshops over several weeks
Participantsdifferent
3-83-82-82-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Flywheel Map, Friction Points, Growth Levers, Experiment BacklogContext Canvas, Glossary, Integration NotesEvent Model, UI Flow, Commands, Read ModelsHooked loop, Trigger map, Reward design, Ethics check
Tagsno overlap
GrowthRetentionConversion
Domain-Driven DesignBoundariesModeling
EventsBlueprintDomain-Driven DesignBehavior
GrowthBehaviorRetention
Add more methods