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) |  Decision Making Pareto Analysis |
|---|---|---|---|
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. | In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle. |
Complexitydifferent | Medium | High | Low |
Timedifferent | 45-60 min | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 1-6 |
Formatsame | 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 | Pareto Chart, Top Causes, Focus List |
Tagsno overlap | AssumptionsRiskExperimentsValidation | ArchitectureQualityRiskTradeoffsStakeholders | PrioritizationQualityFocusRoot cause |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
