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 |  Innovation Brainstorming |  Domain Modeling EventStorming |  Innovation Lotus Blossom |
|---|---|---|---|---|
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 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 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 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 | Low | Medium | Low |
Timedifferent | 30-60 min je Interview | 30-60 min | 2-8 h | 45-90 min |
Participantsdifferent | 5-12 Interviews | 4-12 | 5-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Idea pool, Theme clusters, Shortlist | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | BrainstormingIdeationCreativityWorkshopDivergence | Domain-Driven DesignEventsDiscoveryWorkshop | BrainstormingIdeationCreativityDivergenceWorkshop |