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
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
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.For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.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.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.
Complexitydifferent
LowHighLowMedium
Timedifferent
20–45 min1-4 h15-45 min1-3 h
Participantsdifferent
Small cross-functional group3-81-31-8
Formatdifferent
WorkshopWorkshopAsyncWorkshop + async
Outputdifferent
Risk list, Mitigation plan, Assumption logChallenge Findings, Risk Register, Mitigation PlanADR File, Decision Log, RationaleArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
RiskDecisionFailurePlanning
RiskDecisionSensemaking
ArchitectureRationaleDocumentationGovernance
SensemakingDecisionRationale
Add more methods