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 5 Whys |  Architecture C4 Model |  Operations Root Cause Analysis |  Operations Scatter Diagram |
|---|---|---|---|---|
Purposedifferent | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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 keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | 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 | Medium | Low |
Timedifferent | 15-30 min | 1-4 h | 1-4 h | 30-90 min |
Participantsdifferent | 2-6 | 1-5 | 3-8 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Root cause notes, Countermeasures | Context Diagram, Container Diagram, Component Diagram | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Scatter Plot, Korrelationsnotiz, Hypothesenliste |
Tagsno overlap | Root causeIncidentLeanProblem solving | ArchitectureCommunicationVisualization | Root causeProblem solvingQualityIncident | Root causeQualityVisualization |