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 |  Delivery RAID Log |  Operations Kepner-Tregoe |  Operations 5 Whys |
|---|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 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. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 30 min Setup, dann laufend | 2-8 h | 15-30 min |
Participantsdifferent | 3-20 Reviewer | 1-3 maintaining, briefing for everyone | 2-8 | 2-6 |
Formatdifferent | Async | Async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | RAID Log, Status Report Source | Problem Analysis, Decision Analysis, Risk Plan | Root cause notes, Countermeasures |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | RiskTrackingStakeholdersGovernance | Problem solvingRoot causeDecisionOperations | Root causeIncidentLeanProblem solving |