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."
Or choose a question:
More Videos
"The time for debate has passed; we need to act decisively and collaboratively."
Alex Hurworth Bonnie John Fahd Arshad Antoine MarinDesigning a Contact Tracing App for Universal Access
October 23, 2020
"Preparation is critical to ensure new employees have everything they need prior to their first day and the first few weeks."
Laine Riley Prokay Lisa GordonCarving a Path for Early Career DesignOps Practitioners
September 9, 2022
"If you come with a big idea, they’ll try to dial you back to the smallest iota you can test first."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"If your budgets don’t connect to strategy goals, maybe those budget items shouldn’t exist."
Nathan ShedroffDouble Your Mileage: Use Your Research Strategically
March 31, 2020
"Accessibility is an ongoing process where we iterate, improve, and expand, and mobile-first makes the journey easier."
Sam ProulxMobile Accessibility: Why Moving Accessibility Beyond the Desktop is Critical in a Mobile-first World
November 17, 2022
"You need clear roles for moderators, note takers, recruiters, and designers in a rapid research program."
Feleesha SterlingBuilding a Rapid Research Program (Videoconference)
May 18, 2023
"We are at an inflection point where what got us here won't get us to a thriving future."
Neil BarrieWidening the Aperture: The Case for Taking a Broader Lens to the Dialogue between Products and Culture
March 25, 2024
"The real question is what is it about delivering the value of design at scale."
John DevanneyThe Design Management Office
November 6, 2017
"It’s not about the specific tool, but about how you expose people to the insights in a way that excites them."
Katy MogalBut Do Your Insights Scale?
March 12, 2021