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 Root Cause Analysis |  Decision Making Force Field Analysis |  Operations MORT Analysis |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 1-4 h | 45-90 min | Mehrere Tage bis Wochen | 15-30 min |
Participantsdifferent | 3-8 | 3-12 | 2-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Force Field Map, Change Levers, Risk Notes | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Root cause notes, Countermeasures |
Tagsno overlap | Root causeProblem solvingQualityIncident | ChangeDecisionStrategy | Root causeSafetySystemicIncident | Root causeIncidentLeanProblem solving |