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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.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.
Complexitydifferent
LowMediumLow
Timedifferent
20-60 min1-3 h30-60 min
Participantsdifferent
13-103-12
Formatdifferent
AsyncWorkshopWorkshop
Outputdifferent
Plain-language Explanation, Knowledge Gaps, Study NotesProcess Map, Handoff List, Improvement BacklogStart Stop Continue Board, Improvement Actions
Tagsno overlap
LearningKnowledgeUnderstanding
ProcessOperationsImprovement
RetrospectiveImprovementTeamReflection
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 of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Paper illustration for Learning Review.
Operations
Learning Review