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 |  Architecture Architecture Decision Record |  Operations 5 Whys |  Operations Root Cause Tree Analysis |
|---|---|---|---|---|
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. | 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. | 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. | For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 30-90 min | 15-45 min | 15-30 min | 1-3 h |
Participantsdifferent | 1-4 | 1-3 | 2-6 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Scatter Plot, Korrelationsnotiz, Hypothesenliste | ADR File, Decision Log, Rationale | Root cause notes, Countermeasures | Cause Tree, Evidence Notes, Countermeasures |
Tagsno overlap | Root causeQualityVisualization | ArchitectureRationaleDocumentationGovernance | Root causeIncidentLeanProblem solving | Root causeTreeIncidentQuality |