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 Mad Sad Glad
Agile
Mad Sad Glad
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
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 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.After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.
Complexitydifferent
LowLowMedium
Timedifferent
20-60 min30-60 min30-90 min
Participantsdifferent
13-103-12
Formatdifferent
AsyncWorkshopWorkshop + async
Outputdifferent
Plain-language Explanation, Knowledge Gaps, Study NotesEmotion Board, Themes, Action ItemsPostmortem Doc, Action Items, Timeline
Tagsno overlap
LearningKnowledgeUnderstanding
RetrospectiveTeamReflection
Site Reliability EngineeringIncidentLearningReliability
Add more methods

Often compared together

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

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 Learning Review.
Operations
Learning Review
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command