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 SurfacingRequest for CommentsDecision Rights MappingArchitecture Decision Record
| Criterion |  Decision Making Assumption Surfacing |  Architecture Request for Comments |  Decision Making Decision Rights Mapping |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min | 15-45 min |
Participantsdifferent | 2-8 | 3-20 Reviewer | 4-12 | 1-3 |
Formatdifferent | Workshop + async | Async | Workshop | Async |
Outputdifferent | Assumption List, Critical Assumptions, Learning Plan | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Decision Rights Matrix, Agreement | ADR File, Decision Log, Rationale |
Tagsno overlap | AssumptionsRiskDecisionDiscovery | ArchitectureDecisionAsyncGovernance | DecisionGovernanceAlignmentResponsibility | ArchitectureRationaleDocumentationGovernance |