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 |  Domain Modeling Context Map |  Product Strategy Impact Mapping |  Knowledge Modeling Event Modeling |
|---|---|---|---|---|
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 contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 2-4 h | 1-3 h | 45-90 min | 2-6 h |
Participantsdifferent | 2-8 | 2-8 | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Context Map, Integration Patterns, Boundary Notes | Impact Map, Outcome Hypotheses, Delivery Options | Event Model, UI Flow, Commands, Read Models |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | Domain-Driven DesignBoundariesStrategy | OutcomesStrategyBehaviorPlanning | EventsBlueprintDomain-Driven DesignBehavior |