Naming architecture
See also: nomenclature system
Naming architecture is the system that governs how names relate to one another across a portfolio: which products carry the master brand, which stand alone, and how new entries are named consistently as the range grows.
In practice
Architecture is what stops a company ending up with a feature called one thing in the interface, another in the documentation and a third in the sales deck. It is a set of written rules about who gets a name, what kind of name, and how it sits beside the parent.
Marriott's FY2023 annual report is a public trace of one: the endorsed pattern of "Name by Marriott" appears next to brands that carry no such line, which only stays legible because somebody decided which products get which form. WARC makes the point that the textbook spectrum has collapsed in practice into two opposites, which is why the written rule matters more than the label.
In a naming project the architecture is the document the generation stage reads. It tells the team whether a candidate is a descriptor, a standalone name or an endorsed name, and which of the other names it must not resemble. What goes wrong is its absence: each launch re-opens the debate, exceptions pile up, and a sub-brand appears because the person naming it did not know the rule. The practical steps, from listing the names in use to writing the rule for the next product, are in Brand hierarchy: branded house or house of brands?.
Where this sits in the process
The studio treats this as part of a single run rather than a separate service: the category is read, the creative direction is chosen from what the research found, candidates are generated in volume and then cut against criteria that were written down first. See how the studio works for what that produces, or the naming module for the stages themselves.
Related concepts
- Brand architecture: Branded house, house of brands, or something between: how portfolio structure decides what a new name is allowed to do.
- Sub-brand: When a product deserves its own name and when it only needs a descriptor: the sub-brand decision.
- Naming convention: Every category has patterns its names obey.
Further reading
- Brand hierarchy: branded house or house of brands?: How to structure the brands in a company: branded house, house of brands, endorsed brands and sub-brands. Real examples, and what each model asks of a new name.
Frequently asked questions
What is naming architecture?
Naming architecture is the system that governs how names relate to one another across a portfolio: which products carry the master brand, which stand alone, and how new entries are named as the range grows.
What is the difference between brand architecture and naming architecture?
Brand architecture is the model, such as branded house or house of brands. Naming architecture is the written rule set that applies the model to names: who gets a name, what kind of name, and how it sits beside the parent.
Why do companies need a naming architecture?
Without one, the hierarchy is the sum of naming decisions taken one at a time by different people. The result is a feature called one thing in the interface, another in the documentation and a third in the sales deck.
What does a naming architecture contain?
A short list of rules: the model per product group, the test for when a product earns its own name, the pattern for endorsed names, and the owner who decides exceptions.
Sources
- [1]Form 10-K, Marriott International Inc. (fiscal year 2023)— U.S. Securities and Exchange Commission
- [2]Brand architecture spectrum— WARC