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 Knowledge Mapping |  Delivery Value Stream Mapping |  Agile Ideal Days |  Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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 effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 1-3 h | 15-60 min | 1-2 h |
Participantsdifferent | 3-12 | 4-10 | 2-9 | 1-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Current-state map, Future-state map, Bottleneck list | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | KnowledgeMappingRisk | LeanFlowWasteDelivery | EstimationEffortAgile | KnowledgeConceptsMappingSensemaking |