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 of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.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
LowMediumLowLow
Timedifferent
20-60 min1-3 h30-60 min30-60 min
Participantsdifferent
14-103-123-10
Formatdifferent
AsyncWorkshopWorkshopWorkshop
Outputdifferent
Plain-language Explanation, Knowledge Gaps, Study NotesCurrent-state map, Future-state map, Bottleneck listStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
LearningKnowledgeUnderstanding
LeanFlowWasteDelivery
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
Add more methods