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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
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.For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.
Complexitysame
LowLowLow
Timedifferent
20-60 min20-60 min15-30 min
Participantsdifferent
11-42-6
Formatdifferent
AsyncAsyncWorkshop
Outputdifferent
Plain-language Explanation, Knowledge Gaps, Study NotesRunbook, Checklist, Escalation PathRoot cause notes, Countermeasures
Tagsno overlap
LearningKnowledgeUnderstanding
OperationsReliabilityDocumentation
Root causeIncidentLeanProblem solving
Add more methods

Often compared together

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

A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe