Difficulty naming a concept means you don't understand…
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.
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.