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 |  Operations Fishbone Diagram |  Operations Kepner-Tregoe |  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. | 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. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | 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. |
Complexitydifferent | Low | Low | High | Low |
Timedifferent | 1-4 h | 30-60 min | 2-8 h | 30-90 min |
Participantsdifferent | 1-5 | 2-8 | 2-8 | 1-4 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Fishbone Diagram, Cause Categories, Investigation Backlog | Problem Analysis, Decision Analysis, Risk Plan | Scatter Plot, Korrelationsnotiz, Hypothesenliste |
Tagsno overlap | ArchitectureCommunicationVisualization | Root causeQualityOperations | Problem solvingRoot causeDecisionOperations | Root causeQualityVisualization |