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
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Paper illustration for Flywheel.
Growth
Flywheel
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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 model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.
Complexitysame
MediumMediumMediumMedium
Timedifferent
Multiple workshops over several weeks1-3 h60-120 min1-3 h
Participantsdifferent
2-83-103-82-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Hooked loop, Trigger map, Reward design, Ethics checkDomain Context Map, Boundary Notes, Ownership MapFlywheel Map, Friction Points, Growth Levers, Experiment BacklogContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
GrowthBehaviorRetention
Domain-Driven DesignContextBoundaries
GrowthRetentionConversion
Domain-Driven DesignBoundariesStrategy
Add more methods