View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Failure Scenario Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Product Discovery Smoke Test |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | 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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | 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 | Medium | High | Low | High |
Timedifferent | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 1-5 Tage | 1-4 Wochen |
Participantsdifferent | 3-8 | Evaluation team, architects, and relevant stakeholders | Nutzertraffic | 1-6 |
Formatdifferent | Workshop | Workshop + async | Async | Async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Interest Metrics, Conversion Signal, Learning Note | Experiment results, Decision log, Learning summary |
Tagsno overlap | FailureResilienceRisk | ArchitectureQualityRiskTradeoffsStakeholders | ValidationExperimentsDemandGrowth | ExperimentsGrowthAnalyticsValidation |