View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery Value Stream Mapping | ![]() Product Discovery Assumption Mapping | ![]() Knowledge Modeling Knowledge Mapping | ![]() Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
Purposedifferent | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 45-60 min | 1-3 h | 1-2 h |
Participantsdifferent | 4-10 | 2-8 | 3-12 | 1-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Assumption map, Test backlog, Risk ranking | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | LeanFlowWasteDelivery | AssumptionsRiskExperimentsValidation | KnowledgeMappingRisk | KnowledgeConceptsMappingSensemaking |



