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
Paper illustration for Ideal Days.
Agile
Ideal Days
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 effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats.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
MediumLowLowMedium
Timedifferent
Multiple workshops over several weeks30 min Setup, dann laufend15-60 min1-4 Wochen
Participantsdifferent
2-81-3 maintaining, briefing for everyone2-95-20
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncAsync
Outputdifferent
Hooked loop, Trigger map, Reward design, Ethics checkRAID Log, Status Report SourceIdeal Day Estimates, Assumption Notes, Capacity CaveatsDiary Entries, Longitudinal Patterns, Experience Timeline
Tagsno overlap
GrowthBehaviorRetention
RiskTrackingStakeholdersGovernance
EstimationEffortAgile
UX researchTrackingBehavior
Add more methods