Named after a physicist known for clarity
Richard Feynman, the Nobel Prize-winning physicist, was known for an unusual ability to explain deeply technical physics in plain, accessible language, and he treated that ability as inseparable from actually understanding a topic — his view, often summarized in a line attributed to him, was that if a concept can't be explained simply, it isn't truly understood yet. The technique named after him turns that belief into a repeatable study method.
The four steps
1. Choose a concept and write its name at the top of a blank page. Anything from a single formula to a broad topic works — the technique scales to whatever's being studied.
2. Explain it in plain language, as if teaching it to someone with no background in the subject. Not to a peer already familiar with the field, and not using the field's specialized vocabulary as a shortcut — genuinely plain language, the kind that would make sense to a curious child or an interested adult from outside the subject. This constraint is the core of the technique; the rest of the steps depend on taking it seriously rather than treating it as a formality.
3. Identify exactly where the explanation breaks down or gets vague. Somewhere in step 2, the explanation will hit a point where it starts leaning on jargon, hand-waving ("and then this basically happens"), or a term that hasn't actually been unpacked into simpler pieces. That point is not a minor gap — it's the specific location of a real hole in understanding, and it's usually invisible until an attempt is made to explain the material in genuinely plain terms.
4. Go back to the source material, fill that specific gap, and simplify the explanation further. Rather than re-studying the whole topic broadly, return to the source with a narrow, specific question generated by step 3, and use the answer to patch that exact gap. Then revise the explanation again, ideally making it even simpler and more direct than the first attempt — a good sign the technique is working is that the explanation gets shorter and clearer with each pass, not longer.
Why plain language specifically does the work
Technical vocabulary is efficient for communicating with people who already share the same background — it compresses a lot of shared understanding into a short label. That efficiency is exactly what makes jargon dangerous for self-assessment: it's possible to string together correct-sounding technical terms without actually understanding the mechanism connecting them, because the vocabulary itself carries an appearance of understanding that the underlying explanation may not back up. Plain language removes that shortcut. Without technical terms to lean on, a real explanation has to describe the actual mechanism directly — and a fake or incomplete understanding is much harder to disguise as one, once the jargon that was hiding it is stripped away.
A worked example
Explaining "supply and demand" using economics vocabulary might produce something like: "Price equilibrium occurs where the supply curve intersects the demand curve." That's accurate but doesn't test understanding much — it's a memorized relationship stated in the field's own terms. A Feynman-style plain-language version: "If a thing gets too expensive, fewer people want to buy it, so sellers lower the price to attract buyers again; if it's cheap and lots of people want it, sellers raise the price because they can sell it for more and still find buyers. The price settles wherever roughly as many people want to buy at that price as sellers are willing to offer at that price." Writing that version out is what would expose, for instance, an unclear intuition about why sellers raise or lower prices in response to demand — a gap the technical version's ready-made vocabulary would have quietly covered up.
Where it fits alongside other study methods
The Feynman Technique pairs naturally with active recall (see the companion article on that topic) — explaining a concept from memory, without looking at notes, is itself a form of retrieval practice, with the added benefit of surfacing specifically where the gaps are rather than just confirming that a gap exists somewhere. It's most useful as a diagnostic step, run after initial learning and before an exam, to find precisely which parts of a topic need more attention — rather than as a primary way of first encountering new material, since it depends on already having some raw understanding to work with and simplify.