If you can't explain it simply, you don't understand it well enough. The Feynman Technique turns that maxim into a method: choose a concept, explain it in plain language as if to a novice, identify where you falter or resort to jargon, fill those gaps (by study or simplification), and repeat until the explanation holds without hand-waving. The technique is named after Richard Feynman, the physicist and Nobel laureate who was famous for demanding that ideas be expressible in clear, concrete terms — and for uncovering his own confusion by trying to explain.
The mechanism is feedback from the act of teaching. When you explain aloud or on paper, you force retrieval and reconstruction. Gaps show up immediately: you stumble, you use a term you can't define, or you realise you're paraphrasing a formula without understanding what it means. That feedback is a diagnostic. The places where explanation fails are the places where understanding is shallow. Re-studying those spots — or finding a simpler frame that actually fits your mental model — deepens understanding. The technique is a form of desirable difficulty: explaining is harder than re-reading, and it produces better retention and transfer.
The technique works for any domain: technical concepts, business models, strategy, or processes. The "audience" can be imaginary (a smart 12-year-old, a colleague from another function) or real (a study partner, a write-up for internal docs). The constraint of simplicity is the engine: it forces you to strip away jargon and surface the structure. If you can only say "it's like the standard model but with X," you haven't yet reached the level where you could teach it. When you can build the idea from everyday language and minimal assumptions, you've reached a testable level of understanding.
In understanding and analysing: use the technique to stress-test your grasp of a topic before a decision or presentation. If you're building strategy, explain the logic in Feynman style — the gaps will be the weak links in the argument. If you're evaluating an investment or a technical design, requiring a one-page plain-language explanation will expose what you're assuming without understanding.
Section 2
How to See It
The Feynman Technique appears whenever someone uses explanation — especially simple, novice-directed explanation — as a test and driver of understanding. Look for: teaching or writing as a deliberate check, simplification as a constraint, and iteration when the explanation fails.
Learning
You're seeing Feynman Technique when a student writes a one-paragraph explanation of a concept without using textbook language, then compares it to the source and revises where they were wrong or vague. The act of explaining is the test; the gaps are the study guide.
Performance
You're seeing Feynman Technique when an expert is asked to explain their domain to a non-expert audience and uses that as a discipline to strip jargon and check logic. The constraint of "no insider terms" forces clarification and often reveals edge cases they hadn't articulated.
Understanding
You're seeing Feynman Technique when a team prepares a strategy doc by first requiring a one-pager that a new hire could follow. The process of writing the one-pager exposes fuzzy thinking and missing steps. The full doc is then built on a foundation that has passed the simplicity test.
Analyzing
You're seeing Feynman Technique when an analyst summarises a complex model or deal in plain language before presenting. Where they can't simplify without losing meaning, they flag uncertainty or dig deeper. The technique is a validity check on the analysis.
Section 3
How to Use It
Decision filter
"Before committing to a position or presenting a view, can I explain it in simple language without jargon? If I can't, or I stumble over a part, that's the place to study or simplify. Use explanation as a test; use the gaps as a syllabus."
As a founder
Use the technique on your own pitch, strategy, and product logic. Write a one-pager that explains the business or the key decision as if to a smart outsider. Where you resort to buzzwords or hand-waving, you don't have clarity yet. Fix those spots before the board meeting or the all-hands. The technique also works for technical or operational concepts you need to own: explain the system or the metric in plain language until it holds.
As an investor
Apply the technique to theses and due diligence. Can you explain why this company wins in two paragraphs without jargon? Can you explain the key risk in one sentence? If not, your conviction is not yet grounded. Use the technique to stress-test your understanding before writing the check — and to communicate the thesis clearly to partners and LPs.
As a decision-maker
Require plain-language explanations as a gate for important decisions. "Explain it so a new team member can follow" is a useful standard. The act of producing that explanation will surface missing logic, undefined terms, and unchallenged assumptions. Use the technique as a quality check on analysis and strategy.
Common misapplication: Mistaking verbosity for depth. The technique demands simplicity, not length. A long explanation full of jargon is the opposite of Feynman — the goal is to compress and clarify until the structure is visible.
Second misapplication: Stopping at the first smooth explanation. The first pass often sounds good but hides gaps. Iterate: try explaining to a different audience, or from a different angle. The places where the explanation breaks are the places where understanding is still shallow.
Feynman insisted on understanding by derivation and explanation. He would rework a topic until he could build it from first principles and explain it in clear language. His lectures and books are full of "let's see why" and "in other words" — the technique in action. His view: if you can't explain it, you don't own it.
Musk pushes teams to explain complex systems in first-principles and plain language. His "physics-based" framing — strip away analogy and convention, reason from fundamentals — aligns with the Feynman idea that explanation and simplification are tests of understanding. Requiring that explanations pass a simplicity bar surfaces hidden assumptions and gaps.
Section 6
Visual Explanation
Feynman Technique: choose concept → explain simply (as to novice) → find gaps (stumble, jargon) → fill gaps / simplify → repeat until explanation holds. Explanation is both test and driver of understanding.
Section 7
Connected Models
The Feynman Technique sits among models about understanding, communication, and learning. The connections below show what reinforces it, what tensions exist, and what it leads to.
Reinforces
[Active Recall](/mental-models/active-recall)
Active recall is retrieving information rather than re-reading it. Explaining is a form of recall — you're retrieving and reconstructing. The Feynman Technique uses explanation as the recall task and adds the constraint of simplicity, which forces deeper processing.
Reinforces
First Principles Thinking
First principles thinking is breaking a problem down to fundamentals and building up. The Feynman Technique does the same for understanding: strip to the structure, explain from there. Both reject "because that's how it's done" in favour of derivation and clarity.
Tension
Curse of Knowledge
The curse of knowledge is the difficulty experts have in imagining what novices don't know. The Feynman Technique is a direct counter: by forcing explanation to a novice, you combat the curse. The tension is that the curse makes the technique hard to do well — which is exactly why the constraint is valuable.
Tension
[Chunking](/mental-models/chunking)
Chunking is compressing information into familiar units. Explanation often uses chunks (e.g. "supply and demand"). The tension: if your "simple" explanation is just a chunk label, you may not have deepened understanding. The technique asks you to unpack chunks until the mechanism is clear.
Section 8
One Key Quote
"What I cannot create, I do not understand."
— Richard Feynman
Creation — including the creation of a clear explanation — is the test. If you can't build the idea from scratch or express it in your own simple terms, your understanding is incomplete. The technique turns that test into a repeatable process.
Section 9
Analyst's Take
Faster Than Normal — Editorial View
Use explanation as a gate. Before any high-stakes presentation or decision, run the Feynman test. Write or say the core idea in plain language. Where you can't, you're not ready. Fix those spots before you commit.
Simplify, don't dumb down. The goal is to remove jargon and unnecessary complexity while keeping the logic correct. Simplification that loses critical nuance is a failure. The standard is "understandable by a smart outsider," not "vague."
Iterate on the gaps. The first explanation will have holes. The value is in identifying them. Treat each gap as a study item or a place to refine the argument. Re-explain after filling gaps until the whole thing holds.
Section 10
Summary
The Feynman Technique is using simple explanation as a test and driver of understanding: choose a concept, explain it as to a novice, find where you falter or use jargon, fill those gaps, and repeat. It leverages retrieval, fights the curse of knowledge, and turns explanation into a diagnostic. Use it to stress-test your grasp before decisions or presentations and to force clarity in strategy and analysis.
Testing improves retention more than re-studying. Explaining is a test — you're testing whether you can produce a coherent account. The Feynman Technique is an application of the testing effect with a simplicity criterion.
Leads-to
The Socratic Method
The Socratic Method uses questioning to expose gaps and deepen understanding. Like the Feynman Technique, it forces explanation and surfaces what is not yet clear. Teaching or explaining — whether to others or to an imaginary audience — is a close relative: both use the demand for clarity as a test of understanding.
