View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Example Mapping |  Operations Barrier Analysis |  Operations Family Tree Analysis |  Operations MORT Analysis |
|---|---|---|---|---|
Purposedifferent | 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 risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. | 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 safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 30-60 min | 2-4 h | 2-4 h | Mehrere Tage bis Wochen |
Participantsdifferent | 3-7 | 2-6 | 2-6 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Family Tree Diagram, Pattern Notes, Systemic Measures | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Root causeSafetyIncident | Root causePatternsIncidentSystemic | Root causeSafetySystemicIncident |