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
"We encourage everyone to think big first then trim down based on priorities and keep a backlog of good ideas."
Yunyan Li Anna Le Jen KimUX Best Practices
June 11, 2021
"You can’t just grab everything—you have to refine the content to avoid irrelevant or contradictory information."
Allan LowsonRehashing the Double Diamond: Collaborating across functions with AI-assisted prototyping
June 9, 2026
"We’re not going for perfection. We’re going for excellence and change."
Denise Jacobs Nancy Douyon Renee Reid Lisa WelchmanInteractive Keynote: Social Change by Design
January 8, 2024
"At Meta, one product partner said quality doesn’t matter because we’re bringing in $90 billion a year."
Renee BouwensLanding Product Impact: Aligning Research as a Foundational Driver for Delivering the World’s Best Products
December 15, 2023
"It’s not about power, it’s about guidance—helping people collect and use good data, even in qualitative settings."
Jemma Ahmed Steve Carrod Chris Geison Dr. Shadi Janansefat Christopher NashDemocratization: Working with it, not against it [Advancing Research Community Workshop Series]
July 24, 2024
"Sometimes you’re too early. Don’t fear. File this away and keep your powder dry."
Sam LadnerHow Research Can Drive Strategic Foresight
March 9, 2022
"Knowing in action is the intuition practiced by competent designers, a core of artistry."
Yoel SumitroActions and Reflections: Bridging the Skills Gap among Researchers
March 9, 2022
"Democratization of research is interesting but not a one-size-fits-all; it needs quick assessment of what a team truly needs."
Dave HoraResearch in the Face of Complexity: New Sensibility for New Situations
August 27, 2025
"You don’t want to game anybody here. This is persuasion by evidence, not by trickery."
Daniel J. RosenbergDesigning with and for Artificial Intelligence
August 11, 2022
Latest Books All books
Dig deeper with the Rosenbot
What workflow stages are critical for integrating AI tools in product, design, and engineering?
How will the roles of designers, product managers, and engineers evolve as AI blurs traditional boundaries?
What role can familiar communication channels like WhatsApp play in deploying AI tools in resource-limited settings?