System of Systems: Managing Design Systems at Scale

WHY IT EXISTS: A single, monolithic design system often fails at large scale. It becomes too rigid to serve diverse product needs or too bloated trying to accommodate everyone. A system of systems addresses this by allowing for both shared foundations and specialized extensions, creating more value than the sum of its parts.

THE MENTAL MODEL: Think of it like a federal government. A central authority provides the core brand, shared tokens, and universal components. But individual states—the product-specific design systems—have their own local governments to address unique needs, as long as they don't violate the central rules. It's about managing relationships and boundaries between systems.

HOW IT WORKS: A system of systems is composed of multiple, distinct design systems that are intentionally designed to interoperate. They often share a common core, such as a token library for brand colors and typography. One system might be the "source of truth" for brand foundations, while other systems consume those foundations and add their own platform-specific or product-specific components. The key is a deliberate architecture for sharing and extension.

WHEN TO USE IT: Use this approach in large organizations with multiple, distinct products or brands that need to feel related but not identical. It's also useful when a single product has drastically different platform requirements, such as a web app, a native iOS app, and a native Android app, where a single component library would be impractical.

WHEN NOT TO USE IT: For most companies with a single primary product, a single design system is far simpler and more effective. A system of systems introduces significant overhead in governance, tooling, and communication. Applying this model prematurely is a classic case of over-engineering that creates complexity without solving a real problem.

ONE CANONICAL EXAMPLE: Google's Material Design is a public example. Material 3 is the core system, providing guidelines and tokens. Individual Google products like Gmail, Android OS, and Google Maps each have their own implementation and extensions. They are distinct systems that consume and adapt the core parent system, creating a cohesive but not rigidly uniform ecosystem.