The Feynman Technique: Learn by Explaining

You have probably had this experience: you read a chapter, it all makes sense, and then someone asks you a simple question about it and you can't answer. Reading made the material feel familiar. It didn't make it yours.

The Feynman technique is a simple way to close that gap. You learn a topic by trying to explain it in plain words, noticing where the explanation breaks down, and going back to fix exactly those parts. It works for school subjects, technical concepts, interview topics — anything you need to understand rather than just recognise.

Where the name comes from

The technique is named after Richard Feynman, the physicist who shared the 1965 Nobel Prize in Physics and was well known for explaining difficult ideas in plain language, most famously in his lectures to undergraduates. The tidy four-step version people use today is a later summary of that approach by writers on learning, not a method Feynman published under that name. That doesn't make it less useful — it just means you should treat it as a practical routine, not a formula with a pedigree.

Why explaining works

When you re-read notes, you are mostly recognising information: "yes, I've seen this." When you explain, you have to retrieve it and put it in order yourself. Retrieval is harder, and that difficulty is useful — it shows you immediately what you can and can't do without the page in front of you.

Explaining also exposes a common blind spot. People tend to believe they understand how everyday things work in more detail than they really do. The psychologists Leonid Rozenblit and Frank Keil named this the illusion of explanatory depth in a 2002 paper: when asked to actually explain how something works, step by step, people rated their own understanding lower than before they tried. Trying to explain is what reveals the gap.

The four steps

Step 1: Choose a concept and write down what you know

Pick one specific concept — not "economics", but "why prices rise when interest rates are low". Write the name at the top of a page, or say it out loud, and note what you already know about it.

Step 2: Explain it simply, as if to a beginner

Explain the concept in plain language to an imaginary listener who is smart but new to the subject — a younger cousin, a friend from a different field. Avoid jargon. If you must use a technical term, define it.

This step works best out loud. On paper, it is easy to write a technical-sounding sentence that hides a gap. When you speak, you hear yourself hesitate, repeat, or say "and then it sort of…", and that is exactly where the gap is.

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

Wherever you got stuck, went vague, or reached for a fancy word you couldn't unpack, go back to your textbook, notes or a good explainer. Study just those parts. You are not re-reading the whole chapter — you are filling specific holes.

Step 4: Simplify and use an analogy

Explain it again, start to finish. This time, aim for shorter sentences and at least one analogy or concrete example. If the second explanation is clear from beginning to end, you understand it well enough to use it. If not, repeat steps 3 and 4.

How to spot a gap

The gaps are rarely silent. They show up in how you speak:

Worked example 1: inflation

First attempt (out loud): "Inflation is when prices go up. It happens because there's too much money, basically, and the RBI controls it with interest rates."

Gaps found: "too much money" — compared to what? And how do interest rates control it? The "basically" is hiding the mechanism.

Back to the source: you read how higher interest rates make borrowing more expensive, so people and businesses borrow and spend less, which reduces demand for goods.

Second attempt: "Inflation means that, over time, the same money buys less — a ₹100 note buys fewer things than it used to. One cause is demand rising faster than the goods available. The Reserve Bank of India can raise interest rates to cool that down: loans get more expensive, people borrow and spend less, and demand eases. Think of it like a crowded shop where everyone wants the same few items — prices go up until fewer people are trying to buy."

The second version has a definition, a mechanism, a who-does-what, and an analogy. That is the difference you are aiming for.

Worked example 2: a technical concept

The same steps work for technical topics, where it is especially easy to hide behind vocabulary. Try explaining how JavaScript runs asynchronous code. A first attempt often sounds like: "It uses the event loop, and callbacks go into the queue, and then they run." Each noun there is a label. Can you say when a callback runs, and why a setTimeout of zero milliseconds doesn't run immediately?

If not, that is your gap. Our explainer on the JavaScript event loop is a good source for step 3; then explain it again, out loud, with an example of what prints first.

Mistakes to avoid

• Simplifying until it's wrong. "Simple" means clear, not inaccurate. If your analogy breaks an important rule of the real thing, say where the analogy stops working.
• Skipping step 3. The value is in going back to the source for the exact gaps. Explaining the same gap three times doesn't fill it.
• Only explaining what you already know well. It feels good and teaches little. Pick the topics that make you uncomfortable.
• Doing it all in your head. Silent explanations skip over the stumbles. Say it, or at least write it in full sentences.
• Making it too long. A two- to five-minute explanation of one concept is better than a 30-minute lecture on a whole chapter.

Ways to use it

• Exam revision. After each chapter, explain its two or three key ideas out loud without notes. The parts you can't explain are your revision list.
• Viva and technical interviews. Interviewers often ask "can you explain how this works?" Practising out loud means you have already found and fixed the gaps.
• Learning at work. New to a codebase, a process, or a domain? Explain it to a teammate — or to yourself — before you rely on it.
• Study groups. Take turns explaining a concept while others ask "why?" after each step.

If you take notes while studying, handwritten notes work well as the source for step 3 — but close them before you explain.

Making it a daily habit

The Feynman technique is most powerful when you use it often, on many topics. A good daily rhythm is: one concept, a short period of reading, a two- to five-minute spoken explanation, then a quick read of what you said to find the vague parts.

Daily Talk is built around this rhythm. It gives you one topic a day and up to an hour to research it, then you explain it out loud for 1 to 10 minutes. Your notes aren't shown while you record, so you explain from memory, and afterwards you get a transcript to read back and spot where your explanation got vague. It runs in your browser, the audio is never uploaded, and transcription is English for now. If you want a fuller routine around it, see our 10-minute daily speaking practice method.

Frequently asked questions

Is the Feynman technique only for science?

No. It works for any topic you need to understand: history, economics, law, programming, or a process at work. Subjects full of jargon benefit most, because jargon makes it easy to sound right while understanding little.

Do I need someone to explain to?

No. An imaginary listener works, and so does recording yourself. A real listener who asks "why?" is a bonus, not a requirement.

How is this different from making notes?

Notes record information; the Feynman technique tests whether you can use it. Many people do both: make notes while studying, then close them and explain the topic to find what didn't stick.

How long should an explanation be?

Short enough to stay focused on one concept — usually two to five minutes out loud. If it runs much longer, you are probably covering several concepts; split them.