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 |  Domain Modeling EventStorming |  Innovation Brainstorming |  Innovation Lotus Blossom |
|---|---|---|---|---|
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 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 a team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. | When a central question feels too large, the method breaks it into neighboring topic fields with their own depth of ideation. It holds structure and openness at the same time, so adjacent perspectives don't get lost. This grows an idea space out of a core problem. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 30-60 min je Interview | 2-8 h | 30-60 min | 45-90 min |
Participantsdifferent | 5-12 Interviews | 5-12 | 4-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Idea pool, Theme clusters, Shortlist | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | DiscoveryInterviewsValidation | Domain-Driven DesignEventsDiscoveryWorkshop | BrainstormingIdeationCreativityWorkshopDivergence | BrainstormingIdeationCreativityDivergenceWorkshop |