Loading
If you can't explain it, you don't understand it.
definition
Explaining a concept in simple language, in your own words, to reveal understanding gaps.
The Feynman technique is named after Richard Feynman, though he never formalized it under that name. It comes from observations of how he studied — he would write a concept at the top of a notebook page and then try to explain it as simply as possible, noting where his explanation became jargon-y, hand-wavy, or incoherent. Those points became his study targets.
The technique has four steps: (1) pick a concept, (2) explain it in plain language as if teaching a 12-year-old, (3) identify where you got stuck or reverted to jargon, (4) go back to the source and fix the specific gap. Repeat until the explanation flows.
The magic is in step 3. Most study methods let you gloss over gaps — you re-read the whole chapter and feel like you understood it. Feynman forces the gap to name itself. The exact place your explanation breaks down is the exact place your understanding fails.
Brainback's explain-back surface is the Feynman technique made continuous. You type your explanation of a concept, Haiku 4.5 grades it against a published rubric in under 900ms, and any explanation scored under 4/5 generates a recall card for that specific gap. The 'go back to the source' step happens automatically — the card returns in 1-3 days with the exact gap you missed.
Every design decision Brainback makes about the feynman technique flows from these papers. Cited so you can verify.
Students who spontaneously self-explained while studying worked examples learned significantly more than students who didn't. The specificity of the explanation mattered — vague self-talk had little effect; concrete step-by-step explanations produced large gains.
Middle-school students who explained biology diagrams as they studied showed better transfer to novel problems than students who studied without explanation. The explanation act — not just the exposure — produced the gain.
Meta-analysis of 44 studies. Self-explanation reliably improved learning across STEM and non-STEM domains. Effect held whether explanations were spoken, written, or typed.
The mechanism isn’t decorative. Understanding WHY the effect exists lets you tell when it applies and when it doesn’t.
The cognitive mechanism has two parts. First, generating an explanation forces the concept from recognition memory (where it might feel understood) into production memory (where it actually is). Second, the specific bottleneck in your explanation — the point where you stall or hand-wave — reveals a specific gap you wouldn't otherwise notice.
The neural correlate involves language-production areas of the frontal cortex working in concert with memory-retrieval areas of the hippocampus and neocortex. Recognition activates fewer areas; production activates more, and the co-activation strengthens the network. You're not just retrieving; you're integrating.
The 12-year-old framing is not decorative. Simple language forces you to bypass domain jargon. Jargon can hide a lack of understanding — you can say 'the mitochondrion produces ATP via oxidative phosphorylation' without knowing what 'oxidative' means in that context. Explaining it to a 12-year-old forces you to name the actual mechanism: 'the mitochondrion uses oxygen to gradually release the energy stored in food molecules, packaging it into ATP.'
Physics · why doesn't the moon fall to Earth.
You just finished a chapter on gravitation and orbital mechanics. You feel like you understand it.
You re-read the chapter summary. You highlight the equation for orbital velocity. You solve two practice problems. You feel confident. On the exam next week, you get the conceptual question wrong.
You try to explain to a 12-year-old why the moon doesn't fall to Earth. You get to 'gravity pulls it toward Earth but...' and stall. You realize you can state that the moon is 'always falling but also moving sideways' but you can't explain WHY that produces a stable orbit. The gap names itself. You go back to the source, find the specific paragraph on centripetal force balance, and fix the gap.
In 15 minutes, you've found the exact conceptual gap that would have cost you on the exam. The follow-up: explain it again. This time it flows. Card scheduled 3 days out. On exam day, the concept produces itself because you've explained it three times, not read the summary three times.
Explain-back is the Feynman technique made continuous. Pick a concept, write your explanation, get scored 0-5 against a published rubric. Scores under 4 generate a recall card for that specific gap. The 'go back to the source' step happens automatically — the card returns in 1-3 days with the exact gap you missed.
The method works everywhere. It works especially well in these three domains — for reasons specific to each.
Both disciplines have concepts that feel understood at the equation level but reveal gaps at the explanation level.
Pathway understanding is exactly what explain-back tests. 'Recite the citric acid cycle' vs. 'explain why cells that can't respire aerobically switch to fermentation.'
Argument reconstruction is a form of explanation. If you can't summarize an argument in plain language, you don't understand its structure.
Understanding what the method beats (and by how much) tells you when to reach for it.
why weaker · Zero forced production. You can re-read for hours and never notice the specific gaps in your understanding.
why weaker · Transcription, not synthesis. You can outline a chapter without ever integrating the concepts into your own framework.
why weaker · Passive reception. Watching someone else's explanation is not the same cognitive act as producing your own.
5-10 minutes per concept · aim for 2-3 concepts per study session. The steps below are the sustainable protocol — not a heroic one-off.
Pick a concept. Aim for your second-most-confident, not most-confident (gaps hide in over-confident concepts).
Open a blank page or Brainback's explain-back. Close the source.
Write the explanation in plain language. No jargon unless you also define it.
Stop the moment you stall, blank, or reach for jargon.
Note the specific gap. Look at the source ONLY at that point.
Try again from scratch. See if the gap is smaller.
Move on when the explanation flows without gaps. Card scheduled.
Feynman-ing only the concepts you're already comfortable with. The technique's value is highest on your second-most-confident concept — that's where the interesting gap lives. First-most-confident is boring; least-confident is discouraging.
Production forces the concept out of recognition memory (where it might feel understood) and into working memory (where it actually is). The bottleneck is language — if you can't find the words, you don't have the model.
It's writing with a scoring rubric that names your specific gap. Journaling about a concept produces the feeling of understanding; explain-back produces a diagnosis.
Aim for 4, not 5. Aiming for 5 makes you defensive; aiming for 4 makes you honest. A 4 with a gap named is more useful than a 5 without one.
Yes — the rubric is language-agnostic. Terminology drift across languages is annotated ('this concept is usually called X in English').
Yes — explain the algorithm, not the code. If you can't explain the algorithm without the code in front of you, you don't understand the algorithm.
Yes — same mechanism. But writing forces more precision; the friction is often where the gap lives.
→the feynman technique
Explain-back runs on every account, free tier included.