View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)Hooked ModelLASR (Lightweight Approach for Software Reviews)Flywheel
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Growth Hooked Model |  Architecture LASR (Lightweight Approach for Software Reviews) |  Growth Flywheel |
|---|---|---|---|---|
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. | 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. | Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth. |
Complexitydifferent | High | Medium | Medium | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | Multiple workshops over several weeks | 3–4 h for initial assessment; preparation and deeper analysis additional | 60-120 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 2-8 | 1 or a small team; particularly suitable for 3–4 people | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
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 | 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 | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | GrowthBehaviorRetention | ArchitectureQualityRiskAssessmentLean | GrowthRetentionConversion |