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 5 Whys | ![]() Innovation Contradiction Analysis | ![]() Operations MORT Analysis | ![]() Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | When a system should improve while another measure suffers as a result, the method makes the underlying conflict precisely formulable. It separates the desired effect from its side effect. This makes solutions possible that address the contradiction deliberately instead of half-heartedly. | 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 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 | Low | Medium | High | Medium |
Timedifferent | 15-30 min | 60-120 min | Mehrere Tage bis Wochen | 2-4 h |
Participantsdifferent | 2-6 | 2-8 | 2-6 | 2-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Root cause notes, Countermeasures | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | Root causeIncidentLeanProblem solving | ContradictionsInnovationProblem solving | Root causeSafetySystemicIncident | Root causePatternsIncidentSystemic |



