View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Assumption SurfacingDecision Rights MappingATAM (Architecture Tradeoff Analysis Method)Request for Comments
| Criterion | ![]() Decision Making Assumption Surfacing | ![]() Decision Making Decision Rights Mapping | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | 45-90 min | 90-180 min | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 2-8 | 4-12 | Evaluation team, architects, and relevant stakeholders | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | Assumption List, Critical Assumptions, Learning Plan | Decision Rights Matrix, Agreement | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | AssumptionsRiskDecisionDiscovery | DecisionGovernanceAlignmentResponsibility | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureDecisionAsyncGovernance |



