The Feynman Technique, Explained: Learn by Teaching
Richard Feynman won a Nobel Prize in physics, but he is remembered just as much for his teaching. He had a rare gift for taking ideas that normally require years of training — quantum mechanics, for instance — and explaining them so clearly that a curious teenager could follow along. The study method named after him tries to bottle that gift.
This guide walks through the Feynman Technique step by step: what it actually asks you to do, why explaining something reveals what you don't understand, where the method falls short, and how to fold it into real study sessions without turning every topic into a production.
Pick a concept, then explain it in plain language as if teaching a smart beginner — out loud or on paper, no jargon allowed. Every place you stumble, hedge, or reach for a technical term marks a gap in your understanding. Go back to your source material, fill those gaps, and explain it again until the explanation flows. The explanation is the test.
The four steps
Step one: choose a concept and study it first. The technique is not a way to learn something from nothing. Read the chapter, watch the lecture, or work through the material once so you have something to work with. Pick one concept at a time — a single idea like "how compound interest works" rather than an entire chapter on investing.
Step two: teach it in plain language. Explain the concept as if you were teaching it to someone intelligent but unfamiliar with the subject — a bright twelve-year-old is the classic image. Write it out or say it aloud. The critical rule: no jargon, no technical terms you can't unpack. If you catch yourself saying "photosynthesis converts light energy via chlorophyll," stop and explain what each of those words actually means.
Step three: find the gaps. This is the whole point. Notice exactly where your explanation gets shaky — where you wave your hands, repeat the textbook phrasing without understanding it, or realize you can't answer the obvious follow-up question your imaginary student would ask. Mark those spots. They are a precise map of what you don't actually know yet, which is far more useful than a vague feeling of confusion.
Step four: go back and simplify. Return to your source material with your list of gaps and fill them in. Then explain the concept again from scratch, aiming for an even simpler version. Analogies can help here — comparing an unfamiliar idea to a familiar one forces you to identify what really matters about it. Repeat until the explanation flows without strain.
Why explaining beats rereading
Most study feels productive without being productive. Rereading a chapter feels fluent because the author's organization does the work for you — your eyes glide over sentences your brain already half-remembers, and familiarity masquerades as understanding. Explaining strips away that scaffolding. You have to decide what comes first, what depends on what, and which details actually matter. That organizing work is where the learning happens.
Teaching also forces retrieval. When you explain from memory rather than from the page, you're pulling the idea out of your head and rebuilding it — and rebuilding is what strengthens the memory. A summary can be assembled by copying the source's structure; a genuine explanation has to be constructed from your own understanding, which is exactly why the gaps show up.
Finally, the no-jargon rule does real work. Technical vocabulary is useful shorthand among experts, but for a learner it can function as camouflage. Saying "the mitochondria is the powerhouse of the cell" sounds like knowledge while containing almost none. Forcing yourself to say what that actually means — in words a beginner would accept — reveals whether there's understanding behind the label.
Where the technique falls short
The Feynman Technique is a diagnostic tool, not a complete study system, and it has real limits. First, it's slow. A proper explain-it-simply pass on one concept can take twenty minutes, which makes it impractical as your only method when an exam covers forty concepts. Use it selectively, on the load-bearing ideas that unlock everything else.
Second, it's weak for sheer memorization. Vocabulary words, anatomical names, historical dates, and formulas don't yield much to explanation — they mostly need repeated retrieval practice. Feynman-style teaching helps you understand what a formula means, but it won't by itself make you recall it under pressure. Pair it with flashcards or practice problems for the memorizable parts.
Third, you can fool yourself even while teaching. It's possible to deliver a smooth-sounding explanation that still contains a subtle error or a skipped step, especially with no one there to ask the hard follow-up question. If you can, test your explanation on a real person — a study partner, a friend, even a rubber duck on your desk that you genuinely talk through it with. The questions they ask are the gaps you missed.
Making it practical
You don't need a classroom. Write your explanation on a single page, record a voice memo walking through it, or explain it to a friend over coffee. Writing has an advantage: the page doesn't let you mumble past the hard parts the way speaking sometimes does. But speaking has its own advantage — it keeps the explanation moving and exposes hesitation in real time. Either works; pick the one you'll actually do.
Reserve the full technique for concepts that matter most — the ones other ideas depend on. In a programming course, that might be how variables and functions actually work rather than the syntax of a specific library. In economics, it might be supply and demand rather than the details of one policy case. Twenty minutes spent truly understanding a foundational concept pays off across everything built on top of it.
And combine it with other methods rather than treating it as a replacement. A sensible weekly rhythm: learn new material, use the Feynman Technique on the two or three hardest concepts, then use spaced retrieval — flashcards, practice questions — to lock in the facts and procedures. Understanding and memory are partners; this technique handles the understanding half.
Frequently asked questions
Do I need to actually teach a real person?
No. Writing the explanation out or saying it aloud to an empty room captures most of the benefit, because the work is in constructing the explanation, not in having an audience. A real person adds useful pressure — their confused look tells you where you're unclear — but it's a bonus, not a requirement.
How is this different from just summarizing?
A summary usually follows the structure of the source: you compress each section in order. The Feynman Technique asks you to rebuild the idea from scratch in your own words and your own order, without leaning on the textbook's scaffolding. That rebuilding is what exposes gaps a summary would glide over.
Does it work for math and hands-on skills?
Partially. It's excellent for the concepts underneath the procedures — why an algorithm works, what a statistical test is actually telling you. It's weaker for the procedures themselves, which mostly improve through worked practice. Use explanation for the "why" and practice problems for the "how."
How long should each Feynman session take?
Fifteen to thirty minutes per concept is plenty. Think of it as a diagnostic check, not a production — you're probing for gaps, not writing a textbook chapter. If one concept takes over half an hour, it's probably two concepts bundled together; split it up.
Educational content only — not professional advice. Talk to a qualified professional about personal career or education decisions.