Inability to explain simply = incomplete processing, not a labeling problem — if you can't explain to a zero-context audience, you don't fully understand
When you cannot explain a concept in simple terms to someone with zero shared context, treat this as diagnostic evidence that your processing is incomplete rather than a labeling problem.
Why This Is a Rule
Richard Feynman's famous teaching principle — "If you can't explain it simply, you don't understand it well enough" — isn't just pedagogical advice. It's a diagnostic tool for processing completeness. The ability to explain a concept in simple terms to someone with zero shared context requires that you've built a genuine mental model: you understand the mechanism, you can generate examples, you can distinguish the essential from the incidental, and you can express the core idea without relying on jargon as a crutch.
When you can't explain simply, the instinct is to blame communication: "It's just hard to put into words" or "This is too complex to simplify." But the difficulty almost always lies in the understanding, not the articulation. Jargon serves as a compression format for people who share the decompression key — but if you can't decompress the jargon into plain language, you've memorized the compressed form without understanding the underlying content. You're carrying an encrypted file without the decryption key.
The "zero shared context" constraint is the stringent version. You're not explaining to a peer who shares your vocabulary — you're explaining to someone who has no background in the field. This forces maximum decompression: every assumption must be made explicit, every technical term must be translated, and every logical step must be shown. If your explanation survives this test, your understanding is genuine and complete.
When This Fires
- When testing your own understanding of a concept you've been studying
- When Create SRS cards only for information you already understand — memorization without comprehension produces brittle, unusable memory's prerequisite check (understand before memorizing) needs a verification method
- When you feel like you "kind of understand" something but aren't sure
- When preparing to teach, write about, or apply a concept in a new context
Common Failure Mode
Confusing recognition with understanding: you can recognize correct statements about a concept (multiple-choice tests, nodding during lectures) but can't generate an explanation from scratch. Recognition requires only pattern matching; explanation requires reconstructive understanding. The Feynman test specifically targets generation, not recognition.
The Protocol
(1) Choose a concept you've been processing. (2) Attempt to explain it in 3-5 simple sentences to an imaginary audience with zero shared context. No jargon, no abbreviations, no "as you know" assumptions. (3) Where you get stuck — where you reach for jargon, wave your hands, or say "it's complicated" — mark the sticking point. That's the specific gap in your understanding. (4) Return to the source material and specifically target the gap: what mechanism, relationship, or distinction are you failing to articulate? (5) Re-attempt the explanation. Repeat until you can explain the entire concept simply and completely. The gap between your first attempt and your final attempt represents the processing work that was still needed.