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 Linked Open Terms | ![]() Operations 5 Whys | ![]() Operations 8D Problem Solving |
|---|---|---|---|---|
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. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. | 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 an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 2-4 h | Wochen bis Monate | 15-30 min | 1-6 Wochen |
Participantsdifferent | 2-8 | 2-8 | 2-6 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Root cause notes, Countermeasures | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | OntologyMethodologyAgileSemantic | Root causeIncidentLeanProblem solving | QualityProblem solvingRoot cause |



