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 |  Knowledge Modeling Feynman Technique |  Engineering Kanban |
|---|---|---|---|---|
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. | 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 work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 5-20 min | 20-60 min | Ongoing |
Participantsdifferent | 4-10 | 2-8 | 1 | 2-12 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Understanding Check, Clarification Notes, Learning Gaps | Plain-language Explanation, Knowledge Gaps, Study Notes | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | LeanFlowWasteDelivery | LearningUnderstandingCommunication | LearningKnowledgeUnderstanding | FlowVisual managementDelivery |