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 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
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
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 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.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.
Complexitydifferent
LowLowMediumHigh
Timedifferent
20–45 min15-45 min1-3 h1-4 h
Participantsdifferent
Small cross-functional group1-31-83-8
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop
Outputdifferent
Risk list, Mitigation plan, Assumption logADR File, Decision Log, RationaleArgument Map, Evidence Gaps, Decision RationaleChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
RiskDecisionFailurePlanning
ArchitectureRationaleDocumentationGovernance
SensemakingDecisionRationale
RiskDecisionSensemaking
Add more methods