View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Fault Isolation |  Operations Family Tree Analysis |  Operations MORT Analysis |  Operations Change Analysis |
|---|---|---|---|---|
Purposedifferent | In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected. | 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. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 30-180 min | 2-4 h | Mehrere Tage bis Wochen | 45-120 min |
Participantsdifferent | 1-6 | 2-6 | 2-6 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Family Tree Diagram, Pattern Notes, Systemic Measures | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Change Matrix, Cause Hypotheses, Validation Questions, Action List |
Tagsno overlap | TroubleshootingDiagnosisEngineering | Root causePatternsIncidentSystemic | Root causeSafetySystemicIncident | ChangeRoot causeTroubleshootingComparison |