methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration of NeOn Methodology with its method-specific working model.
Knowledge Modeling
NeOn Methodology
Paper illustration of Ontology Design Patterns with its method-specific working model.
Knowledge Modeling
Ontology Design Patterns
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Purposedifferent
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.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.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 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
LowHighMediumHigh
Timedifferent
15-30 minMehrere Wochen bis Monate1-3 h pro Pattern1-6 Wochen
Participantsdifferent
2-62-101-64-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Root cause notes, CountermeasuresOntology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation ReportSelected Patterns, Adapted Schema Fragments, Pattern Documentation8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan
Tagsno overlap
Root causeIncidentLeanProblem solving
OntologyMethodologyReuseSemanticEngineering
OntologyPatternsReuseSemanticModeling
QualityProblem solvingRoot cause
Add more methods