View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Operations 5 Whys |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Root Cause Analysis |
|---|---|---|---|---|
Purposedifferent | 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 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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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 | Low | Low | High | Medium |
Timedifferent | 30 min Setup, dann laufend | 15-30 min | Several meetings plus preparation and analysis; total effort depends on scope | 1-4 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-6 | Evaluation team, architects, and relevant stakeholders | 3-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Root cause notes, Countermeasures | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Root causeIncidentLeanProblem solving | ArchitectureQualityRiskTradeoffsStakeholders | Root causeProblem solvingQualityIncident |