PROJECT GUIDE / Brand Establishment and Evolution
Aligning Group and Sub-Brands
Clarify each brand’s role to create a brand architecture that can grow.
Define the Task First
Define the role of each brand and build relationships that can evolve as the business grows. Start by reviewing existing materials alongside typical use scenarios to establish where problems occur, who they affect and which content needs to remain in use.
The scope of a group and sub-brand alignment project depends on the business, its audiences and delivery requirements. The following offers a framework for discussion and planning.
Three Stages of Work
Architecture Review
Map corporate, business, product and regional brands separately, recording ownership, audiences and scope of use to keep naming levels distinct.
Identity Roles
Define how the parent brand, sub-brands and product names appear together, specifying which elements are shared and which can vary.
Putting Rules into Practice
Test the brand architecture across websites, business cards, exhibitions and sales documents. The rules should also accommodate new businesses.
What to Prepare Before We Talk
- Business structure, product lines, and future direction
- Existing brand materials and most-used touchpoints
- Customer interviews, sales feedback, and major competing brands
Representative samples are a good place to start. Past versions, real-world photos and typical feedback illustrate the problem better than style references alone; any missing information can be gathered during project discussions.
How We Discuss and Review
- Direction: Can one sentence explain why customers choose you?
- System: Are relationships between group, business units, and products clear?
- Application: Can sales, digital channels, and on-site teams use the same expression?
A shared visual style alone may leave the business hierarchy unclear.
Each review round records confirmed directions, required changes and who owns them. Before moving to the next phase, we clarify which materials the changes affect, so strategy, design and implementation stay connected.
Deliverables to Discuss
Brand architecture map, logo lockup rules, naming hierarchy and application examples.
Specific quantities, content depth, production scope and timing are determined by project materials and usage conditions. At delivery, we also record file versions, usage instructions and ongoing maintenance responsibilities.
CONTINUE READING Further Reading
Find your next step, starting with the question at hand.
When you get in touch about a project, it helps to share your business context, existing materials, primary use scenarios and the problems you want to solve. We'll use this to discuss scope and how we might work together.
Communicate project requirements ↗

















