There's a brutal little test for whether you actually understand something: try explaining it to someone who knows nothing about it, using no jargon. Most of us discover, about two sentences in, that what felt like understanding was really just familiarity with the words.
The Feynman technique builds a study method around that test. You pick a concept, explain it in the simplest language you can manage, watch where the explanation breaks down, and go back to the source to repair exactly those spots. Then you simplify again. The cycle continues until your explanation holds up.
It's named after Richard Feynman, the Nobel Prize-winning physicist famous for making hard ideas feel obvious. The four-step version taught today is an adaptation of how he worked, and it's one of the fastest ways to convert shaky, exam-vulnerable knowledge into the kind you can use under pressure.
Where the technique comes from
Richard Feynman (1918–1988) won the 1965 Nobel Prize in Physics for his work on quantum electrodynamics, but his second reputation was as a teacher — colleagues and students knew him for explaining deep physics in plain, vivid language, without hiding behind abstraction or jargon.
Feynman didn't publish a study method. The 'Feynman technique' as a named, four-step process was distilled later by writers and educators — notably the Farnam Street blog — based on how Feynman approached learning and explaining. The packaging is modern; the underlying idea, that the ability to explain simply is the measure of understanding, is pure Feynman.
The four steps
The whole method fits on an index card. The discipline is in doing each step honestly.
- 1. Pick a concept and write it at the top of a blank page. One concept — 'opportunity cost', 'osmosis', 'the chain rule' — not a whole chapter.
- 2. Explain it as if teaching a child. Write or say the explanation in the simplest words you can, with examples and analogies. No jargon allowed: every technical term you lean on is a place you might be hiding from yourself.
- 3. Identify the gaps and go back to the source. Wherever you hesitated, waffled, or quietly skipped a step — that's a gap. Return to your notes or textbook and relearn exactly that piece.
- 4. Simplify and retell. Rewrite the explanation, tightening the language and the analogies, until it flows from start to finish. If you can, deliver it to a real person and let their questions probe it.
Why explaining works
The technique stacks several evidence-backed mechanisms into one exercise. Producing an explanation from memory is a form of retrieval practice — you're pulling the idea out of your head rather than re-reading it. Translating it into simple language forces elaboration: you have to connect the concept to things you already understand, which is how durable knowledge is built.
Most importantly, it destroys the illusion of knowing. Rereading makes material feel familiar, and familiarity masquerades as understanding. An explanation has nowhere to hide: either the causal chain comes out of your mouth in order, or it doesn't. The technique converts vague anxiety ('I think I know this chapter?') into a precise repair list ('I can't explain why step two follows from step one').
A quick worked example
Say you're studying biology and pick osmosis. Attempt one: 'Osmosis is when water moves across a semipermeable membrane from low solute concentration to high solute concentration.' Fine — but a twelve-year-old would ask why, and if your honest answer is 'it just does', you've found your gap.
Back to the textbook, then attempt two: 'Imagine a room divided by a screen with tiny holes. Water molecules fit through the holes; sugar molecules don't. Molecules bounce around randomly, so water passes both ways — but on the sugary side, sugar gets in the way of water reaching the holes, so less water leaves that side than enters it. The result looks like water flowing toward the sugary side.' Now the mechanism is yours, not the textbook's — and an exam question phrased in an unfamiliar way can't knock it loose.
Common mistakes (and when not to use it)
The technique fails quietly when you let yourself perform understanding instead of testing it.
- Explaining with the book open. That's paraphrasing, not retrieval. Close the source for step two; it only reopens at step three.
- Smuggling in jargon. Saying 'it works via electrochemical gradients' isn't an explanation unless you can also explain what a gradient is. Define every term or don't use it.
- Stopping after one pass. The loop — explain, find gaps, repair, re-explain — is the method. One attempt just generates the to-do list.
- Using it for everything. Pure memorization work (vocabulary, anatomy labels, dates) doesn't benefit much; flashcards and spaced repetition handle those better. Save Feynman for concepts, mechanisms, and anything you'll need to apply or discuss.
- Writing essays instead of explanations. Keep it short and spoken in register. If it doesn't sound like something you'd say out loud, simplify.
Put it into practice
Doing this with PocketNote
Step four of the technique wants an audience that asks awkward questions — and that's something PocketNote's source-grounded chat does well. Explain a concept in your own words, then ask the chat to check your explanation against your actual lecture notes or textbook PDF: it can flag what you got wrong or left out, with the relevant passage to hand.
For the repair step, generate a quick quiz on just the topic where your explanation collapsed, and re-test a few days later. The explain-repair-retest loop runs entirely inside the material your course actually uses.
Frequently asked questions
Sources
Keep reading