Designing for one product, scaling must be redone

Identity designed for a product often looks great at launch. Colors are harmonious, typefaces are carefully chosen, and the layout of packaging or interfaces is clean and consistent. Then, when a second product line, a different price segment, or a new market is needed, everything starts to misalign. Not because the designer did something wrong, but because the system lacks room for growth.

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 immutable layer consists of elements that create brand identity, regardless of which product is being viewed. This group typically includes the logo and its usage in various contexts, the primary typeface, some distinctive graphic elements such as patterns, shapes, spatial arrangement, and tone of voice. These elements should not be compromised when new products are introduced.

The flexible layer consists of elements that can change according to product lines, segments, or specific applications, within predefined limits. Secondary colors for each product line are a prime example. The brand has an immutable primary color, while each product line has its own identifying color, as long as it adheres to the same logic regarding saturation, brightness, and how it combines 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 is the most modern way to realize this principle. 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 applies not only to screens. In overall brand identity, similar logic requires three tasks: defining a color palette by layer (primary brand color, contextual application color, product line color); defining type combination rules (which typeface to use where, ratio between sizes); and defining a no-go zone around the logo. When these rules are documented as a system, rather than just as illustrative examples, practitioners can create new applications without needing to start 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" instead of "which system does this color belong to."