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 |  Delivery RAID Log |  Architecture Views and Beyond |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | 1-3 Tage | 60-120 min |
Participantsdifferent | 3-8 | 1-3 maintaining, briefing for everyone | 1-4 | 2-8 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | RAID Log, Status Report Source | Architecture Views, Cross-view Notes, Rationale | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | FailureResilienceRisk | RiskTrackingStakeholdersGovernance | DocumentationStakeholdersArchitecture | ArchitectureCommunicationStakeholdersCanvas |