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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
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
In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.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
LowMediumLowMedium
Timedifferent
20–45 min1-3 Wochen vom Draft bis zur Entscheidung30-60 min45-90 min
Participantsdifferent
Small cross-functional group3-20 Reviewer2-103-12
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Risk list, Mitigation plan, Assumption logRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsDACI Matrix, Decision Owner, Decision LogRAPID Role Map, Recommendation, Decision Log
Tags1 shared
RiskDecisionFailurePlanning
ArchitectureDecisionAsyncGovernance
DecisionRolesGovernanceAlignment
DecisionRolesGovernance
Add more methods