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 of a four-quadrant grid with tasks sorted by importance and urgency and translated into actions.
Decision Making
Eisenhower Matrix
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.It separates true priorities from noise so it becomes clear what should be done now, scheduled, delegated, or dropped.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
MediumLowMediumLow
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung15-30 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 ticketsEisenhower Matrix, Action List, Delegation NotesRAPID Role Map, Recommendation, Decision LogDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
ArchitectureDecisionAsyncGovernance
PrioritizationFocusTasks
DecisionRolesGovernance
DecisionRolesGovernanceAlignment
Add more methods