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 Kepner-Tregoe |  Operations Change Analysis |  Operations A3 Problem Solving |
|---|---|---|---|---|
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 disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 2-8 h | 45-120 min | 45-90 min |
Participantsdifferent | 3-20 Reviewer | 2-8 | 2-6 | 2-5 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Problem Analysis, Decision Analysis, Risk Plan | Change Matrix, Cause Hypotheses, Validation Questions, Action List | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | Problem solvingRoot causeDecisionOperations | ChangeRoot causeTroubleshootingComparison | LeanProblem solvingCoachingOperations |