How I Design Logo Systems for Multi-Brand Organizations

One Brand Is a Solved Problem

Designing a single logo for a single organization is a well-understood problem. There's a client, a brief, a set of constraints, and a deliverable. The challenges are real but they're bounded.

Multi-brand systems are a different category of problem. Now I'm designing for a parent organization and anywhere from two to twenty sub-brands that need to feel related to each other and to the parent while remaining individually distinct. The architecture of that relationship is the design challenge, and getting it wrong creates identity fragmentation that can persist for decades.

The Three Relationship Models

Before I design anything, I establish which relationship model the organization needs.

The monolithic model means everything lives under one master brand. Sub-brands are expressed as product lines or service categories within the parent's visual language. They don't have distinct logos — they have distinct naming treatments within the parent's mark. This works well for organizations with strong parent brand equity and sub-brands that benefit from the parent's halo.

The endorsed model means each sub-brand has its own distinct identity, but the parent brand appears as an endorser — a smaller lockup that says "a Parent company" or "by Parent." The sub-brands are primary; the parent provides legitimacy. This works for organizations with diverse portfolios where sub-brands serve different markets.

The independent model means sub-brands are fully independent with no visible connection to the parent in the logo. The relationship might be disclosed in legal copy but isn't expressed visually. This works for holding companies, private equity portfolios, and organizations where sub-brand independence is strategically necessary.

Choosing the wrong model causes problems that no amount of great design can solve.

Designing the Architecture First

Once the model is established, I design the architecture before I design any individual mark. For an endorsed model system with six sub-brands, that means defining the endorser lockup format, the spatial relationship between endorser and sub-brand, the minimum size at which the endorser appears, and the color system that allows each sub-brand to be distinctive while feeling systematically related.

These architectural decisions are more important than any individual mark. A beautifully designed sub-brand mark that doesn't fit the architecture is a liability.

Color as the Differentiator

In most multi-brand systems, color is the primary differentiator between sub-brands. The parent brand establishes the color system architecture — a shared neutral palette, shared typography, shared structural conventions — and each sub-brand gets a distinctive primary color within that system.

I select sub-brand colors with the full set in mind, not each one independently. The colors need to be distinct from each other (readable side by side in a chart or family display) while feeling harmonious as a group. This requires working in a color space that gives me enough differentiation room — HSL or OKLCH rather than just thinking about hue names.

Scalability

Multi-brand systems grow. The organization acquires new companies, launches new product lines, creates new service categories. The system I design needs to accommodate additions that weren't anticipated at the time of initial design.

I build scalability in by documenting the rules clearly enough that a new sub-brand identity can be designed by following the guidelines without needing to involve me. The architecture should be self-replicating within the defined rules.

When a system requires my direct involvement to extend, I've made the rules too implicit. Good system documentation is what separates a logo family from a visual identity architecture.