Feynman Technique: Explain It Simply, Then Restudy the Gaps

Rereading feels like work. You can highlight a chapter and still freeze when someone asks you to say it without the page.

That freeze is information. It usually means the idea is still a string of terms, not a chain you can run. The Feynman Technique turns that freeze into a restudy list instead of a vague “study more.”

The Feynman Technique is a four-stage learning loop associated with physicist Richard Feynman: choose a concept, explain it as if to a beginner, notice gaps, then simplify and return to the source. Production teaching contrasts passive input with active output. The “explain it to a child” prompt is a simplicity test. You do not need an actual child.

The method does not grade teaching skill. It grades whether your explanation still needs the textbook’s sentences to stand up.

1. Choose a concept

Name one bounded idea (how a hash map handles collisions, not “computer science”). Study enough to attempt an explanation.

2. Explain in simple language

Write or speak the idea in your own words. Use an analogy only if you can still state the mechanism. When you reach for a term you cannot unpack, mark it.

3. Review gaps

Stuck, skipped steps, and disconnected parts are the product. That edge is where restudy starts.

4. Simplify and restudy

Go back to the source for those holes. Rewrite until the chain holds without empty jargon. Repeat. Simplifying is not deleting the idea until nothing remains.

When another lens fits better, or when you need a complementary view, these frameworks do different jobs. They are not interchangeable labels for the same question.

The Feynman Technique is the lens for testing a concept by explaining it. Other methods help when the question is practice, acquisition sequence, difficulty zone, notes, or reading.

• Checking a hard idea. You have read it and cannot say it.
• Turning a failed explanation into a restudy list. You know you are stuck but not where.
• Preparing to teach or write. You need a plain-language version that still keeps the mechanism.

Example: Recursion that still sounds like a slogan

A developer has read three articles on recursion. In a huddle they say “a function that calls itself” and then cannot explain the base case or the call stack.

They pick recursion with a base case as the concept. The first explanation dies at “it keeps going until it stops.” That sentence is the gap.

They restudy a short trace of factorial: n equals 1 returns 1, otherwise n times factorial of n minus 1, and what the stack holds. The second explanation walks that trace without the slogan.

Implication: The output is a repaired explanation plus a named hole that was fixed. It is not a claim they are now an expert.

What the Feynman Technique can help with

• Testing conceptual understanding with an explanation
• Naming specific gaps instead of “I don’t get it”
• Rewriting an idea in plain language without dropping the mechanism
• Preparing a teachable or writable version of one concept

What the Feynman Technique cannot replace

• Deliberate Practice. Coached rehearsal of a skill. Feynman tests a concept; it does not run a practice schedule.
• Simon Learning Method. A broader acquisition approach on this site. Not the same as explain-and-gap.
• Three Zones of Learning. Comfort, stretch, and panic. Zones set difficulty. Feynman tests a named idea.
• Cornell notes or SQ3R. They structure reading and notes. Feynman tests output.
• Labs, feedback from a teacher, or spaced practice. An explanation can still be wrong in a way you cannot see alone.

Honest scope: Feynman structures an understanding test. It should not be sold as the best way to learn anything.