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
"An agency developing shared technical infrastructure must market to itself why change is preferred, not just rely on top-down mandate."
Stefanie OwensOptimizing for Outcomes: Transformation Design in Systems at Scale
December 4, 2024
"Don’t spend too much time trying to translate experience goals directly into business metrics; show the value of experience separately."
Gonzalo GoyanesDesign ROI: Cover a Little, Get a Lot
September 8, 2022
"Fear of losing your livelihood drives people to work longer hours and avoid asking for support."
Alla WeinbergPeople Are Sick of Change: Psychological Safety is the Cure
July 20, 2023
"Research repositories and libraries are social things — many teams look for best practices beyond just building a library."
Brigette Metzler Dana ChrisfieldResearch Repositories: A global project by the ResearchOps Community
August 27, 2020
"Our biggest hope is that you gain confidence to see opportunity and realize it amid crisis."
Lada GorlenkoTheme 2 Intro
June 9, 2022
"Designers need to be facilitators of other people's expertise and knowledge, not just creators of designed things."
Sheryl CababaExpanding Your Design Lens with Systems Thinking
February 23, 2023
"After four years we were able to see in a concrete way what happened, the changes that we have been able to do for the organization."
Benjamin RealMaturity Models: A Core Tool for Creating a DesignOps Strategy
October 1, 2021
"Decades worth of agricultural experimental data was garbage because of poor experimental design."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
"Early enthusiasm fades; succession planning is key to keeping communities alive."
James LangIf you can design an app, you can design a community
May 22, 2025
