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 | ![]() Knowledge Modeling Knowledge Mapping | ![]() Operations Waste Analysis | ![]() 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. | 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. | For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. | 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 | 45-120 min | 1-2 h |
Participantsdifferent | 4-10 | 3-12 | 2-8 | 1-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Waste Map, Prioritized Waste, Improvement Backlog | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | LeanFlowWasteDelivery | KnowledgeMappingRisk | WasteLeanProcess improvement | KnowledgeConceptsMappingSensemaking |



