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/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
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 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 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.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
Multiple workshops over several weeks1-4 Wochen1-3 h45-60 min
Participantsdifferent
2-81-63-102-8
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Hooked loop, Trigger map, Reward design, Ethics checkExperiment results, Decision log, Learning summaryDomain Context Map, Boundary Notes, Ownership MapAssumption map, Test backlog, Risk ranking
Tagsno overlap
GrowthBehaviorRetention
ExperimentsGrowthAnalyticsValidation
Domain-Driven DesignContextBoundaries
AssumptionsRiskExperimentsValidation
Add more methods