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 Specification by Example |  Operations MORT Analysis |  Operations Family Tree Analysis |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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 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 | Medium | High | Medium | Low |
Timedifferent | 60-90 min pro Feature | Mehrere Tage bis Wochen | 2-4 h | 15-30 min |
Participantsdifferent | 3-6 | 2-6 | 2-6 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Family Tree Diagram, Pattern Notes, Systemic Measures | Root cause notes, Countermeasures |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Root causeSafetySystemicIncident | Root causePatternsIncidentSystemic | Root causeIncidentLeanProblem solving |