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
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for DACI
Decision Making
DACI
Paper illustration for RAPID
Decision Making
RAPID
Purposedifferent
For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.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 cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.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
MediumMediumLowMedium
Timedifferent
Ongoing1-3 Wochen vom Draft bis zur Entscheidung30-60 min45-90 min
Participantsdifferent
2-203-20 Reviewer2-103-12
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Chat Transcript, Action Log, AutomationsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsDACI Matrix, Decision Owner, Decision LogRAPID Role Map, Recommendation, Decision Log
Tagsno overlap
CollaborationEngineeringIncident
ArchitectureDecisionAsyncGovernance
DecisionRolesGovernanceAlignment
DecisionRolesGovernance
Add more methods