The Feynman Technique: The Study Method Top Premeds and CS Students Swear By

A junior at Johns Hopkins once told me she'd spent two weeks rereading her biochem notes for an exam she still bombed. Forty-eight pages of yellow highlighter. Three lecture rewatches. A perfect Notion database. She got a 71. Then, panicking before the retake, she taped a printout of the citric acid cycle to her dorm wall and tried to explain it out loud to her roommate. A film major who'd never opened a science textbook. Halfway through "so the acetyl-CoA, um, joins with…" she stopped cold. She thought she knew. She didn't. The feynman technique studying method, which she stumbled into that night, walked her to an 89 on the retake. This post is the deep version of what she figured out the hard way. We'll cover the four-step method as Richard Feynman built it at Princeton and Caltech, the cognitive science explaining why it beats highlighting and rereading (citations from Roediger, Karpicke, and Dunlosky), and concrete examples by major. Premed, CS, physics, history. You'll know when to use it, when to skip it, and how to pair it with active recall.

Who Was Richard Feynman, and Why His Method Still Beats Highlighters

Richard Phillips Feynman (1918–1988) shared the 1965 Nobel Prize in Physics with Schwinger and Tomonaga for quantum electrodynamics. He spent most of his career at Caltech, where in 1961 he redesigned the intro physics sequence. The result, The Feynman Lectures on Physics, has sold over 1.5 million sets in English. Bill Gates called him "the best teacher I never had" and funded Project Tuva to put Feynman's Messenger Lectures online for free. Caltech still awards the Richard P. Feynman Prize for Excellence in Teaching annually.

Here's the part most study guides skip. Feynman wasn't a born explainer. He built the habit. At Princeton, before his oral qualifying exam, he walked over to MIT, opened a fresh notebook, and wrote on the title page: Notebook Of Things I Don't Know About. The feynman technique studying habit is built on that same idea: an honest, written audit of what you actually don't know, separate from what you've merely seen before. The highlighter, by contrast, lets you feel productive while flagging your ignorance in pretty colors.

The Four Steps, Exactly as Feynman Used Them

Step 1: Pick one concept. Write it at the top of a blank page. Not a topic, a concept. "Glycolysis" is a topic. "Why glycolysis nets 2 ATP even though 4 are made" is a concept. If you can't name what you're learning in one sentence, you're not ready to study it.

Step 2: Explain it in plain language, as if teaching a curious 12-year-old. Out loud, on paper, or to a real human. No jargon, no hand-waving, no "as we know from chapter 4." If the only way you can describe NADH is "a coenzyme involved in redox reactions," you're parroting. A 12-year-old needs "a tiny shuttle that picks up electrons in one part of the cell and drops them off in another, like a delivery driver."

Step 3: Find the cracks. Where did you stall? Where did you reach for the textbook? Mark those spots in red. Those are your study targets. Not the whole chapter, just the cracks. Go back to the source (lecture notes, textbook, 3Blue1Brown, Khan Academy) and patch them.

Step 4: Simplify and add an analogy. Rewrite shorter, with one good analogy that captures the mechanism. Test it on someone who doesn't know the material. Their first question is your next study target. Repeat until the explanation flows in under two minutes.

What the Cognitive Science Actually Says

Two camps of research back the method. Roediger and Karpicke's 2011 study in Science showed that students who practiced retrieval outperformed students who built elaborate concept maps by roughly 50% on delayed tests a week later. That upended a decade of advice about "elaborative" study. The feynman technique studying loop forces retrieval at step 2: you can't explain what you can't pull from memory.

The second camp is Dunlosky's 2013 meta-analysis in Psychological Science in the Public Interest, which ranked ten study techniques. Practice testing and distributed practice landed in "high utility." Highlighting, rereading, and summarizing landed in "low utility." Elaborative interrogation. Asking why a fact is true and generating the explanation. Landed in "moderate utility" and works best when you have background knowledge. Feynman is retrieval practice plus elaborative interrogation glued together, which is why it punches above either ingredient alone. Not magic. Just good cognitive design.

Feynman Technique Studying for Premeds: Anatomy and Biochem

Anatomy is the classic target because the temptation to memorize 200 muscle origins without understanding function is overwhelming. The smarter move: pick one functional unit (the rotator cuff), then explain why four muscles instead of one, what each one stops the shoulder from doing, and what tears when a quarterback throws wrong. If you can't say why supraspinatus tears more than the other three (it's pinched under the acromion during overhead motion), you've memorized a list, not learned anatomy. Med School Insiders recommends this for neuroanatomy especially.

Biochem is where the method earns its keep. The MCAT tests pathway logic, not whether you can recite intermediates. Try this: explain glycolysis under aerobic versus anaerobic conditions using only kitchen analogies. If you say "the NADH gets shuttled to the mitochondria" without being able to say why (the inner membrane is impermeable to NADH, so the malate-aspartate or glycerol-3-phosphate shuttle moves the reducing equivalents across). That's your crack. Patch it. UWorld's MCAT biochem question banks are a built-in step 3 detector.

CS Majors: Algorithms and Data Structures the Feynman Way

CS students at MIT, Berkeley, and CMU have a particular problem: LeetCode pattern-matching trains you to solve problems without understanding why the solution works. Then a slightly different prompt shows up in the technical interview and you freeze. The fix is brutal but effective. Pick Dijkstra's. Close the laptop. Explain on paper why it fails on graphs with negative edges, why Bellman-Ford handles that case at runtime cost, and where the priority queue lives. If you stumble, open CLRS to chapter 24 and patch it.

