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 Shape-First Modeling | ![]() Operations Getting Things Done | ![]() Knowledge Modeling Competency Questions | ![]() Operations ALPEN Method |
|---|---|---|---|---|
Purposedifferent | Shape-First Modeling defines data quality through shapes before implementation or integration frays at the edges. The approach fits when validation and data contracts should be part of the design from the start. | With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory. | 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. | With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | Halber Tag pro Domain Slice | 1-2 h Setup, laufend | 2-4 h | 10-20 min daily |
Participantsdifferent | 1-4 | 1 | 2-8 | 1 |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Action Lists, Project List, Review Routine | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Daily Plan, Time Estimates, Review Notes |
Tagsno overlap | Knowledge graphValidationSemantic | ProductivityPlanningTasksExecution | OntologyKnowledge graphScopeRequirementsSemantic | PlanningTime managementProductivityOperations |



