Decide how your brands should relate

Map the portfolio customers encounter

List the company names, product names, ranges, memberships and service labels that people actually see. Include invoices, stores, apps, search results and support messages. Then identify what each name represents and who owns its promise. The internal organization chart is useful background, but a division name does not automatically deserve a separate customer-facing brand. Customers may organize their choices very differently from the finance department.

Map the journey across offers. Where does a person compare alternatives, move from an entry product to a specialist one, or seek support after buying? Note where a shared identity provides reassurance and where it creates a mistaken expectation. Collect concrete examples of confusion, such as customers requesting one product through another team's support channel. A portfolio diagram should solve a navigation problem rather than simply make the company look orderly.

Compare possible levels of connection

Consider a leading shared brand with descriptive offer names, a distinct offer name visibly endorsed by a parent, or identities that operate more independently. These are working options, not a rigid taxonomy that every business must fit. Sketch the same product page, storefront and invoice under each option. The consequences become clearer when customers must understand who is speaking, what is available and who will help if something goes wrong.

Ask what trust transfers between offers and what assumptions transfer with it. A familiar parent can reduce explanation, but it can also carry an unsuitable price expectation or service promise. Separation may create room for a different audience, while increasing the cost of recognition and maintenance. Shared ownership does not by itself prove customers want a shared identity. Conversely, small differences in product features may need clear descriptors rather than an entirely new brand.

Include the operational cost of each identity

Count the assets and obligations a new brand creates: naming review, design, domains, product information, sales training, customer support, measurement and ongoing communication. Estimate who can keep these accurate after launch excitement fades. If no owner can maintain the distinction, it may disappear into inconsistent improvisation. This is particularly important when a portfolio has many small offers, each with an enthusiastic sponsor but little continuing support.

IBM's public event guidance is an example of explicit master-brand governance: event expression and sub-brand systems serve a common identity, and teams are warned against inventing event brands without approval. This describes IBM's chosen system, not a universal answer. Its useful lesson is the existence of an enforceable rule, a shared resource and an approval owner. Your business may choose more independence, but it still needs equally clear boundaries.

Use contrasting portfolio choices as questions

HUGO BOSS describes distinct approaches for BOSS and HUGO, including different intended audiences and brand expression. That gives a concrete example of maintaining separate customer identities inside one corporate group. Read the case by asking what distinction a customer should notice and how communication supports it. The public report does not reveal every internal trade-off or prove that a two-brand structure is right for a different clothing business.

Heinz's global platform describes unifying communication around the Heinz name across products and markets. This is a contrasting direction: strengthen a shared brand idea rather than multiply campaign identities. It does not mean every product becomes interchangeable or that local requirements disappear. Together, the cases show that a corporate group, a consumer brand and a campaign platform are different levels of the system. Keep those levels explicit when debating whether something deserves a logo.

Write rules for the next offer

Choose the relationship that makes the portfolio easiest to understand while protecting meaningful differences. Specify which name leads, how endorsement appears, how categories and variants are described, and which promises are shared. Define an exception process for acquisitions, regulated offers or partnerships. A clear default with justified exceptions is more usable than a beautiful diagram that cannot accommodate the next practical launch.

Test the map with customer tasks, not only management approval. Ask people where they would buy, compare, upgrade, complain or obtain a replacement. Observe whether they confuse identity with ownership or assume benefits transfer when they do not. Document the decision, its owner and the evidence that would trigger review. Revisit architecture when the portfolio materially changes, rather than allowing each campaign team to quietly create its own lasting structure.

Make the reasoning concrete.

A hypothetical home-care business sells cleaning visits, maintenance plans and a professional training course. Each team wants its own brand.

Prototype both systems on an order page and a support request before commissioning three visual identities.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Inventory

   Which names exist and what real offer does each represent?

2. Customer movement

   Where do people compare, switch or seek help across offers?

3. Transfer

   Which trust and expectations should or should not transfer?

4. Maintenance

   Who will fund and maintain each proposed identity?

5. Rules

   Which identity leads, and when is endorsement used?

6. Exceptions

   Who approves a new brand or deviation from the system?

Read with a question in mind.

Watch for the wrong conclusion.

• Copying the organization chart into customer-facing names.
• Creating a separate brand for every feature.
• Ignoring support and maintenance costs.
• Confusing a campaign title with a permanent portfolio identity.

Sources & scope

Original editorial synthesis grounded in opened public practice sources and campaign evidence. Exercises, example businesses and calculations are hypothetical. No named human author or reviewer is claimed. This framework is not a validated universal law.

• IBM Event Design: Brand expression →Primary practice guidance · Supports: An actual master-brand governance model connecting event identities and sub-brand systems.
• HUGO BOSS Annual Report 2021: New Branding →Primary corporate report · Supports: Brand-refresh context and distinct BOSS/HUGO positioning.
• Kraft Heinz: Global creative platform launch →Primary brand announcement · Supports: 1 June 2023; unified strategy, five true/could-be-true vignettes, media channels, launch markets and relative investment claim.