View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Opportunity Scoring |  Domain Modeling EventStorming |  UX Research Affinity Diagramming |  Product Discovery Jobs to Be Done |
|---|---|---|---|---|
Purposedifferent | When opportunities need ranking by their effect, it makes importance and satisfaction directly comparable. It separates problem, assumption, solution, and evidence. The result is captured as an opportunity-score table and top outcomes. | When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. | When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | 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 | Medium | Low | Medium |
Timedifferent | 60-120 min | 2-8 h | 45–90 min | 1-3 Wochen |
Participantsdifferent | 3-6 | 5-12 | 3-10 | 5-12 Interviews |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Opportunity Score Table, Top Outcomes | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Theme clusters, Insight statements, Opportunity areas | Job Stories, Outcome Statements, Opportunity List |
Tagsno overlap | PrioritizationDiscoveryOutcomesNeeds | Domain-Driven DesignEventsDiscoveryWorkshop | SynthesisQualitativeRoot cause | CustomerOutcomesNeeds |