View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Competency Questions |  Knowledge Modeling Ontology Design Patterns |  Operations 5 Whys |  Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. | 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 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 2-4 h | 1-3 h pro Pattern | 15-30 min | 2-4 h |
Participantsdifferent | 2-8 | 1-6 | 2-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Selected Patterns, Adapted Schema Fragments, Pattern Documentation | Root cause notes, Countermeasures | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | OntologyPatternsReuseSemanticModeling | Root causeIncidentLeanProblem solving | Root causePatternsIncidentSystemic |