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 | ![]() Knowledge Modeling Teach-back | ![]() Knowledge Modeling Concept Mapping | ![]() 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. | 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. | 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. | 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 | Low | Medium | Low |
Timedifferent | 20-60 min | 5-20 min | 1-2 h | 45–75 min |
Participantsdifferent | 1 | 2-8 | 1-8 | Team members involved |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | Understanding Check, Clarification Notes, Learning Gaps | Concept Map, Relationship Labels, Knowledge Gaps | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | LearningKnowledgeUnderstanding | LearningUnderstandingCommunication | KnowledgeConceptsMappingSensemaking | RetrospectiveLearningReflectionTeam |



