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 |  Architecture arc42 |  Decision Making Argument Mapping |  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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | Low | Low | Medium | High |
Timedifferent | 20–45 min | 1-2 Tage | 1-3 h | 1-4 h |
Participantsdifferent | Small cross-functional group | 1-4 | 1-8 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Architecture Document, Context View, Runtime View, Deployment View | Argument Map, Evidence Gaps, Decision Rationale | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | RiskDecisionFailurePlanning | ArchitectureDocumentationCommunication | SensemakingDecisionRationale | RiskDecisionSensemaking |