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 Communication Canvas |  Delivery RAID Log |
|---|---|---|---|
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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-3 h | 60-120 min | 30 min Setup, dann laufend |
Participantsdifferent | 3-8 | 2-8 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop | Workshop + async | Async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | RAID Log, Status Report Source |
Tagsno overlap | FailureResilienceRisk | ArchitectureCommunicationStakeholdersCanvas | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
