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
Paper illustration of Competency Questions with its method-specific working model.
Knowledge Modeling
Competency Questions
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration of Property Graph Schema Design with its method-specific working model.
Knowledge Modeling
Property Graph Schema Design
Paper illustration for 8D Problem Solving.
Operations
8D 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.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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 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
MediumLowMediumHigh
Timedifferent
2-4 h30-60 min4-8 h initial, dann iterativ1-6 Wochen
Participantsdifferent
2-82-81-64-10
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Competency Question Set, Required Concepts, Test Queries, Coverage MatrixFishbone Diagram, Cause Categories, Investigation BacklogSchema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan
Tagsno overlap
OntologyKnowledge graphScopeRequirementsSemantic
Root causeQualityOperations
Knowledge graphModelingSemantic
QualityProblem solvingRoot cause
Add more methods