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 Fishbone Diagram |  Operations Fault Tree Analysis |  Agile Specification by Example |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | 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 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. | 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. |
Complexitydifferent | Low | High | Medium | Low |
Timedifferent | 30-60 min | 2-6 h | 60-90 min pro Feature | 30-60 min |
Participantsdifferent | 2-8 | 3-8 | 3-6 | 3-7 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Fishbone Diagram, Cause Categories, Investigation Backlog | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | Root causeQualityOperations | RiskRoot causeSafety | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement |