The Feynman Technique: How to Learn Anything by Teaching It

The physicist Richard Feynman was famous for explaining hard ideas in plain language. The study method named after him — the Feynman technique — rests on one simple test: if you can't explain it simply, you don't understand it yet.

It's one of the most useful techniques you can learn, because it does something rereading and highlighting can't: it shows you exactly where your understanding breaks. This guide covers the four steps, why it works, and how to stop fooling yourself while you do it.

Why explaining works

When you read an explanation, it makes sense. When you have to produce one yourself, you discover all the steps you were skipping.

Several lines of research support this:

• Self-explanation. In a classic study by Michelene Chi and colleagues (1994), students who were prompted to explain a biology text to themselves as they read it — on the circulatory system — understood it better than students who read it twice.
• Expecting to teach. Nestojko and colleagues (2014) found that students who studied a passage expecting to teach it recalled more, and organised what they recalled better, than students expecting a test.
• Actually teaching. Fiorella and Mayer (2013) found that students who went on to actually teach the material (by recording a short lesson) did better on a delayed test a week later than students who only prepared to teach.

Explaining forces you to organise ideas, connect them, and retrieve them from memory — all things that make learning stick.

The Feynman technique in 4 steps

Step 1: Choose one concept

Be specific. "Cell biology" is too big. "How the sodium–potassium pump keeps the resting membrane potential negative" is right. Write the name at the top of a page.

Step 2: Explain it to a beginner

Without looking at your notes, explain the concept — out loud, on paper, or into your phone — as if to a curious 12-year-old with no background. Rules:

• No jargon you haven't explained. If you say "electrochemical gradient", you have to say what that means.
• Explain the why, not just the what. "Sodium is pumped out" isn't an explanation. Why does it matter?
• Keep going until you've covered it all — or until you get stuck.

Step 3: Find the gaps and go back to the source

You'll hit places where you wave your hands, use a term you can't define, or simply don't know what comes next. Those are the gold. Mark them, then go back to the textbook or lecture for just those parts.

The hardest gaps to see are the ones you don't notice — ideas you left out entirely. That's why it helps to check your explanation against the source afterwards, idea by idea: what did the page say that you didn't?

Step 4: Simplify and use an analogy

Explain it again, shorter and plainer. Try an analogy ("the pump is like a bouncer letting three people out for every two let in"). If your explanation still needs the textbook's exact wording, you've memorised it, not understood it.

Common mistakes

• Explaining with notes open. That's reading aloud, not explaining. Close everything.
• Being too generous with yourself. "I basically know this" is how gaps survive. If you hesitated, it's a gap.
• Skipping the check. Without comparing to the source, you won't notice what you left out.
• Never asking "what if…?" Once you can explain the normal case, push further: what would happen if the pump stopped? Exams love these questions.
• Using it for everything. It's slow. Save it for concepts and processes; use practice questions and spaced repetition for straightforward facts.

Teach it back in DeepRevision

DeepRevision has the Feynman technique built in as Teach it back. Pick an answer from PinPoint (DeepRevision's AI tutor), a section of your study plan, or a moment from a recorded lecture, and explain it in your own words — typed or out loud.

• Your explanation is checked idea by idea against your own pages, so you see exactly which ideas you covered and which you missed. Every hint links to the page it came from.
• A curious beginner asks "why?" about the gaps — and never gives you the answer. You have to work it out.
• Once you've covered every idea, a harder audience asks "what would happen if…" questions to test whether you can apply it.
• The ideas you missed can be turned into practice questions in one tap, so they come back for review.

Over time, DeepRevision plots each topic by two things — how many of its questions you get right, and how much of it you can explain — so you can spot topics you've memorised but don't understand, and the reverse.

When to use the Feynman technique

A good rhythm: learn a topic, practise questions on it, then teach it back. The questions tell you what you get wrong; teaching it back tells you why.