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 modeled as multi-tiered ecosystems rather than monoliths to manage scale and complexity effectively.
-
•
Adoption varies widely; some products embed design without using the system code, leading to inconsistency and fragile connections.
-
•
Successful design systems generate three outputs: design assets, component code, and comprehensive documentation.
-
•
Separation of design assets and code repositories is sometimes necessary due to diverse frameworks and product needs.
-
•
Acquisitions introduce brand and system fragmentation requiring strategic alignment and often dual system coexistence.
-
•
Generational upgrades of design systems incur high cost and complexity, often delaying adoption of new versions.
-
•
Descendant systems allow subsidiary teams to extend or override components, balancing consistency with localized needs.
-
•
Organizational tribalism results in siloed design systems tied to business units, complicating enterprise-wide convergence.
-
•
Effective governance involves ongoing onboarding, support, and negotiation of appropriate variation boundaries.
-
•
Involving content strategists and brand teams early is critical for embedding content, tone, and identity into design systems.
Notable Quotes
"Design systems are information products as much as they are code or UI."
"One source of truth is the ideal, but reality often has many systems operating in parallel."
"Not every product will adopt the system fully; some embed the design manually in their own code."
"Separating design and code can be a don't unless justified by framework diversity or scale."
"Acquisition success starts by engaging brand teams, not jumping straight to migration analysis."
"A design system isn’t a single big thing to adopt or reject; it’s an architecture with rooms for subgroups."
"Allowing controlled overrides like color changes can be justified if it meets localized business goals."
"Banks are among the hardest enterprises to unify under a design system because they move deliberately slow."
"Onboarding speed and success are critical to developer adoption and overall system health."
"Creating one adopted component can be harder than creating 100 that go unused."
Dig deeper—ask the Rosenbot:
















More Videos

"Small anchors really add up, both culturally and tangibly, in what you build together."
Scott Jensen Sarah Delaney Carmen LiuShort Take #2: UX/Product Lessons from Your Industry Peers
December 6, 2022

"The challenges we faced last year require us to take responsibility when designing systems for millions of people."
Lada GorlenkoTheme 3: Introduction
June 10, 2021

"Having formal backup tools like Google Meet or phone calls ready is essential because technical failures will happen."
Sarah RinkRemote User Research: Dos and Don'ts from the Virtual Field (Videoconference)
June 11, 2020

"Even what we think of as service design is highly trained and pointed right at digital now and into the future."
Leah BuleyClosing Plenary: The Crisis of Digital
March 31, 2020

"Navigating inherent conflict that arises between many stakeholders is a key part of Civic design."
Ariel KennanTheme Two Intro
November 17, 2022

"Collaboration between spheres of education and technology is key to innovation."
Lena ShenkarenkoCollaborative Wireframing for Creating Team Alignment and Shipping Better Products
October 21, 2020

"Go home and find a way to do it where you’re from; don’t come here to Thailand."
Amy Brana StuartRest in Peace Fly-in-fly-out Design
June 9, 2022

"I realized my superpower was facilitating conversations cross-functionally to lead to better outcomes."
Christian Crumlish Aditi Ruiz Johanna Kollmann Catt SmallMorning Insights Panel
December 6, 2022

"If CTAs and tasks are easy to perform, people are much more likely to do them."
Michael WeirMixed Methods and Behavioural Science (Videoconference)
May 26, 2023