View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Kepner-Tregoe |  Architecture arc42 |  Architecture Request for Comments |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | 2-8 h | 1-2 Tage | 1-3 Wochen vom Draft bis zur Entscheidung | 15-30 min |
Participantsdifferent | 2-8 | 1-4 | 3-20 Reviewer | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Problem Analysis, Decision Analysis, Risk Plan | Architecture Document, Context View, Runtime View, Deployment View | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Root cause notes, Countermeasures |
Tagsno overlap | Problem solvingRoot causeDecisionOperations | ArchitectureDocumentationCommunication | ArchitectureDecisionAsyncGovernance | Root causeIncidentLeanProblem solving |