The Technique Named After a Nobel Physicist’s Study Habits
Richard Feynman wasn’t just a brilliant physicist — he was famous among colleagues for insisting he didn’t really understand something until he could explain it in plain language to someone with no background in the subject. That habit became a formal learning method: pick a concept, explain it as if teaching it to a curious ten-year-old, and pay close attention to exactly where you stumble, reach for jargon, or go vague. Those stumbling points aren’t awkward moments to smooth over — they’re a precise map of what you don’t actually understand yet, dressed up until now as things you merely couldn’t explain well.
Why Explaining Beats Re-Reading
Most studying is recognition-based: you re-read a chapter, nod along because it sounds familiar, and mistake familiarity for mastery. Explaining out loud forces retrieval and reconstruction, which is a fundamentally harder cognitive task than recognition — and that difficulty is the point. You can’t gloss over a gap in understanding while speaking in simple sentences the way you can while silently re-reading a paragraph you’ve seen three times already. The moment you hit “and that happens because… uh,” you’ve found the exact edge of your knowledge, which is far more useful than another hour of passive review.
The Four-Step Version You Can Use Today
Step one: write the concept’s name at the top of a blank page. Step two: explain it underneath in plain language, as if to someone who has never heard of it, avoiding technical terms entirely — if you must use one, define it immediately in simpler words. Step three: when you get stuck, that’s not a failure, it’s the data — go back to the source material and fill only that specific gap. Step four: once your explanation reads cleanly, go through it again and simplify further, replacing any remaining jargon or awkward phrasing with an analogy a non-expert would actually grasp.
Where It Works Best
The Feynman Technique shines hardest on conceptual material — the “why” behind something, not just the “what.” It’s less useful for pure memorization (vocabulary lists, dates) and extremely useful for anything with underlying mechanisms: how compound interest actually compounds, why a programming loop terminates, how a negotiation tactic works psychologically. Try it on one thing you “already know” this week — a concept from your job, a hobby, or something you learned in school — and notice how often the explanation reveals a gap you didn’t know was there.
