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
Paper illustration for DACI
Decision Making
DACI
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Paper illustration for RAPID
Decision Making
RAPID
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.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 Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.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
MediumLowLowMedium
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung30-60 min1-2 h45-90 min
Participantsdifferent
3-20 Reviewer2-103-83-12
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsDACI Matrix, Decision Owner, Decision LogInception Canvas, Risks, Goal List, Open QuestionsRAPID Role Map, Recommendation, Decision Log
Tagsno overlap
ArchitectureDecisionAsyncGovernance
DecisionRolesGovernanceAlignment
AlignmentArchitectureCanvas
DecisionRolesGovernance
Add more methods