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 Architecture Decision Record |  Decision Making Assumption Surfacing |  Architecture arc42 |
|---|---|---|---|---|
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. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 15-45 min | 45-90 min | 1-2 Tage |
Participantsdifferent | 3-8 | 1-3 | 2-8 | 1-4 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | ADR File, Decision Log, Rationale | Assumption List, Critical Assumptions, Learning Plan | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | FailureResilienceRisk | ArchitectureRationaleDocumentationGovernance | AssumptionsRiskDecisionDiscovery | ArchitectureDocumentationCommunication |