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
"Why do designers decide how to design this? How do we wean design's addiction from whiteness?"
George AyeThat Quiet Little Voice: When Design and Ethics Collide
November 16, 2022
"We mapped every individual journey on Google Earth attaching quotations and photographs to each location to represent human experiences."
Xenia Adjoubei Sean BruceEmpowering Communities Through the Researcher in Residence Program
March 29, 2023
"When you get a best in class tool, you are able to execute more rigorous research and show clearer ROI."
Benjamin Wiedmaier Annie MayfieldRedefining Toolkits: Unbundling to Create a Perfect Match
March 11, 2025
"Impact evaluation is where organizations struggle the most, partly because metrics often don’t fit design’s multifaceted value."
John DevanneyThe Design Management Office
November 6, 2017
"Finding allies within an enterprise and demonstrating success is how you get a foothold for experimentation culture."
Steve Sanderson Alissa Briggs Jeff Gothelf Bill ScottDiscussion
May 14, 2015
"In the enterprise space, the UX function is added later. It’s not part of the company’s original DNA."
Jemma AhmedTheme 2 Intro
January 8, 2024
"The more senior you become, the more focus shifts from methodology to interpersonal qualities like empathy and bravery."
Megan KiersteadYou Are a Badass at UX: Overcoming Imposter Syndrome
March 10, 2021
"We capture component design decisions and health transparently with checklists; unchecked items correspond to open tickets for prioritization."
PJ Buddhari Nate BaldwinMeet Spectrum, Adobe’s Design System
June 9, 2021
"The ethics in community design are critical — emotional damage can be severe if mishandled."
James LangIf you can design an app, you can design a community
May 22, 2025
