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 Concept Mapping | ![]() Delivery Monte Carlo Forecasting |
|---|---|---|---|
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. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 1-3 h | 1-2 h | 30-90 min Setup, danach laufend |
Participantsdifferent | 4-10 | 1-8 | 1-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Concept Map, Relationship Labels, Knowledge Gaps | Forecast Percentiles, Throughput Dataset, Risk Communication |
Tagsno overlap | LeanFlowWasteDelivery | KnowledgeConceptsMappingSensemaking | ForecastingFlowDelivery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






