View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Decision Making Constraint Analysis | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Product Discovery MVP Test Matrix |
|---|---|---|---|
Purposedifferent | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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 several minimal variants compete to answer the same question, it makes comparing and choosing between them cleaner. It separates problem, assumption, solution, and evidence. The result is captured as a Test Matrix and a Test Plan. |
Complexitydifferent | Low | High | Medium |
Timedifferent | 30-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 45-75 min |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Test Matrix, Test Plan |
Tagsno overlap | ConstraintsDecisionPlanningOptions | ArchitectureQualityRiskTradeoffsStakeholders | ExperimentsValidationDiscoveryOptions |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






