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 Event Modeling |  Product Discovery Outcome-Driven Innovation |  Domain Modeling Context Map |
|---|---|---|---|
Purposedifferent | 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. | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | 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. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 2-6 h | Mehrere Wochen | 1-3 h |
Participantsdifferent | 2-8 | 2-6 researchers plus sample | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | OutcomesInnovationResearchQuantitative | Domain-Driven DesignBoundariesStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
