Identity must be redone when expanding product lines is a structural fault, not an aesthetic one. The system is designed around a specific product, rather than around the logic of the brand. The solution is to establish an identity architecture that can scale from the very first time, rather than waiting until there are many products to think about the system.
In this article · 6 sections
An identity designed for a single product usually looks very good at launch. The colors are harmonious, the typefaces carefully chosen, the packaging or interface layouts clean and consistent. Then a second product line is needed, or a different price segment, or a new market, and things start to fall out of line. Not because the designer did anything wrong, but because the system has no room to grow.
The issue is not about aesthetics
When a brand has to redo its identity after expanding its product line, the natural reaction is to blame the quality of the original design. But this is the wrong way to frame the issue. The initial identity may be very beautiful and work well within the scope it was created for. The problem is that it was created for a specific situation, not for a scalable system.
The difference between these two approaches is a difference in structural thinking, not in skill. A skilled designer without a systems mindset will create beautiful identities that are fragile and break when stretched beyond their original context. A designer with a systems mindset creates identities that can accommodate change without losing consistency.
Why the system breaks
When brand identity design starts from a specific product rather than from the brand essence, visual choices often follow the characteristics of that product. For example, the color of the material, the shape of the packaging, the feel of the price segment. All these choices make sense in the initial context.
If the initial identity is built around the characteristics of the first product, the second product will fall into two situations. One is that it looks like the first product even though they are fundamentally different. The other is that it looks completely different and loses connection with the parent brand. Both are poor choices.
This figure reflects a deeper structural issue: guidelines are written to describe an existing identity, not to guide how that identity can expand. When new products emerge outside the scope of the written guidelines, practitioners are forced to improvise. And improvising multiple times without clear foundational principles is a recipe for inconsistency.
Immutable layer and flexible layer
The core principle of a scalable identity system is to clearly separate two parts. One part never changes. The other part is allowed to change in a controlled manner.
The fixed layer is made up of the elements that create brand identity, no matter which product you are looking at. This group usually includes the logo and how it is used in different contexts, the primary typeface, a few distinctive graphic elements such as patterns, shapes and the way space is arranged, and the tone of voice. These are the things that cannot be compromised when a new product arrives.
The flexible layer is made up of elements that can change by product line, segment, or specific application, within a predefined range. Secondary colors for each product line are a typical example. The brand has a fixed primary color, while each product line has its own signature color, as long as it follows the same logic of saturation, brightness, and how it pairs with the primary color.
Build a system, not a page.
Brad Frost, Atomic Design
This statement is written in the context of digital interface design, but the principles apply to the entire brand identity. When designing a specific packaging page, the result is a packaging page. When designing a system that creates packaging, the result is the ability to produce dozens of different packages that still look like they belong to the same family.
Design token: the infrastructure of consistency
In digital design, the concept of design tokens (design variables) is the most modern way to put this principle into practice. Tokens are named values stored centrally: the primary color is #1A1A2E, standard font size is 16px, unit whitespace is 8px. When any value needs to be changed, simply change it in one place and the entire system updates accordingly.
Token thinking does not apply only to screens. In a complete brand identity, the same logic calls for three things: defining a tiered color palette (core brand colors, context-based application colors, product-line colors); defining typeface pairing rules (which typefaces are used where, and the ratio between sizes); and defining an inviolable clear space around the logo. When these rules are written down as a system, rather than left as illustrative examples, the people executing the work can create new applications without having to ask from scratch.
Brand architecture and early decisions
The question of the scalability of identity is essentially a question of brand architecture. It is the relationship between the parent brand and its product or product lines. This decision is often postponed until there is a practical issue. But by then, it is too late to resolve it without incurring costs.
There are two main extremes. One is a branded house: all products carry the parent brand, sharing maximum identity, with lower identity-building costs since only one brand needs to be maintained. The other is a house of brands: each product or product line has its own completely independent brand, offering high flexibility but increasing operational costs with the number of brands. Between these two extremes, there are many intermediate structures, such as endorsed brands or sub-brands.
There is no structure that is completely right for every case. But this decision must be made consciously and early. Identity designed after the structure has been established will serve that structure much better than identity designed first and then forced into a later structure.
Signs that the system is not ready
Some common situations indicate that the current identity will not hold up when expanding. If you find yourself in any of the situations below, this is a good time to reassess the structure of the system before launching new products.
- The brand color is chosen because it fits the image of the first product, not because it represents the brand values.
- The logo has only one version, with no rules regarding how to resize, change colors, or use it on complex backgrounds.
- The guidelines document is a PDF file describing the current packaging or interface, not a document explaining the logic behind the choices.
- Each time a new document or application is needed, the original designer must be consulted again because no one internally knows for sure what the rules are.
- When adding a product line, the first question is “what color should we use” rather than “which part of our system does this color belong to.”
References
Marty Neumeier, The Brand Gap. Byron Sharp, How Brands Grow (Ehrenberg-Bass Institute). Brad Frost, Atomic Design. W3C Design Token Community Group, DTCG spec (stable 10/2025). Nathan Curtis, Modular Web Design and a deck on design system governance. David Aaker, Building Strong Brands. McKinsey & Company, The Business Value of Design, 2018. Marq (Lucidpress) / Demand Metric, Brand Consistency Report, 2021.
