View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Event Modeling |  Product Discovery Opportunity Interview |  Innovation Lotus Blossom |  Innovation Brainstorming |
|---|---|---|---|---|
Purposedifferent | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | 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 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 2-6 h | 30-60 min je Interview | 45-90 min | 30-60 min |
Participantsdifferent | 2-8 | 5-12 Interviews | 3-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Interview Notes, Opportunity Themes, Customer Quotes | Lotus Diagram, Idea Themes, Shortlist | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | DiscoveryInterviewsOpportunityCustomer | BrainstormingIdeationCreativityDivergenceWorkshop | BrainstormingIdeationCreativityWorkshopDivergence |