View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Fishbone DiagramCompetency QuestionsSpecification by ExampleFailure Mode and Effects Analysis
| Criterion |  Operations Fishbone Diagram |  Knowledge Modeling Competency Questions |  Agile Specification by Example |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
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. | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. | 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 process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 30-60 min | 2-4 h | 60-90 min pro Feature | 2-6 h |
Participantsdifferent | 2-8 | 2-8 | 3-6 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Fishbone Diagram, Cause Categories, Investigation Backlog | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Example Table, Acceptance Tests | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | Root causeQualityOperations | OntologyKnowledge graphScopeRequirementsSemantic | AgileRequirementsExamplesBehavior-Driven Development | RiskQualityOperationsRoot cause |