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 Decision Tree | ![]() Decision Making RAPID | ![]() Architecture Request for Comments | ![]() Decision Making Decision Rights Mapping |
|---|---|---|---|---|
Purposedifferent | For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 30-90 min | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min |
Participantsdifferent | 1-6 | 3-12 | 3-20 Reviewer | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Decision Tree, Option Map, Assumption List | RAPID Role Map, Recommendation, Decision Log | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Decision Rights Matrix, Agreement |
Tags1 shared | DecisionTreeOptions | DecisionRolesGovernance | ArchitectureDecisionAsyncGovernance | DecisionGovernanceAlignmentResponsibility |



