Imagine a shelf in a store or a list of apps on a phone screen. A person has fractions of a second to distinguish one product from the line from another and at the same time understand that both belong to the same company. He does not read the text — he scans the color spot. That is why color works faster in brand architecture than a logo and faster than a slogan: it is the only element that the brain processes almost instantly, even before shape recognition.
The problem is that most companies solve this task intuitively: 'We'll give this subbrand green, it's about ecology', 'and this one — purple, it's premium.' Without a single logic, within two to three years, a mess of shades accumulates in the portfolio that are not connected to each other and do not read as a family of products.
A commonly accepted recommendation in branding is that approximately 70% of the visual code remains unchanged for recognition, while 30% provides uniqueness. Seventy percent of the visual code—logo shape, font pair, illustration style, and overall tone—remains unchanged and works to build trust: the user recognizes the 'parent' and transfers the reputation of the entire company to the sub-brand. The remaining thirty percent, often color, gives the sub-brand the right to its own identity and allows it to stand out from the rest of the product line.
A vivid example of this balance is AWS. Amazon Web Services uses the same corporate orange (#FF9900) as its parent Amazon, but places it on a dark background (#252F3E) instead of white. The color remains the same — the context has changed. The connection to the master brand is preserved at the level of recognizing the shade, while differentiation is achieved through changing the background and overall tone of the product: the retail marketplace looks light and 'consumer-friendly', while the cloud platform looks tech-savvy and strict.
A similar, yet mirror-like approach is seen on the Russian market: when Yandex Market transitioned from pure yellow to a combination of yellow + red, it gained a contrasting combination that stands out among dozens of other yellow icons in the phone, while the red still refers to the parent Yandex logo. This is the case where 30% of differences work in favor of competing for attention, while 70% of similarities work in favor of trust in the brand as a whole.
This is where the main gap lies in most materials on this topic: almost nobody explains how to distribute colors among dozens of products so that the system does not collapse within a year. A working approach is not to 'invent a color for each sub-brand', but to first build a categorization, and then assign a color to each category.
A telling example is AWS, which uses color coding for its services distributed by category:
The logic is simple: color encodes not the product name, but the function that the product performs in the system. A user seeing a red icon, even without knowing the service name, understands that this is about security. This is the color matrix: a table of 'product category → assigned color → justification for the choice', which lasts longer than the rebranding of a single subbrand.
When building such a matrix, it is important to limit yourself to five to six contrasting colors. More than ten colors in one system create confusion, and similar shades — for example, purple and lavender — are unsuitable for differentiation because the brain and especially cameras or low-quality screens are not always capable of distinguishing them.
The choice of color strategy directly depends on the brand architecture, and here one should look not at trends but at the structure of the portfolio.
| Architecture | The logic of color | Example |
|---|---|---|
| Branded House | Monochrome or one base color + tints — unity is more important than differences | Yandex, VTB |
| House of Brands | Contrast encoding — each sub-brand gets its own color world | P&G, Nestlé |
| Endorsed brands | Mixed approach: part of the logo in the parent brand's color + a sub-brand's own color block | Marriott, VTS |
VTS is a good example of a hybrid, endorsed model: the upper part of the sub-brand logos remains blue, visually tying them to the parent company, while the lower part is individually colored for each product. The sub-brand names are nevertheless styled uniformly — the difference is only through the color block, not through chaotic changes to the entire palette.
This is not an aesthetic coincidence, but a direct consequence of how color is perceived in the context of pricing positioning. Black, deep navy blue, and muted gray visually signal 'restraint' and 'confidence'—qualities that premium segment buyers subconsciously associate with quality and status. Bright saturated colors—yellow, orange, red—work to speed up perception and impulsive decision-making, which is critical for mass market, where decisions are made in seconds on the shelf or in a feed.
That is exactly why, within a single brand portfolio, a premium sub-brand almost never gets the same bright color as its mass-market counterpart—even while maintaining the same font and logo, the difference in color saturation and lightness signals a difference in positioning faster than a price tag ever could.
Cannibalization happens not because sub-brands are similar—often, on the contrary, it is due to incorrect differentiation. Here are typical failures:
All these mistakes are united by one thing: the lack of a matrix, which was mentioned above. Without a document where it is clearly stated who and why received their own color, decisions are made situationally—situation-based decisions in a portfolio of ten or more products almost inevitably begin to conflict sooner or later
A designer’s eye is not protection from mistakes—there needs to be a check that is close to real perception conditions
Such a process takes a couple of days, but saves years of rework — portfolio color matrices are changed unwillingly because they are already built into the packaging, interfaces and marketing materials of dozens of products at the same time.
Imagine a shelf in a store or a list of apps on a phone screen. A person has fractions of a second to distinguish one product from the line from another and at the same time understand that both belong to the same company. He does not read the text — he scans the color spot. That is why color works faster in brand architecture than a logo and faster than a slogan: it is the only element that the brain processes almost instantly, even before shape recognition.
The problem is that most companies solve this task intuitively: 'We'll give this subbrand green, it's about ecology', 'and this one — purple, it's premium.' Without a single logic, within two to three years, a mess of shades accumulates in the portfolio that are not connected to each other and do not read as a family of products.
A commonly accepted recommendation in branding is that approximately 70% of the visual code remains unchanged for recognition, while 30% provides uniqueness. Seventy percent of the visual code—logo shape, font pair, illustration style, and overall tone—remains unchanged and works to build trust: the user recognizes the 'parent' and transfers the reputation of the entire company to the sub-brand. The remaining thirty percent, often color, gives the sub-brand the right to its own identity and allows it to stand out from the rest of the product line.
A vivid example of this balance is AWS. Amazon Web Services uses the same corporate orange (#FF9900) as its parent Amazon, but places it on a dark background (#252F3E) instead of white. The color remains the same — the context has changed. The connection to the master brand is preserved at the level of recognizing the shade, while differentiation is achieved through changing the background and overall tone of the product: the retail marketplace looks light and 'consumer-friendly', while the cloud platform looks tech-savvy and strict.
A similar, yet mirror-like approach is seen on the Russian market: when Yandex Market transitioned from pure yellow to a combination of yellow + red, it gained a contrasting combination that stands out among dozens of other yellow icons in the phone, while the red still refers to the parent Yandex logo. This is the case where 30% of differences work in favor of competing for attention, while 70% of similarities work in favor of trust in the brand as a whole.
This is where the main gap lies in most materials on this topic: almost nobody explains how to distribute colors among dozens of products so that the system does not collapse within a year. A working approach is not to 'invent a color for each sub-brand', but to first build a categorization, and then assign a color to each category.
A telling example is AWS, which uses color coding for its services distributed by category:
The logic is simple: color encodes not the product name, but the function that the product performs in the system. A user seeing a red icon, even without knowing the service name, understands that this is about security. This is the color matrix: a table of 'product category → assigned color → justification for the choice', which lasts longer than the rebranding of a single subbrand.
When building such a matrix, it is important to limit yourself to five to six contrasting colors. More than ten colors in one system create confusion, and similar shades — for example, purple and lavender — are unsuitable for differentiation because the brain and especially cameras or low-quality screens are not always capable of distinguishing them.
The choice of color strategy directly depends on the brand architecture, and here one should look not at trends but at the structure of the portfolio.
| Architecture | The logic of color | Example |
|---|---|---|
| Branded House | Monochrome or one base color + tints — unity is more important than differences | Yandex, VTB |
| House of Brands | Contrast encoding — each sub-brand gets its own color world | P&G, Nestlé |
| Endorsed brands | Mixed approach: part of the logo in the parent brand's color + a sub-brand's own color block | Marriott, VTS |
VTS is a good example of a hybrid, endorsed model: the upper part of the sub-brand logos remains blue, visually tying them to the parent company, while the lower part is individually colored for each product. The sub-brand names are nevertheless styled uniformly — the difference is only through the color block, not through chaotic changes to the entire palette.
This is not an aesthetic coincidence, but a direct consequence of how color is perceived in the context of pricing positioning. Black, deep navy blue, and muted gray visually signal 'restraint' and 'confidence'—qualities that premium segment buyers subconsciously associate with quality and status. Bright saturated colors—yellow, orange, red—work to speed up perception and impulsive decision-making, which is critical for mass market, where decisions are made in seconds on the shelf or in a feed.
That is exactly why, within a single brand portfolio, a premium sub-brand almost never gets the same bright color as its mass-market counterpart—even while maintaining the same font and logo, the difference in color saturation and lightness signals a difference in positioning faster than a price tag ever could.
Cannibalization happens not because sub-brands are similar—often, on the contrary, it is due to incorrect differentiation. Here are typical failures:
All these mistakes are united by one thing: the lack of a matrix, which was mentioned above. Without a document where it is clearly stated who and why received their own color, decisions are made situationally—situation-based decisions in a portfolio of ten or more products almost inevitably begin to conflict sooner or later
A designer’s eye is not protection from mistakes—there needs to be a check that is close to real perception conditions
Such a process takes a couple of days, but saves years of rework — portfolio color matrices are changed unwillingly because they are already built into the packaging, interfaces and marketing materials of dozens of products at the same time.