View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Fishbone Diagram |  Architecture Architecture Communication Canvas |  Architecture C4 Model |  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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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 | Medium | Low | High |
Timedifferent | 30-60 min | 60-120 min | 1-4 h | 2-6 h |
Participantsdifferent | 2-8 | 2-8 | 1-5 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Fishbone Diagram, Cause Categories, Investigation Backlog | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Context Diagram, Container Diagram, Component Diagram | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | Root causeQualityOperations | ArchitectureCommunicationStakeholdersCanvas | ArchitectureCommunicationVisualization | RiskQualityOperationsRoot cause |