Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
Summary
As large organizations embed design systems, they'll often find they have multiple systems. A search for the "one source of truth" collides with another truth: change and coordination across business units is hard, alignment is costly and effortful, and sometimes there's good reasons for having many systems loosely coupled. In this conversation, we explored the nature of systems of systems, tiered for participation at many levels across an organization.
Key Insights
-
•
Design systems should be viewed as multi-tiered ecosystems rather than monolithic entities.
-
•
Adoption varies across products; some embed system designs without using code, weakening consistent implementation.
-
•
Separating design assets from code tools can be justified in complex environments with diverse frameworks.
-
•
Mergers and acquisitions challenge system adoption and require early collaboration with brand teams.
-
•
Multiple generations of a design system can coexist, creating upgrade and adoption challenges.
-
•
Subsystems or descendant systems enable product teams to extend core components for their unique needs.
-
•
Tribalism and business-unit silos impede unified system governance and consistency.
-
•
Successful design systems treat their teams as product teams with roadmaps and clear customer relationships.
-
•
Effective onboarding and vendor collaboration are critical for maintaining system quality and consistency.
-
•
Building consensus on incremental shared elements, like colors or iconography, helps unite fragmented design efforts.
Notable Quotes
"Design systems are not just products; in many respects, they're information products."
"One source of truth is the goal, but in reality, even at scale, adoption and consistency vary widely."
"Embedding design from the system into product code without using system code leads to irregular quality and durability issues."
"Should you separate design from code? In some multi-framework environments, yes, it makes sense."
"Acquisition integration shouldn’t start with migration analysis but with engaging brand teams first."
"Allowing teams to override small things like button color may be justified if it delivers business value."
"Banks are among the hardest organizations to unify around a design system due to slow, deliberate change."
"Building a design system is really about breaking big problems into smaller parts that have real value."
"Onboarding is critical; the first five minutes an engineer spends working with a system defines their experience."
"Creating one adopted component can be harder than creating a hundred that never get used."
Or choose a question:
More Videos
"We are truly in a golden age for our profession."
Doug PowellClosing Keynote: Design at Scale
November 8, 2018
"Make sure children understand they can stop the session at any time, and confirm they really get that."
Mila Kuznetsova Lucy DentonHow Lessons Learned from Our Youngest Users Can Help Us Evolve our Practices
March 9, 2022
"Artifacts of the future help us envision and grasp the change that we’re hoping to have—it’s not just bullet points or vision statements."
Sarah GallimoreInspire Progress with Artifacts from the Future
November 18, 2022
"Junior team members don’t have to talk directly to executives; working effectively with peers can create grassroots buy-in."
Lada Gorlenko Sharbani Dhar Sébastien Malo Rob Mitzel Ivana Ng Michal Anne RogondinoTheme 1: Discussion
January 8, 2024
"Our goal is to be AI fluent, not necessarily AI experts."
Alnie FigueroaThe Future of Design Operations: Transforming Our Craft
September 10, 2025
"When executives start questioning your research details, that’s a good sign they’re engaged and trusting the process."
Landon BarnesAre My Research Findings Actually Meaningful?
March 10, 2022
"Every workaround is a mini story of somebody overcoming an obstacle."
Emily EagleCan't Rewind: Radio and Retail
June 3, 2019
"We did a blended approach with a visual refresh first to minimize differences between old and new and buy time."
Malini RaoLessons Learned from a 4-year Product Re-platforming Journey
June 9, 2021
"I learned to be relentless about prioritization and to hone in on specific details and use cases."
Asia HoePartnering with Product: A Journey from Junior to Senior Design
November 29, 2023
Latest Books All books
Dig deeper with the Rosenbot
What systemic challenges in tech have led professionals like Chelsea to leave for law?
How do champions at different organizational levels impact the success of service design initiatives?
How should service designers adapt their approach when working in different cultural and market contexts, like the US versus Europe?