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 for Argument Mapping
Decision Making
Argument Mapping
Paper illustration for RAPID
Decision Making
RAPID
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.
Complexitydifferent
LowMediumMediumLow
Timedifferent
20–45 min1-3 h45-90 min15-45 min
Participantsdifferent
Small cross-functional group1-83-121-3
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Risk list, Mitigation plan, Assumption logArgument Map, Evidence Gaps, Decision RationaleRAPID Role Map, Recommendation, Decision LogADR File, Decision Log, Rationale
Tagsno overlap
RiskDecisionFailurePlanning
SensemakingDecisionRationale
DecisionRolesGovernance
ArchitectureRationaleDocumentationGovernance
Add more methods