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 Scatter Diagram |  Operations Fault Tree Analysis |  Architecture Architecture Communication Canvas |  Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to 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. | 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. |
Complexitydifferent | Low | High | Medium | Low |
Timedifferent | 30-90 min | 2-6 h | 60-120 min | 1-4 h |
Participantsdifferent | 1-4 | 3-8 | 2-8 | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Scatter Plot, Korrelationsnotiz, Hypothesenliste | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | Root causeQualityVisualization | RiskRoot causeSafety | ArchitectureCommunicationStakeholdersCanvas | ArchitectureCommunicationVisualization |