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 PARA Method | ![]() Innovation Lean Startup | ![]() Knowledge Modeling Concept Mapping | ![]() Product Discovery Pretotyping |
|---|---|---|---|---|
Purposedifferent | The PARA Method organizes knowledge into Projects, Areas, Resources, and Archives. It creates order when digital notes, files, and tasks no longer cleanly fit current work. | 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. | 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. | 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 | Medium | Low |
Timedifferent | 1-3 h Setup, laufend | Wochen bis Monate je Lernzyklus | 1-2 h | Stunden bis wenige Tage |
Participantsdifferent | 1 | 2-8 | 1-8 | 1-4 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Concept Map, Relationship Labels, Knowledge Gaps | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision |
Tagsno overlap | KnowledgeProductivityOrganization | LeanStartupValidationMVP | KnowledgeConceptsMappingSensemaking | ValidationDemandMVP |



