What is brand architecture?
Brand architecture is the family tree. Every company with more than one thing to sell has to decide how those things are named, how they look, how much of the parent brand they carry and how much they stand on their own. The decision is the architecture, and it comes in three broad shapes: a branded house, where everything carries the master brand (one name, many products); a house of brands, where the parent stays in the background and each brand has its own identity; and the endorsed or hybrid models in between, where a sub-brand has its own name but visibly belongs to the parent.
It sounds like an org chart and it behaves like one. Architecture decides what a customer sees on the shelf, what a new product inherits on launch day, which brand takes the damage when something goes wrong and where a company's marketing money has to be spread. Most companies have an architecture whether they designed it or not; the undesigned ones are the ones with four logos on the same package.
Why it matters
Why brand architecture matters
Clarity sells. A customer who understands how a company's products relate to each other can find the right one, trade up to a better one and trust a new one because of the name it carries. A customer faced with a jumble of brands, sub-brands and product names has to work out the relationships, and most will not bother. Architecture is the difference between a portfolio that reinforces itself and one where every launch starts from zero.
It also matters for growth. A clear architecture tells a company where a new product belongs, what it should be called and whether it should exist at all. It protects the master brand from a risky extension, and lets a fashion house reach a new, younger customer with a sub-brand without diluting the main line. Companies that skip the work tend to find out later, when the rebrand costs ten times what the planning would have.
In practice
How brand architecture works in practice
- 01
It starts with an audit: every brand, sub-brand, product name, logo and descriptor the company uses, laid out with where it appears and what it is meant to do. Then the strategic questions. Does the master brand add credibility to this product or hold it back? Does this audience want to know who the parent is? Are two brands competing for the same customer? Would a new product be stronger with its own name or with the parent's?
- 02
From the answers comes the model and the rules: naming conventions, how logos lock up, how much visual identity each level inherits, what an endorsement line says, which brands get their own marketing budgets and which ride on the master. The output is a document, a set of guidelines and, usually, some brands that get retired. Then it has to be lived in, because architecture erodes one well-meaning product name at a time.
- 03
The naming question is where most of the arguments happen. A descriptive name under the master brand is cheap to launch and inherits trust; an independent brand is expensive to launch and can go where the master cannot. The right answer depends on how far the new thing sits from what the parent is known for, and on how much money the company is prepared to spend making a new name mean something.
- 04
The model is tested before it is adopted. The proposed names and lockups are mocked onto the places customers meet them, a shelf, an app store listing, a store sign, a search results page, and shown to a few customers who are asked to find a product and say who makes it. Then the model gets a keeper: a small group that approves any new name or logo before it exists, because a model with no gatekeeper lasts until the next product launch.
At RIOT
Brand architecture at RIOT
We have watched architecture at work over more than a decade with Coach, including Coachtopia, a sub-brand with its own purpose and audience that still visibly belongs to the house. We run our own small version: RIOT is the master brand, and Krova (production software), AltSounds (a music video channel), vandal_ (a creative shop) and Muvvoo (a music video database) each carry their own name for an audience that does not need to know about the agency first.
Watch out
What people get wrong about brand architecture
Letting it happen by accident. Every product team wants its own logo, and without a model to say no, a company ends up with a house of brands it never meant to build and cannot afford to market. The opposite error is forcing everything under one name when the audiences genuinely differ. Architecture is a strategic choice, and the sign of a bad one is a customer asking which of your brands is the real you.
