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 |  Operations Fishbone Diagram |
|---|---|---|---|
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. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-3 h | 60-120 min | 30-60 min |
Participantsdifferent | 3-8 | 2-8 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | FailureResilienceRisk | ArchitectureCommunicationStakeholdersCanvas | Root causeQualityOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
