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 | ![]() Knowledge Modeling Competency Questions | ![]() Product Strategy Lean Canvas |
|---|---|---|---|
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. | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. | 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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 2-4 h | 45-90 min |
Participantsdifferent | 1-4 | 2-8 | 1-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Lean Canvas, Core Assumptions, Experiment Backlog |
Tagsno overlap | ValidationDemandMVP | OntologyKnowledge graphScopeRequirementsSemantic | StartupLeanAssumptionsBusiness model |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






