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 Request for Comments |  Operations 5 Whys |  Operations Kepner-Tregoe |  Operations Root Cause Analysis |
|---|---|---|---|---|
Purposedifferent | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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 disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | 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 | Medium | Low | High | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 15-30 min | 2-8 h | 1-4 h |
Participantsdifferent | 3-20 Reviewer | 2-6 | 2-8 | 3-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Root cause notes, Countermeasures | Problem Analysis, Decision Analysis, Risk Plan | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | Root causeIncidentLeanProblem solving | Problem solvingRoot causeDecisionOperations | Root causeProblem solvingQualityIncident |