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 for DACI
Decision Making
DACI
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
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
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.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.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
30-60 min1-2 h1-3 Wochen vom Draft bis zur Entscheidung45-90 min
Participantsdifferent
2-103-103-20 Reviewer3-12
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop + async
Outputdifferent
DACI Matrix, Decision Owner, Decision LogArchitecture Canvas, Goals, Constraints, Quality AttributesRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsRAPID Role Map, Recommendation, Decision Log
Tagsno overlap
DecisionRolesGovernanceAlignment
CanvasArchitectureAlignmentWorkshop
ArchitectureDecisionAsyncGovernance
DecisionRolesGovernance
Add more methods