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
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration for RAPID
Decision Making
RAPID
Paper illustration for DACI
Decision Making
DACI
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.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.In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung30-90 min45-90 min30-60 min
Participantsdifferent
3-20 Reviewer1-63-122-10
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsDecision Tree, Option Map, Assumption ListRAPID Role Map, Recommendation, Decision LogDACI Matrix, Decision Owner, Decision Log
Tags1 shared
ArchitectureDecisionAsyncGovernance
DecisionTreeOptions
DecisionRolesGovernance
DecisionRolesGovernanceAlignment
Add more methods