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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of Hooked Model with its method-specific working model.
Growth
Hooked Model
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
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.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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.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.
Complexitydifferent
LowMediumLowHigh
Timedifferent
30 min Setup, dann laufendMultiple workshops over several weeks1-5 Tage1-4 Wochen
Participantsdifferent
1-3 maintaining, briefing for everyone2-8Nutzertraffic1-6
Formatdifferent
AsyncWorkshop + asyncAsyncAsync
Outputdifferent
RAID Log, Status Report SourceHooked loop, Trigger map, Reward design, Ethics checkInterest Metrics, Conversion Signal, Learning NoteExperiment results, Decision log, Learning summary
Tagsno overlap
RiskTrackingStakeholdersGovernance
GrowthBehaviorRetention
ValidationExperimentsDemandGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods