View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Growth Hooked Model | ![]() UX Research Diary Study |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | High | Medium | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | Multiple workshops over several weeks | 1-4 Wochen |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 2-8 | 5-20 |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Hooked loop, Trigger map, Reward design, Ethics check | Diary Entries, Longitudinal Patterns, Experience Timeline |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | GrowthBehaviorRetention | UX researchTrackingBehavior |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






