Brand Architecture: What Should Your Brands Share—and What Should Stay Different?
By Quincy Samycia
Imagine a company with five specialist businesses. Each has its own name, website and presentation. Some acknowledge the parent company. Others barely mention it. A customer moves between two of them and cannot tell whether they have discovered a related service or an entirely different organization.
Shared ownership alone is a weak reason to make every brand look alike. The relationship between brands should help customers understand the offer. A tidy family of logos cannot do that work on its own.
This is where brand architecture becomes a design problem. Brand architecture defines the relationships between a company, its brands and its offers. Those relationships become visible through names, identity systems, language, navigation and everyday interactions.
My test is practical: can someone understand how these businesses belong together, and does that understanding help them make a decision? If the connection adds no useful meaning, making it more prominent may simply add noise.
Start with the relationship the customer needs

An organizational chart explains ownership and reporting. It does not necessarily explain how a customer should encounter the business.
Two services may share a finance department while serving unrelated audiences. Two separately managed businesses may solve consecutive parts of the same customer problem. Design has to account for the relationship that matters outside the company.
Before deciding how closely the identities should resemble each other, ask what the connection contributes. Does the parent name provide useful credibility? Would customers benefit from discovering the other services? Does one specialist brand carry recognition that a new group identity should preserve?
The answers establish the job of the architecture. A shared identity needs a customer-facing purpose. Separate teams still need to explain their connection when their services form part of the same journey.
Give the parent brand a clear role

There are several ways to make the relationship visible. The parent brand can lead, with individual services described beneath it. A specialist brand can lead, supported by a parent endorsement. Or the businesses can present themselves independently, with the ownership relationship carrying little weight in the customer experience.
Consider a hypothetical group offering workplace training, recruitment and executive coaching. Its leadership wants one name across the portfolio, but the coaching business has an established reputation with senior executives. Replacing that name would make the presentation tidier while asking an existing audience to learn a new identity.
A possible answer is to retain the coaching name and add a clear parent endorsement. Training and recruitment could use the parent name with service descriptors. The trade-off is deliberate: accept some visual variation to preserve recognition, while making the group relationship understandable.
These choices establish different expectations. A prominent parent name suggests something meaningful is shared. The business needs to decide what that is: expertise, standards, access, service or another credible connection.
A parent endorsement should represent something the business can explain and deliver. A customer should not have to discover that the apparent continuity ends immediately after the enquiry.
Decide what is shared, variable and distinct

Once the relationship is agreed, the identity needs to express it consistently.
That requires more than placing several logos on the same slide. Decide which name leads, how an endorsement appears, what typography is shared, where colour distinguishes an offer, and how imagery reflects each audience.
I find it useful to separate the decisions into three groups: what is shared, what can vary, and what must remain distinct. Applied to the hypothetical group, that framework produces specific design choices.
Shared: Use a consistent parent endorsement, typographic hierarchy and familiar navigation patterns. These elements explain the relationship and make related websites easier to move between.
Variable: Allow photography, accent colours and audience-specific language to change. Recruitment may need to speak to candidates and employers; executive coaching needs to address a different conversation. Variation should reflect those needs.
Distinct: Preserve the coaching brand’s name and specialist positioning. Keep service promises, credentials and the identity of the business receiving an enquiry explicit. The group connection should not imply that every service has the same expertise.
These are choices for this example, not universal rules. Another portfolio may need much greater independence. The framework gives the team a way to explain where consistency helps and where it would conceal a meaningful difference.
The rules should explain the reason for each choice. If a specialist colour helps people identify a service, say so. If an endorsement establishes the group relationship, define where it needs to appear and remain legible.
A guideline becomes more useful when the next designer can understand the decision well enough to apply it in a situation the original team never illustrated.
Make the website explain the connection

The website is where an apparently coherent brand family can become confusing.
A visitor selects a service and arrives on another domain. The logo changes, the language shifts, and the form asks them to introduce themselves again. Perhaps that separation is appropriate. But the transition needs to make sense.
Map those transitions before deciding how many websites the business needs. What should the visitor understand before leaving one site? Which context needs to be explained on arrival? Who will respond to the enquiry? Can someone return to the broader offer without starting over?
A single website can support distinct service journeys. Separate websites can still explain their relationship clearly. Domain structure should follow the audience and operating requirements rather than become a substitute for deciding the architecture.
Nielsen Norman Group’s guidance on consistency and standards explains how familiar patterns help users understand interfaces, including across a family of products. Applied here, the lesson is to keep recurring actions understandable even when related brands have distinct identities.
That clarity belongs in the small details. Form labels, confirmation messages and contact information should identify the business the person is engaging with. A shared visual system should never obscure that distinction.
Protect recognition during the transition

Architecture projects often involve brands that already have customers, employees and a history. Their existing names may still be doing useful work.
A presentation of the future system can make immediate uniformity look attractive. The customer may encounter the change through an old bookmark, a familiar sign, a referral or an email from someone they already know.
Include those encounters in the design brief. Explain a changed name where people will look for the old one. Make the relationship between old and new materials understandable. Give staff language they can use to describe the change.
This is also a question of sequence. The company may need to introduce the relationship before asking customers to recognize an entirely new identity.
A transition is part of the design assignment. It deserves more thought than a launch announcement followed by the assumption that everyone has caught up.
Test the family beyond the presentation

A row of logos can demonstrate visual harmony while leaving the experience unresolved.
Review the architecture through specific tasks. Ask someone to identify the right service, explain the relationship between two brands, and find out who will handle an enquiry. Show them an individual page or document without first explaining the full portfolio.
Then introduce something the system was not built around: a longer name, a new audience, an acquired business with a familiar identity, or a service that spans two specialties.
These exercises expose different weaknesses. Customer tasks reveal whether the relationships are understandable. New additions reveal whether the rules can accommodate growth without becoming meaningless.
The team also needs to know who owns those rules. Who approves a new name? Who decides when an endorsement is necessary? What justifies an exception? Without clear responsibility, each new project can quietly create a different architecture.
Design the relationship people will actually experience

The strongest outcome is a brand family whose structure helps people understand the offer. Sometimes that means putting the parent company forward. Sometimes it means allowing an established specialist to remain prominent.
For designers, the opportunity is to make those choices tangible: in the first name someone reads, the service they select, the website transition they follow and the message they receive afterward.
Before approving a family of brands, take away the presentation that explains it. Show someone a service page, an enquiry form and a confirmation email. If the relationship is only clear when the designer is in the room, the architecture still has work to do.
Quincy Samycia is co-founder and Head of Brand & Growth at The Branded Agency, where he works with teams on brand strategy, identity systems, and website experiences.
Find more Community stories on our blog Courtside. Have a suggestion? Contact stories@dribbble.com.
内容来自 Dribbble,版权归原作者所有。
阅读原文 ↗