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 |  Decision Making Constraint Analysis |  Operations A3 Problem Solving |  Operations Kepner-Tregoe |
|---|---|---|---|---|
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. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 30-90 min | 45-90 min | 2-8 h |
Participantsdifferent | 3-20 Reviewer | 2-8 | 2-5 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | A3 Report, Action Plan, Root Cause Analysis | Problem Analysis, Decision Analysis, Risk Plan |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | ConstraintsDecisionPlanningOptions | LeanProblem solvingCoachingOperations | Problem solvingRoot causeDecisionOperations |