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
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
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.When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become 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.
Complexitydifferent
LowMediumLow
Timedifferent
20-60 min1-3 h45–75 min
Participantsdifferent
14-10Team members involved
Formatdifferent
AsyncWorkshopWorkshop
Outputdifferent
Plain-language Explanation, Knowledge Gaps, Study NotesCurrent-state map, Future-state map, Bottleneck list4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
LearningKnowledgeUnderstanding
LeanFlowWasteDelivery
RetrospectiveLearningReflectionTeam
Add more methods

Often compared together

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

Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Learning Review.
Operations
Learning Review