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 |  Operations 5 Whys |  Knowledge Modeling Property Graph Schema Design |  Operations A3 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. | 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. | 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 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 2-4 h | 15-30 min | 4-8 h initial, dann iterativ | 45-90 min |
Participantsdifferent | 2-8 | 2-6 | 1-6 | 2-5 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Root cause notes, Countermeasures | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | Root causeIncidentLeanProblem solving | Knowledge graphModelingSemantic | LeanProblem solvingCoachingOperations |