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 | ![]() Decision Making Decision Matrix | ![]() Product Strategy RICE Scoring | ![]() Delivery MoSCoW |
|---|---|---|---|---|
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 several options collide with several criteria, comparison quickly becomes subjective. A Decision Matrix makes the trade-off visible and brings weighting, criteria, and options into a shared logic. | When many initiatives compete for the same resources, it brings reach, impact, confidence, and effort into one shared ranking. It makes prioritization economically connectable. | When a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 2-4 h | 45-90 min | 60-90 min | 30-90 min |
Participantsdifferent | 2-8 | 2-8 | 2-10 | 3-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Decision Matrix, Scoring Rationale, Selected Option | RICE Scores, Ranked List, Assumption Log | Prioritized Backlog, Release Scope, Tradeoff Notes |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | DecisionCriteriaScoringTradeoffs | PrioritizationScoringRoadmapTradeoffs | PrioritizationScopeDecision |



