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 Family Tree Analysis |  Innovation TRIZ |  Operations Root Cause Analysis |  Operations MORT Analysis |
|---|---|---|---|---|
Purposedifferent | 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 technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles. | 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 safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. |
Complexitydifferent | Medium | High | Medium | High |
Timedifferent | 2-4 h | 1-4 h | 1-4 h | Mehrere Tage bis Wochen |
Participantsdifferent | 2-6 | 2-8 | 3-8 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Family Tree Diagram, Pattern Notes, Systemic Measures | Contradiction Statement, Inventive Principles, Solution Concepts | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | Root causePatternsIncidentSystemic | InnovationProblem solvingContradictionsCreativity | Root causeProblem solvingQualityIncident | Root causeSafetySystemicIncident |