View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Failure Scenario AnalysisRAID LogArchitecture Communication CanvasArchitecture Decision Record
| Criterion |  Engineering Failure Scenario Analysis |  Delivery RAID Log |  Architecture Architecture Communication Canvas |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | 60-120 min | 15-45 min |
Participantsdifferent | 3-8 | 1-3 maintaining, briefing for everyone | 2-8 | 1-3 |
Formatdifferent | Workshop | Async | Workshop + async | Async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | RAID Log, Status Report Source | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | ADR File, Decision Log, Rationale |
Tagsno overlap | FailureResilienceRisk | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationStakeholdersCanvas | ArchitectureRationaleDocumentationGovernance |