View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Hooked ModelDiary StudyATAM (Architecture Tradeoff Analysis Method)Failure Mode and Effects Analysis
| Criterion |  Growth Hooked Model |  UX Research Diary Study |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Failure Mode and Effects 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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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. |
Complexitydifferent | Medium | Medium | High | High |
Timedifferent | Multiple workshops over several weeks | 1-4 Wochen | Several meetings plus preparation and analysis; total effort depends on scope | 2-6 h |
Participantsdifferent | 2-8 | 5-20 | Evaluation team, architects, and relevant stakeholders | 3-10 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Hooked loop, Trigger map, Reward design, Ethics check | Diary Entries, Longitudinal Patterns, Experience Timeline | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | GrowthBehaviorRetention | UX researchTrackingBehavior | ArchitectureQualityRiskTradeoffsStakeholders | RiskQualityOperationsRoot cause |