methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration for Feynman Technique.
Knowledge Modeling
Feynman Technique
Paper illustration for Teach-back.
Knowledge Modeling
Teach-back
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Purposedifferent
Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.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.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
MediumLowLowLow
Timedifferent
1-3 h20-60 min5-20 min45–75 min
Participantsdifferent
3-1212-8Team members involved
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanPlain-language Explanation, Knowledge Gaps, Study NotesUnderstanding Check, Clarification Notes, Learning Gaps4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
KnowledgeMappingRisk
LearningKnowledgeUnderstanding
LearningUnderstandingCommunication
RetrospectiveLearningReflectionTeam
Add more methods