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 Bottleneck Analysis.
Operations
Bottleneck Analysis
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 Feynman Technique.
Knowledge Modeling
Feynman Technique
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput.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 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.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-3 h45–75 min20-60 min30-60 min
Participantsdifferent
3-8Team members involved13-10
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop
Outputdifferent
Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures4Ls Board, Learning Themes, Improvement ActionsPlain-language Explanation, Knowledge Gaps, Study NotesEmotion Board, Themes, Action Items
Tagsno overlap
FlowMeasurementConstraints
RetrospectiveLearningReflectionTeam
LearningKnowledgeUnderstanding
RetrospectiveTeamReflection
Add more methods