How do you use a major design system as a reference without losing your own design identity?

References like Adobe, Microsoft, and Apple show how to control rhythm and hierarchy.

They do not tell you what font sizes to use or what personality to have.

Major design systems are useful for what they get right structurally: rhythm, spacing, hierarchy, density, component behavior. They have been tested across millions of users and screens. They are not useful as a source of aesthetic choices — font pairings, accent colors, expressive components, personality. Those choices belong to the product. The mistake is to study a reference's structure and accidentally copy its surface. You end up with the reference's personality instead of your own. The product starts to look like a cheaper version of Adobe or Microsoft, rather than a distinctive thing. Use references surgically: take the structural lesson. Leave the surface entirely alone.

A team studied how Microsoft Fluent handles spacing tokens and applied that structural learning to fix inconsistent component padding. The product's own color palette, typography, and expressive components were not changed. The result was a more disciplined product — not a Microsoft-flavored one.

References like Adobe, Microsoft, and Apple show how to control rhythm and hierarchy. They do not tell you what font sizes to use or what personality to have.