Naming gets treated as the fun part, a brainstorm, a few sticky notes, a vote. Then the name ships and shapes years of decisions nobody traces back to that afternoon. What you call things determines what people can think clearly about. That makes naming infrastructure, not garnish.
Names are just interfaces
A good name is an interface to an idea. It compresses something complex into a handle people can pass around without re-explaining. A bad name charges a tax: every conversation starts with a definition, every new hire needs a translation, every customer hesitates for the half-second that adds up.
Internal names matter as much as external ones. If your features, tiers, and processes are named inconsistently — three words for the same thing, one word for three different things — your team pays a comprehension tax on every exchange.
Confused naming is confused thinking with better production values.
The compounding cost of 'we'll fix it later'
Names are sticky because they propagate. A name enters the codebase, the contracts, the help docs, the customer's vocabulary. By the time everyone agrees it's wrong, it's load-bearing, and renaming means touching everything it touched. The cheapest moment to get a name right is before it spreads. The second cheapest is now.
A simple naming discipline
You don't need a linguistics degree. You need a few rules applied consistently:
- One thing, one name. Kill synonyms ruthlessly. Pick the word and enforce it everywhere.
- Name by what it does, not what's clever. Cleverness ages badly and onboards slowly.
- Test it out loud. If people can't say it, spell it, or remember it, it will quietly fail in every verbal channel — which is most of them.
- Write the definition once, centrally. A name without an owned definition drifts into meaning whatever the loudest person assumes.
Naming as a system, not a moment
The mistake is treating naming as a one-time event instead of an ongoing capability. Products grow, features multiply, tiers get added. Without a naming convention — a small set of patterns your team reaches for by default — every new thing gets named from scratch, and the system frays.
Build the convention once and naming stops being a debate. New things slot into an existing logic. The brand stays coherent not because someone polices it, but because the easy path is the consistent one. That's brand as infrastructure applied to the most overlooked layer of all: the words.