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
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
"Stop watching this video, give it a spin, check out the link below."
Louis RosenfeldAbout the Rosenverse
March 15, 2026
"Ethical technology governance means anticipating the long-term social impacts of technology today and acting to protect essential public goods."
Ilana LipsettAnticipating Risk, Regulating Tech: A Playbook for Ethical Technology Governance
December 10, 2021
"AI and automation have meaningfully raised the bar for how I operate as an ops."
Aletheia DelivreNew Shapes and Emerging Identities for Design Ops
September 11, 2025
"Some designers forget to stop the Toggl timer, which skews data but is easy to spot and correct."
Kristin Sundermeyer Tygre MorehartDesign Ops Metrics
September 30, 2021
"Slack is the way you ask questions to the speakers, and it’s where most of the community interaction happens."
Bria AlexanderOpening Remarks
March 28, 2023
"The Cheesecake Factory has basically cracked the code across what I am deeming four tenets of standardization at scale: quality, scope, velocity, and craft."
Candace MyersStandardizing Design at Scale
September 9, 2022
"I was much more interested in talking to clients, understanding the scope, and translating that into what designers would build."
Courtney KaplanTaking it to the next level: Career paths in DesignOps
November 8, 2018
"The future is researchers painting the larger picture while PMs and designers focus on deep, tactical user insights."
Mike OrenImproving Democratized Research with CustomGPTs and Gems
February 25, 2026
"At NASA, we had to start AI readiness strategy with workshops led by David Salvinini, the chief artificial intelligence officer."
Erika FlowersThe Handoff is Dead: Design-Led Engineering with AI Agents
March 4, 2026
