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 |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Systems Thinking Evaporating Cloud |  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. | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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 | Medium | High |
Timedifferent | 45-60 min | Several meetings plus preparation and analysis; total effort depends on scope | 60-120 min | 1-4 Wochen |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 2-8 | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Assumption map, Test backlog, Risk ranking | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Experiment results, Decision log, Learning summary |
Tagsno overlap | AssumptionsRiskExperimentsValidation | ArchitectureQualityRiskTradeoffsStakeholders | Theory of ConstraintsAssumptionsSystems thinking | ExperimentsGrowthAnalyticsValidation |