View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Decision Making Pre-Mortem | ![]() Engineering Failure Scenario Analysis | ![]() Architecture Architecture Decision Record | ![]() 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. | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | 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 | Low | Medium | Low | Medium |
Timedifferent | 20–45 min | 1-3 h | 15-45 min | 1-3 h |
Participantsdifferent | Small cross-functional group | 3-8 | 1-3 | 1-8 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | ADR File, Decision Log, Rationale | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | RiskDecisionFailurePlanning | FailureResilienceRisk | ArchitectureRationaleDocumentationGovernance | SensemakingDecisionRationale |



