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 Pretotyping |  Domain Modeling EventStorming |  Product Discovery Concierge MVP |  Innovation Lean Startup |
|---|---|---|---|---|
Purposedifferent | Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data. | 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 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. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 2-8 h | 1-4 Wochen | Wochen bis Monate je Lernzyklus |
Participantsdifferent | 1-4 | 5-12 | 3-10 Kunden | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Concierge Learnings, Service Blueprint, MVP Risks | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision |
Tagsno overlap | ValidationDemandMVP | Domain-Driven DesignEventsDiscoveryWorkshop | MVPValidationServiceDiscovery | LeanStartupValidationMVP |