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
Paper illustration of Hooked Model with its method-specific working model.
Growth
Hooked Model
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
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.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 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.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
60-120 minMultiple workshops over several weeks1-3 h1-3 h
Participantsdifferent
3-82-82-83-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Flywheel Map, Friction Points, Growth Levers, Experiment BacklogHooked loop, Trigger map, Reward design, Ethics checkContext Map, Integration Patterns, Boundary NotesDomain Context Map, Boundary Notes, Ownership Map
Tagsno overlap
GrowthRetentionConversion
GrowthBehaviorRetention
Domain-Driven DesignBoundariesStrategy
Domain-Driven DesignContextBoundaries
Add more methods