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 Problem Interview |  UX Research Affinity Diagramming |  Domain Modeling EventStorming |  Product Discovery Experiment Canvas |
|---|---|---|---|---|
Purposedifferent | When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. | 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 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 experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 30-60 min je Interview | 45–90 min | 2-8 h | 30-60 min |
Participantsdifferent | 5-12 Interviews | 3-10 | 5-12 | 1-5 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | Theme clusters, Insight statements, Opportunity areas | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Completed Experiment Canvas, Success Metric |
Tagsno overlap | DiscoveryInterviewsValidation | SynthesisQualitativeRoot cause | Domain-Driven DesignEventsDiscoveryWorkshop | ExperimentsValidationDiscoveryHypothesis |