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 Mode and Effects AnalysisArchitecture Communication CanvasSoftware Architecture CanvasFishbone Diagram
| Criterion |  Operations Failure Mode and Effects Analysis |  Architecture Architecture Communication Canvas |  Architecture Software Architecture Canvas |  Operations Fishbone Diagram |
|---|---|---|---|---|
Purposedifferent | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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 | High | Medium | Low | Low |
Timedifferent | 2-6 h | 60-120 min | 1-2 h | 30-60 min |
Participantsdifferent | 3-10 | 2-8 | 3-10 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | FMEA Table, Risk Priority, Mitigation Actions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Canvas, Goals, Constraints, Quality Attributes | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | RiskQualityOperationsRoot cause | ArchitectureCommunicationStakeholdersCanvas | CanvasArchitectureAlignmentWorkshop | Root causeQualityOperations |