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 |  Agile Example Mapping |  Operations Family Tree Analysis |
|---|---|---|---|
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. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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 | High | Low | Medium |
Timedifferent | 2-6 h | 30-60 min | 2-4 h |
Participantsdifferent | 3-8 | 3-7 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Example Map, Acceptance Criteria, Open Questions | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | RiskRoot causeSafety | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Root causePatternsIncidentSystemic |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
