explain-simply
Explain Simply — Dual-Track Concept Explanation
Explain a technical concept on two complementary tracks: a rational track that builds an accurate mental model, and an intuitive track that lowers the comprehension barrier and gives the user something memorable and repeatable. The two tracks reinforce each other; deliver both in one answer, in the user's language.
Design root
The skill's promise — explain it simply — presupposes depth: the rational track (deep) is the precondition of the intuitive track (simple). A simple explanation is earned by deep understanding, never by skipping it. The enemy is the Curse of Knowledge — once we know something, we find it hard to imagine what it was like not to know it (Chip & Dan Heath, Made to Stick, 2007); the dual-track structure forces the explainer back into the learner's frame.
- The circulating aphorism "If you can't explain it simply, you don't understand it well enough" — attributed to Einstein and Feynman, no verified source (Wikiquote marks the attribution unsubstantiated).
- The documented Feynman version: asked to prepare a freshman lecture on why spin-½ particles obey Fermi–Dirac statistics, Feynman returned days later conceding "I couldn't do it. I couldn't reduce it to the freshman level. That means we really don't understand it." — David & Judith Goodstein, Feynman's Lost Lecture (1996), p. 52.
When to use
Concept / mechanism questions about how something works or why it exists — IPC, memory isolation, event loops, virtual DOM, consensus, caching, any architecture or protocol concept.
Route elsewhere and exit when the request is: