View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Expectation Mapping |  Operations Root Cause Analysis |  Operations Family Tree Analysis |  Operations MORT Analysis |
|---|---|---|---|---|
Purposedifferent | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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 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. | 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. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 45-90 min | 1-4 h | 2-4 h | Mehrere Tage bis Wochen |
Participantsdifferent | 3-12 | 3-8 | 2-6 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Family Tree Diagram, Pattern Notes, Systemic Measures | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | AlignmentStakeholdersTeam | Root causeProblem solvingQualityIncident | Root causePatternsIncidentSystemic | Root causeSafetySystemicIncident |