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 of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Paper illustration for Feynman Technique.
Knowledge Modeling
Feynman Technique
Paper illustration for Learning Review.
Operations
Learning Review
Purposedifferent
After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.
Complexitydifferent
LowLowMedium
Timedifferent
20-45 min20-60 min1-3 h
Participantsdifferent
3-1213-10
Formatdifferent
Workshop + asyncAsyncWorkshop
Outputdifferent
Lessons learned, Action items, Event summaryPlain-language Explanation, Knowledge Gaps, Study NotesLearning Review Notes, System Factors, Improvement Actions
Tags1 shared
LearningOperationsImprovement
LearningKnowledgeUnderstanding
LearningRetrospectiveIncidentOperations
Add more methods

Often compared together

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

The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem