methodatlas
Compare

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 Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration for RAPID
Decision Making
RAPID
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration of Decision Rights Mapping with its method-specific working model.
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
MediumMediumMediumMedium
Timedifferent
30-90 min45-90 min1-3 Wochen vom Draft bis zur Entscheidung90-180 min
Participantsdifferent
1-63-123-20 Reviewer4-12
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop
Outputdifferent
Decision Tree, Option Map, Assumption ListRAPID Role Map, Recommendation, Decision LogRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsDecision Rights Matrix, Agreement
Tags1 shared
DecisionTreeOptions
DecisionRolesGovernance
ArchitectureDecisionAsyncGovernance
DecisionGovernanceAlignmentResponsibility
Add more methods