The Feynman Technique

What Feynman actually did

Richard Feynman won the 1965 Nobel Prize in Physics for his work on quantum electrodynamics. He was also one of the most celebrated teachers of physics in the twentieth century, often called the "Great Explainer." His Feynman Lectures on Physics remain in print decades later.

Feynman himself did not publish a four-step technique. The named "Feynman Technique" was distilled by later authors from his teaching practice and personal habits. James Gleick's biography Genius: The Life and Science of Richard Feynman describes a notebook Feynman kept titled "Notebook of things I don't know about" — a record of concepts he couldn't yet explain simply. His method of working through an unfamiliar topic was to write out an explanation, find where the explanation broke down, and then fill in the actual physics.

The technique as commonly taught today preserves this pattern.

The four steps

1. Choose one specific concept. Write it at the top of a page. Resist the urge to pick a broad topic — "thermodynamics" is too big; "the second law of thermodynamics" is workable.

2. Explain it in simple language, as if to someone with no background. Avoid jargon. Use analogies and everyday examples. Write or speak the explanation in full sentences, not bullet points.

3. Identify where you got stuck. The places where you reached for jargon, the steps you glossed over, the connections you couldn't make explicit — these are your knowledge gaps. Mark them.

4. Go back to the source material to fix the gaps. Read, watch a lecture, work through a textbook section, talk to someone who knows. Then return to step 2 and try the explanation again.

The loop continues until your explanation flows without jargon-shaped patches. At that point, you have something close to genuine understanding rather than fluent recognition.

Why it works

The technique combines three well-evidenced cognitive principles:

Active retrieval. Producing an explanation from memory is a retrieval event. Roediger and Karpicke's testing-effect research (2006) established that retrieval strengthens memory more than re-reading. The Feynman Technique is essentially an extended free-recall exercise where the question is "what do you actually know about this?"

Self-explanation. Chi, de Leeuw, Chiu, and LaVancher (1994) studied biology students who were prompted to explain text passages to themselves. The self-explanation group developed substantially deeper conceptual understanding and stronger problem-solving abilities than students who simply read the same material. Self-explanation forces inference, integration with prior knowledge, and gap-identification.

Expecting to teach. Nestojko, Bui, Kornell, and Bjork (2014) had participants study a passage either expecting to be tested on it or expecting to teach it to another person who would then be tested. The teach-expectant group performed better on retention measures and showed signs of more organized memory. The mere expectation of having to explain changes how you encode the material.

Learning by teaching. Fiorella and Mayer (2013, 2014) directly tested whether explaining a video lesson to a future learner produced better understanding than simply studying it twice. The teaching condition consistently outperformed the restudy condition on tests measuring deep understanding, even when test time was equated.

Dunlosky and colleagues (2013), in their influential review of ten common study techniques, rated self-explanation as a "moderate utility" technique — well-supported by research and broadly applicable, though slightly less universally effective than distributed practice and practice testing.

Where it works best

The Feynman Technique is most powerful for material with internal logical structure: physics concepts, mathematical proofs, programming patterns, biological processes, historical causes-and-effects. Anywhere the parts connect to each other through reasoning, explaining the connections exposes whether you actually have them.

It's less directly useful for material that is essentially a list of arbitrary facts — vocabulary translations, historical dates, drug-class members. For those, the bottleneck is encoding and durability, not understanding. A memory palace plus spaced repetition fits that situation better.

That said: even pure fact-learning benefits from understanding why a fact is the case. Knowing that ACE inhibitors end in "-pril" is faster to memorize when you understand they all share a mechanism on the same enzyme. The Feynman Technique builds the why layer; flashcards then handle the durable storage of the what.

Common failure modes

Picking a topic that's too broad. "Quantum mechanics" cannot be Feynman-explained in one session. "Why does the uncertainty principle prevent simultaneous precise measurement of position and momentum" can.

Skipping the gap-identification step. It's tempting to read your explanation, feel good about it, and stop. The discipline is to look for the parts you handwaved through. Those are where the technique pays off.

Not actually retrieving. Looking at the source material while you write the explanation defeats the purpose. The explanation should come from memory; the source is for filling gaps afterward.

Using it on material you don't need to deeply understand. If you only need to recognize a fact on a multiple-choice exam, the Feynman Technique is overkill. Reserve it for material where understanding matters — concepts you'll need to apply, problems you'll need to solve.

A worked example

Suppose you're studying for a programming interview and the topic is "closures in JavaScript."

Attempt 1. You write: "A closure is when a function remembers the variables from where it was defined, so it can use them later, even when called somewhere else."

Gap check. You notice you wrote "remembers" — but how does it actually remember? You wrote "the variables from where it was defined" — but is it the variables themselves or references to them? What happens if those variables change after the closure is created?

Refine. You go back to MDN, work through the lexical-scope mechanism, write a small example with let and var to see the variable-vs-reference behavior, and come back.

Attempt 2. "A closure is a function plus the lexical scope in which it was defined. When the function runs, it accesses variables through a reference to that scope chain — so it sees the variable's current value at call time, not its value at definition time. This is why a loop creating closures with var produces surprising results: each closure references the same loop variable, not a snapshot of it."

The second explanation is substantially better — and writing it forced you to confront the parts of "closures" you hadn't actually internalized.

Related reading

Metacognition

Judgments of learning, the illusion of competence, and how to calibrate your sense of what you actually know — Dunlosky's research on why students consistently misjudge their understanding.

Retrieval Practice

Why testing yourself is a learning event, not just an assessment — and how the testing effect makes flashcard reviews more powerful than re-study.

Cornell Notes

Walter Pauk's 1950s note-taking system: how the three-section layout works, what research shows about its effectiveness, and how to convert Cornell notes into flashcards.