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 Concept Mapping | ![]() Product Strategy Lean Canvas | ![]() Product Discovery Pretotyping |
|---|---|---|---|
Purposedifferent | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-2 h | 45-90 min | Stunden bis wenige Tage |
Participantsdifferent | 1-8 | 1-6 | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Lean Canvas, Core Assumptions, Experiment Backlog | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | StartupLeanAssumptionsBusiness model | ValidationDemandMVP |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






