View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordRoot Cause Tree AnalysisAffinity DiagrammingRoot Cause Analysis
| Criterion |  Architecture Architecture Decision Record |  Operations Root Cause Tree Analysis |  UX Research Affinity Diagramming |  Operations Root Cause Analysis |
|---|---|---|---|---|
Purposedifferent | 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 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. | When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | 1-3 h | 45–90 min | 1-4 h |
Participantsdifferent | 1-3 | 2-8 | 3-10 | 3-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Cause Tree, Evidence Notes, Countermeasures | Theme clusters, Insight statements, Opportunity areas | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Root causeTreeIncidentQuality | SynthesisQualitativeRoot cause | Root causeProblem solvingQualityIncident |