View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Growth Funnel Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Growth A/B Testing |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | High | High | Medium |
Timedifferent | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 1-4 Wochen | 45-60 min |
Participantsdifferent | 1-5 | Evaluation team, architects, and relevant stakeholders | 1-6 | 2-8 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | Funnel report, Drop-off analysis, Optimization hypotheses | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Experiment results, Decision log, Learning summary | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | AnalyticsConversionGrowth | ArchitectureQualityRiskTradeoffsStakeholders | ExperimentsGrowthAnalyticsValidation | AssumptionsRiskExperimentsValidation |