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 |  Product Strategy Lean Canvas |  Domain Modeling EventStorming |  Business Strategy 5-Minuten VC-Check |
|---|---|---|---|---|
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 an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable. | 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. | The 5-Minute VC Check clarifies opportunities and strategic options at the earliest idea stage. It compares problem quality, customer willingness to pay, alternatives, differentiation, and market potential, and captures the result as a VC-check note, go/sharpen/park decision, and risk list. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | Stunden bis wenige Tage | 45-90 min | 2-8 h | 5-15 min |
Participantsdifferent | 1-4 | 1-6 | 5-12 | 1-5 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Lean Canvas, Core Assumptions, Experiment Backlog | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step |
Tagsno overlap | ValidationDemandMVP | StartupLeanAssumptionsBusiness model | Domain-Driven DesignEventsDiscoveryWorkshop | StartupValidationCompetition |