View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Assumption Mapping |  Delivery RAID Log |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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. | 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. |
Complexitydifferent | Medium | Low | High | High |
Timedifferent | 45-60 min | 30 min Setup, dann laufend | Several meetings plus preparation and analysis; total effort depends on scope | 1-4 Wochen |
Participantsdifferent | 2-8 | 1-3 maintaining, briefing for everyone | Evaluation team, architects, and relevant stakeholders | 1-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Assumption map, Test backlog, Risk ranking | RAID Log, Status Report Source | 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 |
Tagsno overlap | AssumptionsRiskExperimentsValidation | RiskTrackingStakeholdersGovernance | ArchitectureQualityRiskTradeoffsStakeholders | ExperimentsGrowthAnalyticsValidation |