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
Paper illustration for ALPEN Method
Operations
ALPEN Method
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
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
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.With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.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.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.
Complexitysame
LowLowLowLow
Timedifferent
20-60 min10-20 min daily30-60 min45–75 min
Participantsdifferent
113-10Team members involved
Formatdifferent
AsyncAsyncWorkshopWorkshop
Outputdifferent
Plain-language Explanation, Knowledge Gaps, Study NotesDaily Plan, Time Estimates, Review NotesEmotion Board, Themes, Action Items4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
LearningKnowledgeUnderstanding
PlanningTime managementProductivityOperations
RetrospectiveTeamReflection
RetrospectiveLearningReflectionTeam
Add more methods