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 Assumption Surfacing | ![]() Decision Making Decision Matrix | ![]() Architecture Request for Comments | ![]() 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. | When several options collide with several criteria, comparison quickly becomes subjective. A Decision Matrix makes the trade-off visible and brings weighting, criteria, and options into a shared logic. | 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. | 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 | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 15-45 min |
Participantsdifferent | 2-8 | 2-8 | 3-20 Reviewer | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Async | Async |
Outputdifferent | Assumption List, Critical Assumptions, Learning Plan | Decision Matrix, Scoring Rationale, Selected Option | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | ADR File, Decision Log, Rationale |
Tagsno overlap | AssumptionsRiskDecisionDiscovery | DecisionCriteriaScoringTradeoffs | ArchitectureDecisionAsyncGovernance | ArchitectureRationaleDocumentationGovernance |



