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 Family Tree Analysis |  Operations Root Cause Analysis |  Operations Failure Mode and Effects 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 series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. | 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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 30 min Setup, dann laufend | 2-4 h | 1-4 h | 2-6 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-6 | 3-8 | 3-10 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | Family Tree Diagram, Pattern Notes, Systemic Measures | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Root causePatternsIncidentSystemic | Root causeProblem solvingQualityIncident | RiskQualityOperationsRoot cause |