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 of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
MediumLowHighMedium
Timedifferent
Multiple workshops over several weeks30 min Setup, dann laufend1-4 Wochen45-60 min
Participantsdifferent
2-81-3 maintaining, briefing for everyone1-62-8
Formatdifferent
Workshop + asyncAsyncAsyncWorkshop + async
Outputdifferent
Hooked loop, Trigger map, Reward design, Ethics checkRAID Log, Status Report SourceExperiment results, Decision log, Learning summaryAssumption map, Test backlog, Risk ranking
Tagsno overlap
GrowthBehaviorRetention
RiskTrackingStakeholdersGovernance
ExperimentsGrowthAnalyticsValidation
AssumptionsRiskExperimentsValidation
Add more methods