View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling Domain Storytelling | ![]() Operations MORT Analysis | ![]() Operations Family Tree Analysis | ![]() Operations Fault Tree Analysis |
|---|---|---|---|---|
Purposedifferent | Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected. | 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. | 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. |
Complexitydifferent | Low | High | Medium | High |
Timedifferent | 1-2 h | Mehrere Tage bis Wochen | 2-4 h | 2-6 h |
Participantsdifferent | 2-8 | 2-6 | 2-6 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Family Tree Diagram, Pattern Notes, Systemic Measures | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | Root causeSafetySystemicIncident | Root causePatternsIncidentSystemic | RiskRoot causeSafety |



