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 ModelATAM (Architecture Tradeoff Analysis Method)Diary StudyLASR (Lightweight Approach for Software Reviews)
| Criterion |  Growth Hooked Model |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  UX Research Diary Study |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
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. | 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. | 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. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | Multiple workshops over several weeks | Several meetings plus preparation and analysis; total effort depends on scope | 1-4 Wochen | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 5-20 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Hooked loop, Trigger map, Reward design, Ethics check | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Diary Entries, Longitudinal Patterns, Experience Timeline | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks |
Tagsno overlap | GrowthBehaviorRetention | ArchitectureQualityRiskTradeoffsStakeholders | UX researchTrackingBehavior | ArchitectureQualityRiskAssessmentLean |