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 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 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 |
Timedifferent | 2-6 h | 30-60 min je Interview | 30-60 min |
Participantsdifferent | 2-8 | 5-12 Interviews | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Interview Notes, Opportunity Themes, Customer Quotes | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | DiscoveryInterviewsOpportunityCustomer | BrainstormingIdeationCreativityWorkshopDivergence |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
