Seven worlds, one system

A product family needs coherence, but coherence is not sameness. A word game and a PDF utility should not share every visual decision. They should share a deeper standard: how clearly they communicate, how carefully they respond, and what they refuse to make complicated.

Separate principles from components

Components are reusable solutions. Principles are reusable judgment. A button can be shared across closely related products, but “make the primary action unmistakable” can guide every product regardless of platform or visual style.

When a design system begins with components alone, teams can produce consistent screens that still feel inappropriate for the task. Starting with principles makes room for category-specific expression while protecting the qualities that define the studio.

Define the family resemblance

Family resemblance can live in typography, spacing rhythm, interaction timing, language, icon construction, and the way surfaces respond to input. Not every trait needs to appear everywhere. A small set of repeated cues is usually stronger than a rigid template.

We look for decisions users can feel across products: direct language, focused flows, forgiving actions, careful defaults, and motion that explains change. Visual motifs then reinforce that behavior instead of carrying the entire brand.

Let each product earn its identity

Category matters. Learning software benefits from visible progress and encouragement. A utility should emphasize speed and reliability. A game needs tension, rhythm, and reward. The shared system should help each product become more itself.

This is where tokens and components become flexible tools rather than rules. Color, density, and expression can vary while accessibility, interaction quality, and structural conventions remain dependable.

Govern through examples

Design-system documentation is most useful when it shows decisions in context. A principle such as “clear over clever” becomes actionable when paired with before-and-after examples, content guidance, and exceptions.

A small studio can keep governance lightweight. Review new patterns, record why they exist, and promote them into the shared system only after they prove useful in real work. The system grows from evidence rather than prediction.

TakeawayA strong multi-product design system protects shared principles while giving every product enough freedom to respond honestly to its category and users.