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 MORT Analysis | ![]() Business Strategy VRIO Framework | ![]() Operations Family Tree 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 safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | The VRIO Framework rates resources and capabilities on whether they are Valuable, Rare, Inimitable, and Organized. It compares strengths, risks, market logic, and courses of action. The result is captured as a VRIO table and strategic actions. | 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. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 30-180 min | Mehrere Tage bis Wochen | 90-180 min | 2-4 h |
Participantsdifferent | 1-6 | 2-6 | 3-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | VRIO Table, Strategic Actions | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | TroubleshootingDiagnosisEngineering | Root causeSafetySystemicIncident | StrategyDiagnosisBusiness modelCapability | Root causePatternsIncidentSystemic |



