View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Failure Scenario Analysis |  Decision Making Argument Mapping |  Architecture arc42 |  Decision Making Red Teaming |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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 | Medium | Medium | Low | High |
Timedifferent | 1-3 h | 1-3 h | 1-2 Tage | 1-4 h |
Participantsdifferent | 3-8 | 1-8 | 1-4 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Argument Map, Evidence Gaps, Decision Rationale | Architecture Document, Context View, Runtime View, Deployment View | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | FailureResilienceRisk | SensemakingDecisionRationale | ArchitectureDocumentationCommunication | RiskDecisionSensemaking |