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 Feynman Technique | ![]() Delivery Value Stream Mapping | ![]() Operations Waste Analysis | ![]() Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 20-60 min | 1-3 h | 45-120 min | 45–75 min |
Participantsdifferent | 1 | 4-10 | 2-8 | Team members involved |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | Current-state map, Future-state map, Bottleneck list | Waste Map, Prioritized Waste, Improvement Backlog | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | LearningKnowledgeUnderstanding | LeanFlowWasteDelivery | WasteLeanProcess improvement | RetrospectiveLearningReflectionTeam |



