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 Root Cause Analysis |  Architecture arc42 |
|---|---|---|---|---|
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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 30-90 min | 15-45 min | 1-4 h | 1-2 Tage |
Participantsdifferent | 1-4 | 1-3 | 3-8 | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Scatter Plot, Korrelationsnotiz, Hypothesenliste | ADR File, Decision Log, Rationale | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | Root causeQualityVisualization | ArchitectureRationaleDocumentationGovernance | Root causeProblem solvingQualityIncident | ArchitectureDocumentationCommunication |