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 Change Analysis | ![]() Growth Hooked Model | ![]() Operations Fault Tree Analysis | ![]() Operations MORT Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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 critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | 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 | Medium | High | High |
Timedifferent | 45-120 min | Multiple workshops over several weeks | 2-6 h | Mehrere Tage bis Wochen |
Participantsdifferent | 2-6 | 2-8 | 3-8 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Hooked loop, Trigger map, Reward design, Ethics check | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | ChangeRoot causeTroubleshootingComparison | GrowthBehaviorRetention | RiskRoot causeSafety | Root causeSafetySystemicIncident |



