Concepts
Apprentissage Pédagogie

The Feynman Technique

Origin : Richard Feynman, ~1950

To truly understand something, try to explain it simply. The gaps in your explanation reveal the gaps in your understanding.

To truly understand something, try to explain it to someone who knows nothing about it. Where you get stuck, where you fall back on jargon, where your explanation turns fuzzy — that is where your understanding has a gap.


Origin

Richard Feynman (1918–1988) was a theoretical physicist, winner of the 1965 Nobel Prize in Physics for his work on quantum electrodynamics. He was famous for something almost as rare as his genius: his ability to explain concepts of extreme complexity in a simple and accessible way.

The “Feynman Technique” is not something he wrote — it is a synthesis of his pedagogical approach, as it comes through in his lectures at Caltech (recorded between 1961 and 1963) and in his memoirs. The quote often attributed to him — “If you can’t explain it simply, you don’t understand it well enough” — captures the essence of his method.


The Theory

The technique unfolds in four steps:

  1. Choose a concept you want to understand.
  2. Explain it as if you were talking to a child — no jargon, no technical terms, with concrete examples.
  3. Identify where you get stuck — where you use jargon because you cannot explain it any other way, where you have to go back to your notes, where the explanation becomes fuzzy.
  4. Go back to the source — fill the gaps, rewrite the explanation in simpler terms.

The underlying principle is that explanation forces structure. What is fuzzy in your head becomes obvious when you try to put it into accessible words. Jargon is often a cover: it allows you to talk about a subject without truly understanding it.


In Practice

The technique is particularly powerful in active learning contexts — learning by doing, learning by teaching, learning by writing.

Writing and publishing: Every article that explains a concept is a forced Feynman session. The constraint of making something understandable to someone who doesn’t know it reveals the blind spots in your own understanding.

Rubber duck debugging: In software development, explaining your code to a rubber duck (or a colleague) before asking for help. Verbalizing forces structure, and often the bug appears during the explanation.

Preparing a talk: Explaining a subject aloud, without notes, to a non-specialist, reveals within minutes what you truly master and what you merely believe you master.

The technique connects with the Curse of Knowledge: the more expert you are, the more you forget what it was like not to know. Feynman solved this problem by constantly forcing himself back to the beginner’s level.


Nuances and Limits

The Feynman Technique is not a shortcut — it is often longer than passive methods (reading, re-reading, highlighting). It demands active effort and, often, humility: accepting that you might discover you do not understand as well as you thought.

It is less suited to memorizing facts than to understanding concepts. For lists, dates, and formulas, other methods (spaced repetition, flashcards) are more effective.

The “child” level is a guide, not an absolute constraint. The goal is simplicity and clarity, not triviality. Some concepts have irreducible complexity — the technique helps identify which part of that complexity is necessary and which part is noise.

Sources: Feynman, R. (1985). “Surely You’re Joking, Mr. Feynman!” · Feynman Lectures on Physics, Caltech 1961–1963 · Feynman Technique — Farnam Street

Concepts