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 Funnel Analysis |  Operations Fishbone Diagram |  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. | 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 a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | 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 | Low | High |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 h | 30-60 min | 1-4 Wochen |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 1-5 | 2-8 | 1-6 |
Formatdifferent | Workshop + async | Async | Workshop | 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 | Funnel report, Drop-off analysis, Optimization hypotheses | Fishbone Diagram, Cause Categories, Investigation Backlog | Experiment results, Decision log, Learning summary |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | AnalyticsConversionGrowth | Root causeQualityOperations | ExperimentsGrowthAnalyticsValidation |