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 MORT Analysis |  Operations 5 Whys |  Operations Fault Tree 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 safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | 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. | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. |
Complexitydifferent | Low | High | Low | High |
Timedifferent | 30 min Setup, dann laufend | Mehrere Tage bis Wochen | 15-30 min | 2-6 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-6 | 2-6 | 3-8 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Root cause notes, Countermeasures | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Root causeSafetySystemicIncident | Root causeIncidentLeanProblem solving | RiskRoot causeSafety |