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 Teach-back |  Agile NoEstimates |  Knowledge Modeling Feynman Technique |
|---|---|---|---|---|
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. | Teach-back checks whether an explanation actually got through to the other person. The method makes misunderstandings visible early and strengthens shared understanding in advisory and learning situations. | When estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. | The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 5-20 min | laufend | 20-60 min |
Participantsdifferent | 4-10 | 2-8 | 2-12 | 1 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Understanding Check, Clarification Notes, Learning Gaps | Throughput Data, Flow Forecast, Slicing Rules | Plain-language Explanation, Knowledge Gaps, Study Notes |
Tagsno overlap | LeanFlowWasteDelivery | LearningUnderstandingCommunication | EstimationForecastingFlow | LearningKnowledgeUnderstanding |