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
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
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration for Feynman Technique.
Knowledge Modeling
Feynman Technique
Purposedifferent
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.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.
Complexitydifferent
LowMediumLow
Timedifferent
45–75 min1-3 h20-60 min
Participantsdifferent
Team members involved3-121
Formatdifferent
WorkshopWorkshopAsync
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsKnowledge Map, Critical Knowledge Areas, Transfer PlanPlain-language Explanation, Knowledge Gaps, Study Notes
Tagsno overlap
RetrospectiveLearningReflectionTeam
KnowledgeMappingRisk
LearningKnowledgeUnderstanding
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
Paper illustration for Learning Review.
Operations
Learning Review