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 |  Growth Funnel Analysis |  Growth A/B Testing |
|---|---|---|---|---|
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 many visitors or users drop off along the way, the reason behind the number often stays hidden. Funnel Analysis exposes these transitions and makes visible exactly where the path collapses. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. |
Complexitydifferent | High | Medium | Medium | High |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | Multiple workshops over several weeks | 1-3 h | 1-4 Wochen |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 2-8 | 1-5 | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | 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 | Funnel report, Drop-off analysis, Optimization hypotheses | Experiment results, Decision log, Learning summary |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | GrowthBehaviorRetention | AnalyticsConversionGrowth | ExperimentsGrowthAnalyticsValidation |