View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Request for Comments |  Decision Making RAPID |  Decision Making Assumption Surfacing |  Decision Making Decision Rights Mapping |
|---|---|---|---|---|
Purposedifferent | 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 complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | 45-90 min | 90-180 min |
Participantsdifferent | 3-20 Reviewer | 3-12 | 2-8 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | RAPID Role Map, Recommendation, Decision Log | Assumption List, Critical Assumptions, Learning Plan | Decision Rights Matrix, Agreement |
Tags1 shared | ArchitectureDecisionAsyncGovernance | DecisionRolesGovernance | AssumptionsRiskDecisionDiscovery | DecisionGovernanceAlignmentResponsibility |