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 Architecture Decision Record |  Operations ABC Analysis |  Operations Root Cause Analysis |  Operations Fishbone Diagram |
|---|---|---|---|---|
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. | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 15-45 min | 30-60 min | 1-4 h | 30-60 min |
Participantsdifferent | 1-3 | 1-5 | 3-8 | 2-8 |
Formatdifferent | Async | Async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | ABC Classification, Focus Rules, Control List | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | PrioritizationOperationsPortfolio | Root causeProblem solvingQualityIncident | Root causeQualityOperations |