Difficulty naming a concept means you don't understand it yet — not a vocabulary problem
When encountering difficulty naming a concept precisely, treat that difficulty as a diagnostic signal revealing incomplete understanding requiring further processing rather than a labeling problem.
Why This Is a Rule
Naming precision tracks understanding depth. When you deeply understand a concept, naming it is easy — the name falls out of the understanding. "This is the gap between perceived understanding and actual understanding" → "illusion of explanatory depth." The name is obvious because the concept is clear.
When naming is hard — when you cycle through options that all feel slightly wrong, or when you resort to vague descriptors like "that thing where..." — the difficulty isn't a vocabulary problem. It's a comprehension problem. The concept in your mind is fuzzy, and the naming friction is feedback telling you the fuzz exists.
This reframe matters because the two diagnoses lead to different actions. If naming difficulty is a vocabulary problem, the fix is to search for existing terminology (thesaurus, domain jargon). If naming difficulty is an understanding problem, the fix is to process the concept further — decompose it, explain it, test its boundaries — until the understanding clarifies enough that the name becomes obvious.
When This Fires
- Creating a new note and struggling to title it
- Naming a variable, function, or class in code and cycling through options
- Trying to label a category in a framework or taxonomy
- Any situation where you can describe something but can't name it concisely
Common Failure Mode
Forcing a "good enough" name and moving on. The vague name becomes a permanent container for vague understanding. Every time you or someone else encounters the name, it doesn't quite communicate the concept — because the concept was never clarified. The naming friction was a signal you ignored, and the unclear name perpetuates the unclear thinking.
The Protocol
When naming a concept is hard: (1) Stop trying to name it. (2) Write a paragraph explaining what the concept is, how it works, and how it differs from adjacent concepts. (3) Read your paragraph. If the concept is now clear, the name will be obvious. (4) If the concept is still unclear, the paragraph revealed specifically where your understanding breaks down — process that gap. (5) Return to naming only after the explanation is crisp. The name should feel inevitable, not chosen.