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) |  Product Discovery Smoke Test |  Architecture Risk Storming |
|---|---|---|---|---|
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. | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Medium | High | Low | Low |
Timedifferent | 45-60 min | Several meetings plus preparation and analysis; total effort depends on scope | 1-5 Tage | 60-90 min |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | Nutzertraffic | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
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 | Interest Metrics, Conversion Signal, Learning Note | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | AssumptionsRiskExperimentsValidation | ArchitectureQualityRiskTradeoffsStakeholders | ValidationExperimentsDemandGrowth | RiskArchitectureWorkshopValidation |