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.
Design Systems for Us: How Many One-Source(s)-of-Truth Are Enough?
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
"Synthetic users might be okay for finding average behaviors, but they won’t replace unique insights from real users."
Kate Towsey Basel Fakhoury Oren Friedman Graham GardnerParticipant Recruitment and Management Tools
March 12, 2026
"People are the plot twist in this journey — despite promising AI, only human connection reveals new problems and solutions."
Jennifer KongJourneying toward AI-assisted documentation in healthcare
June 5, 2024
"Engineers are great at executing code but often lack connection to user experience and design processes."
Kevin M. HoffmanTheme 2: Enterprise Team Journey
June 3, 2019
"Find your senior executive ally who understands design and go talk to them first — it works."
Amy MarquezINVEST: Discussion
June 15, 2018
"Designers can be really paranoid and very precious."
Gretchen AndersonScaling the Human Center
June 8, 2017
"Foresight is a team sport—the more perspectives you have, the better your future scenarios become."
April ReaganLook, Think, Act: The Futures-Smart Design Organization
October 1, 2021
"We matched designers with new peer buddies outside their usual domains to encourage learning and networking."
Dante GuintuHow to Crush the Talent Crunch
September 8, 2022
"Respect your design system rules to ensure consistent experiences across your product and teams."
Jaime CreixemsBest Practices when Creating and Maintaining a Design System
June 7, 2023
"Balsamiq is more a communication tool, intentionally limiting high polish so you focus on sharing ideas and getting feedback."
Billy CarlsonPrinciples of Team Wireframing
October 2, 2023
