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 for Diary Study.
UX Research
Diary Study
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 experiences build up over days or weeks and a single session cannot capture them, Diary Study records the course of everyday life. Recurring triggers, moods, and habits become visible this way, beyond the sharpness of memory.
Complexitydifferent
MediumLowHighMedium
Timedifferent
Multiple workshops over several weeks30 min Setup, dann laufend1-4 Wochen1-4 Wochen
Participantsdifferent
2-81-3 maintaining, briefing for everyone1-65-20
Formatdifferent
Workshop + asyncAsyncAsyncAsync
Outputdifferent
Hooked loop, Trigger map, Reward design, Ethics checkRAID Log, Status Report SourceExperiment results, Decision log, Learning summaryDiary Entries, Longitudinal Patterns, Experience Timeline
Tagsno overlap
GrowthBehaviorRetention
RiskTrackingStakeholdersGovernance
ExperimentsGrowthAnalyticsValidation
UX researchTrackingBehavior
Add more methods