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 Fault Tree Analysis |  Growth Hooked Model |  Operations MORT Analysis |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | The Hooked Model helps clarify engagement loops, user behavior, and experiments. It makes repeat behavior measurable and captures the result as a hooked loop, trigger map, and reward design. | 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 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. |
Complexitydifferent | High | Medium | High | Low |
Timedifferent | 2-6 h | Multiple workshops over several weeks | Mehrere Tage bis Wochen | 15-30 min |
Participantsdifferent | 3-8 | 2-8 | 2-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Hooked loop, Trigger map, Reward design, Ethics check | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Root cause notes, Countermeasures |
Tagsno overlap | RiskRoot causeSafety | GrowthBehaviorRetention | Root causeSafetySystemicIncident | Root causeIncidentLeanProblem solving |