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 |  Knowledge Modeling Event Modeling |  Innovation Design Thinking |  Product Discovery Concierge MVP |
|---|---|---|---|---|
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. | 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. | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. | When an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 30-60 min je Interview | 2-6 h | 1 Tag bis mehrere Wochen | 1-4 Wochen |
Participantsdifferent | 5-12 Interviews | 2-8 | 4-10 | 3-10 Kunden |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | Event Model, UI Flow, Commands, Read Models | Problem Statement, Prototype, Test Learnings | Concierge Learnings, Service Blueprint, MVP Risks |
Tagsno overlap | DiscoveryInterviewsValidation | EventsBlueprintDomain-Driven DesignBehavior | InnovationPrototypeResearch | MVPValidationServiceDiscovery |