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
Paper illustration for Waste Analysis.
Operations
Waste 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
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.For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery.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
LowMediumLowLow
Timedifferent
20-60 min1-3 h45-120 min45–75 min
Participantsdifferent
14-102-8Team members involved
Formatdifferent
AsyncWorkshopWorkshopWorkshop
Outputdifferent
Plain-language Explanation, Knowledge Gaps, Study NotesCurrent-state map, Future-state map, Bottleneck listWaste Map, Prioritized Waste, Improvement Backlog4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
LearningKnowledgeUnderstanding
LeanFlowWasteDelivery
WasteLeanProcess improvement
RetrospectiveLearningReflectionTeam
Add more methods