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
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 Root Cause Analysis.
Operations
Root Cause Analysis
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 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 problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
LowLowMedium
Timedifferent
20-60 min30-60 min1-4 h
Participantsdifferent
13-123-8
Formatdifferent
AsyncWorkshopWorkshop + async
Outputdifferent
Plain-language Explanation, Knowledge Gaps, Study NotesStart Stop Continue Board, Improvement ActionsProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
LearningKnowledgeUnderstanding
RetrospectiveImprovementTeamReflection
Root causeProblem solvingQualityIncident
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 for 8D Problem Solving.
Operations
8D Problem Solving
Paper illustration for Learning Review.
Operations
Learning Review