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 Property Graph Schema Design | ![]() Operations 5 Whys |
|---|---|---|---|
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. | Property Graph Schema Design turns business and technical requirements into a robust graph schema. It fits when query patterns, constraints, and migrations need to be thought about together. | 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 | Low |
Timedifferent | 2-4 h | 4-8 h initial, dann iterativ | 15-30 min |
Participantsdifferent | 2-8 | 1-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | Root cause notes, Countermeasures |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | Knowledge graphModelingSemantic | Root causeIncidentLeanProblem solving |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






