View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Fishbone DiagramSoftware Architecture CanvasArchitecture Communication CanvasFailure Mode and Effects Analysis
| Criterion |  Operations Fishbone Diagram |  Architecture Software Architecture Canvas |  Architecture Architecture Communication Canvas |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitydifferent | Low | Low | Medium | High |
Timedifferent | 30-60 min | 1-2 h | 60-120 min | 2-6 h |
Participantsdifferent | 2-8 | 3-10 | 2-8 | 3-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Fishbone Diagram, Cause Categories, Investigation Backlog | Architecture Canvas, Goals, Constraints, Quality Attributes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | Root causeQualityOperations | CanvasArchitectureAlignmentWorkshop | ArchitectureCommunicationStakeholdersCanvas | RiskQualityOperationsRoot cause |