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 A/B Testing |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Delivery RAID Log |  Product Discovery Smoke Test |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. |
Complexitydifferent | High | High | Low | Low |
Timedifferent | 1-4 Wochen | Several meetings plus preparation and analysis; total effort depends on scope | 30 min Setup, dann laufend | 1-5 Tage |
Participantsdifferent | 1-6 | Evaluation team, architects, and relevant stakeholders | 1-3 maintaining, briefing for everyone | Nutzertraffic |
Formatdifferent | Async | Workshop + async | Async | Async |
Outputdifferent | Experiment results, Decision log, Learning summary | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | RAID Log, Status Report Source | Interest Metrics, Conversion Signal, Learning Note |
Tagsno overlap | ExperimentsGrowthAnalyticsValidation | ArchitectureQualityRiskTradeoffsStakeholders | RiskTrackingStakeholdersGovernance | ValidationExperimentsDemandGrowth |