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 Property Graph Schema Design |  Operations MORT Analysis |  Knowledge Modeling Competency Questions |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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 safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | 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 | High | Medium | Low |
Timedifferent | 4-8 h initial, dann iterativ | Mehrere Tage bis Wochen | 2-4 h | 15-30 min |
Participantsdifferent | 1-6 | 2-6 | 2-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Root cause notes, Countermeasures |
Tagsno overlap | Knowledge graphModelingSemantic | Root causeSafetySystemicIncident | OntologyKnowledge graphScopeRequirementsSemantic | Root causeIncidentLeanProblem solving |