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 Linked Open Terms | ![]() Operations 5 Whys | ![]() Operations A3 Problem Solving | ![]() Knowledge Modeling NeOn Methodology |
|---|---|---|---|---|
Purposedifferent | 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 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. | The NeOn Methodology structures ontology work as a controlled process with reuse, scenarios, and reviews. It is useful when ontologies should not emerge ad hoc but modularly and reusably. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | Wochen bis Monate | 15-30 min | 45-90 min | Mehrere Wochen bis Monate |
Participantsdifferent | 2-8 | 2-6 | 2-5 | 2-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Root cause notes, Countermeasures | A3 Report, Action Plan, Root Cause Analysis | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report |
Tagsno overlap | OntologyMethodologyAgileSemantic | Root causeIncidentLeanProblem solving | LeanProblem solvingCoachingOperations | OntologyMethodologyReuseSemanticEngineering |



