·High Performance & Learning
Section 1
The Core Idea
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.
