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 Feynman Technique.
Knowledge Modeling
Feynman Technique
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 Eat the Frog
Operations
Eat the Frog
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
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.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.The method protects energy and attention for the task that creates the largest progress and is often postponed.When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.
Complexitysame
LowLowLowLow
Timedifferent
20-60 min45–75 min15-90 min daily30-60 min
Participantsdifferent
1Team members involved13-10
Formatdifferent
AsyncWorkshopAsyncWorkshop
Outputdifferent
Plain-language Explanation, Knowledge Gaps, Study Notes4Ls Board, Learning Themes, Improvement ActionsPriority Task, Completion Note, Daily FocusEmotion Board, Themes, Action Items
Tagsno overlap
LearningKnowledgeUnderstanding
RetrospectiveLearningReflectionTeam
PrioritizationProductivityFocusExecution
RetrospectiveTeamReflection
Add more methods