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 |  Product Discovery Jobs to Be Done |
|---|---|---|---|
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 switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 2-6 h | Mehrere Wochen | 1-3 Wochen |
Participantsdifferent | 2-8 | 2-6 researchers plus sample | 5-12 Interviews |
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 | Job Stories, Outcome Statements, Opportunity List |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | OutcomesInnovationResearchQuantitative | CustomerOutcomesNeeds |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
