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 A3 Problem Solving |  Knowledge Modeling Linked Open Terms |  Knowledge Modeling Competency Questions |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 45-90 min | Wochen bis Monate | 2-4 h | 15-30 min |
Participantsdifferent | 2-5 | 2-8 | 2-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Root cause notes, Countermeasures |
Tagsno overlap | LeanProblem solvingCoachingOperations | OntologyMethodologyAgileSemantic | OntologyKnowledge graphScopeRequirementsSemantic | Root causeIncidentLeanProblem solving |