A new product range can make a new name feel irresistible. Before starting a naming exercise, I separate two possibilities: is the product new, or is the reason people choose it fundamentally different? Not every addition requires another brand.
Map the relationship the customer actually sees
Brand architecture is not a copy of an organisation chart. How does someone connect the names on packaging, in a shop or on a website? Does the parent name provide useful reassurance, or does it make different products harder to understand? I begin with that encounter.
Imagine a homeware brand introducing a tableware collection. If it serves a similar audience, price expectation and product promise, a collection name may be sufficient. A different use, distribution model and core proposition might justify a stronger distinction. This is an illustrative scenario, not a description of a particular company.
Compare the structures using the same questions
A single masterbrand, an endorsed sub-brand and an independent brand create different obligations. A masterbrand can draw on existing recognition, but its products share expectations. An endorsed name signals difference while retaining a visible relationship. An independent identity requires its own meaning to be established and maintained.
My comparison includes audience overlap, promise compatibility, distribution differences, reputational connection and editorial capacity. Being able to open another social account is not enough. The team should explain why anyone would follow it and which distinct information it will consistently provide.
Test the architecture at real touchpoints
I show alternatives on a packaging label, category page and short product explanation. People should not need internal company terminology to understand the relationship. I look for questions such as: whose product is this, how does it differ from the other range, and which assurances still apply?
The approach in message testing is useful here. Ask people to describe their understanding rather than vote on whether a design appeals to them. A tidy strategy diagram does not establish that the structure will make sense during an actual purchase decision.
Build only what the team can maintain
Another brand means another set of descriptions, assets, source files and update responsibilities. If ownership is unclear, a neat distinction can gradually become inconsistency. I consider how the structure would operate a year after launch, not just how it looks in the announcement.
Returning to the brand strategy guide, my test is practical: does the structure help readers understand a meaningful difference and help the team make consistent decisions? If not, simplifying the existing hierarchy may be more valuable than adding a name.