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 Teach-back.
Knowledge Modeling
Teach-back
Paper illustration for Feynman Technique.
Knowledge Modeling
Feynman Technique
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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.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 a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.
Complexitysame
LowLowLowLow
Timedifferent
45–75 min5-20 min20-60 min30-60 min
Participantsdifferent
Team members involved2-813-12
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsUnderstanding Check, Clarification Notes, Learning GapsPlain-language Explanation, Knowledge Gaps, Study NotesStart Stop Continue Board, Improvement Actions
Tagsno overlap
RetrospectiveLearningReflectionTeam
LearningUnderstandingCommunication
LearningKnowledgeUnderstanding
RetrospectiveImprovementTeamReflection
Add more methods