View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Growth Hooked Model | ![]() UX Research Diary Study | ![]() Operations Fault Tree Analysis | ![]() Operations MORT 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 critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. |
Complexitydifferent | Medium | Medium | High | High |
Timedifferent | Multiple workshops over several weeks | 1-4 Wochen | 2-6 h | Mehrere Tage bis Wochen |
Participantsdifferent | 2-8 | 5-20 | 3-8 | 2-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Hooked loop, Trigger map, Reward design, Ethics check | Diary Entries, Longitudinal Patterns, Experience Timeline | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | GrowthBehaviorRetention | UX researchTrackingBehavior | RiskRoot causeSafety | Root causeSafetySystemicIncident |



