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 for Diary Study.
UX Research
Diary Study
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
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 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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.
Complexitydifferent
MediumMediumHighHigh
Timedifferent
Multiple workshops over several weeks1-4 Wochen2-6 h2-6 h
Participantsdifferent
2-85-203-103-8
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Hooked loop, Trigger map, Reward design, Ethics checkDiary Entries, Longitudinal Patterns, Experience TimelineFMEA Table, Risk Priority, Mitigation ActionsFault Tree, Critical Paths, Cause Hypotheses, Control Actions
Tagsno overlap
GrowthBehaviorRetention
UX researchTrackingBehavior
RiskQualityOperationsRoot cause
RiskRoot causeSafety
Add more methods