View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)Hypothesis Prioritization CanvasProblem Framing Workshop
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Product Discovery Hypothesis Prioritization Canvas |  Facilitation Problem Framing Workshop |
|---|---|---|---|
Purposedifferent | 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 many hypotheses compete for attention, it brings order to their learning sequence and importance. It separates problem, assumption, solution, and evidence. The result is captured as a prioritization canvas and a hypothesis backlog. | When a team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other. |
Complexitydifferent | High | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 60-90 min | 60-120 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-8 | 4-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Prioritization Canvas, Hypothesis Backlog | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | ExperimentsPrioritizationDiscoveryHypothesis | FacilitationAlignmentDiscovery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
