View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture C4 Model |  Architecture Architecture Decision Record |  Operations Fishbone Diagram |  Operations Scatter Diagram |
|---|---|---|---|---|
Purposedifferent | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 1-4 h | 15-45 min | 30-60 min | 30-90 min |
Participantsdifferent | 1-5 | 1-3 | 2-8 | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale | Fishbone Diagram, Cause Categories, Investigation Backlog | Scatter Plot, Korrelationsnotiz, Hypothesenliste |
Tagsno overlap | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance | Root causeQualityOperations | Root causeQualityVisualization |