Data structures work the same way. Anyone can recite that a hash map is O(1) average. Far fewer can explain why it degrades to O(n) when too many keys collide, and how Java's HashMap switched to a red-black tree at 8 collisions per bucket to bound the worst case. The feynman test: can you draw the collision, explain the tree, and tell me the load factor where Java triggers the rebuild? If yes, you'll crush system design. If no, you've got a LeetCode habit, not a CS education.

Physics, History, and Why the Method Works for Humanities Too

Intro physics students confuse calculation with comprehension constantly. You can solve a projectile motion problem by plugging into kinematic equations without grasping that the horizontal and vertical components are independent. Which is the whole point. Feynman built the Caltech lectures around explaining why before computing. Try this: explain to a 12-year-old why a bullet fired horizontally and a bullet dropped from the same height hit the ground at the same time. If you can't, every problem you "solve" is a coin flip. Walter Lewin's MIT 8.01 lectures on OCW model this beautifully.

History majors get an unexpected boost. Memorizing dates is the trap; explaining causation is the exam. Pick the 1956 Suez Crisis and explain why a canal in Egypt nearly triggered a nuclear standoff. You'll quickly notice you don't fully grasp the British post-imperial economy, Cold War alignment, or why Eisenhower sided against his own allies. Those are your study targets. The same applies to political theory, econ, even literary criticism. The method scales.

When to Skip the Feynman Method (Honest Take)

The technique is not a universal hammer. Honest take: don't waste it on raw memorization where there's no underlying logic. French verb endings, the first 20 elements, the bones of the hand. Spaced repetition with Anki crushes those faster. Reserve Feynman for concepts with mechanism, causation, or interlocking parts. Pharmacology, pathophysiology, algorithms, orgo, macro models, constitutional law. Yes. Vocab lists. No.

Two more cases to skip it. First, under 48 hours from an exam, do not start. The method surfaces gaps you can't patch in time. Second, with zero prior exposure, do a first-pass read or lecture before attempting step 2. Dunlosky's research is explicit that elaborative interrogation needs some background knowledge. Otherwise you're not teaching, you're inventing.

Putting the Feynman Technique Studying Loop on Repeat

The move that separates students who use the method once from students who retain a semester's worth of material: build a "Notebook of Things I Don't Know" like Feynman did, but make it a living doc. Every concept you Feynman gets a line with the date. Revisit at 24 hours, 3 days, 7 days, 21 days. If the re-explanation takes more than 5 minutes, the concept needs another full session. Pair this with Anki for the factual layer and you've got the closest thing to a guaranteed retention system cognitive psychology has produced. The feynman technique studying habit compounds when you treat it as a verb, not a one-time stunt.

Frequently Asked Questions

How long does one Feynman session actually take? Plan for 30 to 45 minutes per concept the first time. Step 1 takes 2 minutes, step 2 takes 10 to 15, step 3 (patching cracks) is the longest at 15 to 20, step 4 takes 5 to 10. By week three, most students cut to 20 minutes per concept. Don't try more than four concepts a day; cognitive fatigue tanks step 3.

Is the Feynman technique better than active recall with flashcards? They're complementary, not competing. Anki is unbeatable for discrete facts. Drug names, landmarks, vocabulary. Feynman is unbeatable for systems. Pathways, algorithms, causal chains. Premeds use both: Anki for thousands of MCAT cards, Feynman for the 15 or so biochem pathways where mechanism matters.

Can I do the Feynman technique alone, without anyone to teach? Yes, and most students do. Talk out loud to an empty room, record a voice memo, or write it as a Reddit r/explainlikeimfive post. The recording trick is underrated. Playing it back the next day surfaces phrases that sounded smart but meant nothing. Explaining to a real human is still 20% more effective because their confused face is a faster gap-detector than your own.

Does the Feynman method work for the MCAT specifically? Especially well for biochemistry, psych/soc, and CARS-adjacent reasoning. Khan Academy's MCAT content is built for it. Short videos that teach mechanism, followed by passages that test whether you got it. Use Feynman for the 30 to 40 biochem pathways and signal cascades that recur, plus cardiac and renal physiology. AAMC's practice exams are your step-3 crack detector.

How is Feynman different from summarizing my notes? Summarization compresses what's already there. Feynman forces you to generate an explanation from memory. A fundamentally different cognitive operation. Dunlosky rated summarization as low utility partly because you can paraphrase without understanding. You cannot fake step 2. Summarizing lets you hide; Feynman makes you honest.

What if I'm an introvert and hate "teaching" out loud? Write it. Open a blank doc, set a 15-minute timer, and type the explanation as if writing a tutorial for a younger sibling. The writing version keeps about 80% of the benefit because the constraints still apply. Bonus: re-read it a week later as a built-in spaced review. Plenty of CS students build Notion vaults of Feynman write-ups and crush interviews.

Can I use ChatGPT or Claude as my imaginary 12-year-old? Carefully, yes. Prompt: "Act as a curious 12-year-old who doesn't know any biology. Ask follow-up questions whenever my explanation uses a word a 12-year-old wouldn't know." The model will hammer you with "but what does enzyme mean?" questions that surface jargon. The risk: it sometimes accepts a wrong explanation if it sounds confident. Verify against your textbook before locking it in.