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 5 Whys |  Operations MORT Analysis |
|---|---|---|---|
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 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. | 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 | Low | High |
Timedifferent | 60-90 min pro Feature | 15-30 min | Mehrere Tage bis Wochen |
Participantsdifferent | 3-6 | 2-6 | 2-6 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Root cause notes, Countermeasures | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Root causeIncidentLeanProblem solving | Root causeSafetySystemicIncident |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
