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 |  Architecture arc42 |  Decision Making Red Teaming |  Decision Making Pre-Mortem |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 1-3 h | 1-2 Tage | 1-4 h | 20–45 min |
Participantsdifferent | 3-8 | 1-4 | 3-8 | Small cross-functional group |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Architecture Document, Context View, Runtime View, Deployment View | Challenge Findings, Risk Register, Mitigation Plan | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | FailureResilienceRisk | ArchitectureDocumentationCommunication | RiskDecisionSensemaking | RiskDecisionFailurePlanning |