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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
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 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 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.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.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
Multiple workshops over several weeks1-3 h1-4 Wochen1-3 h
Participantsdifferent
2-82-81-63-8
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Hooked loop, Trigger map, Reward design, Ethics checkContext Map, Integration Patterns, Boundary NotesExperiment results, Decision log, Learning summaryContext Canvas, Glossary, Integration Notes
Tagsno overlap
GrowthBehaviorRetention
Domain-Driven DesignBoundariesStrategy
ExperimentsGrowthAnalyticsValidation
Domain-Driven DesignBoundariesModeling
Add more methods