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 Interview | ![]() Facilitation Decision Jam | ![]() Domain Modeling EventStorming |
|---|---|---|---|
Purposedifferent | When opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. | When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 30-60 min je Interview | 60-90 min | 2-8 h |
Participantsdifferent | 5-12 Interviews | 4-10 | 5-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Problem Cluster, Prioritized Challenge, Experiment | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | FacilitationDecisionProblem solvingWorkshop | Domain-Driven DesignEventsDiscoveryWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






