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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration for DACI
Decision Making
DACI
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for RAPID
Decision Making
RAPID
Purposedifferent
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.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.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.
Complexitydifferent
LowLowMediumMedium
Timedifferent
20-60 min30-60 min1-3 Wochen vom Draft bis zur Entscheidung45-90 min
Participantsdifferent
1-42-103-20 Reviewer3-12
Formatdifferent
AsyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathDACI Matrix, Decision Owner, Decision LogRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsRAPID Role Map, Recommendation, Decision Log
Tagsno overlap
OperationsReliabilityDocumentation
DecisionRolesGovernanceAlignment
ArchitectureDecisionAsyncGovernance
DecisionRolesGovernance
Add more methods