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
"Scale isn’t just about quantity, it’s about the quality and impact you have on the outcomes of the organization."
Standardizing Product Merits for Leaders, Designers, and Everyone
June 15, 2018
"You can mine metadata from your platform to spot emerging patterns and commoditize new components."
Simon WardleyMaps and Topographical Intelligence (Videoconference)
January 31, 2019
"If you’re in tech, you are in social change, whether you realize it or not."
Sandra CamachoCreating More Bias-Proof Designs
January 22, 2025
"By observing Jeff’s concerns and asking questions, I was able to show empathy and focus on the problem rather than get defensive."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"After each interview, I input the transcript into ChatGPT and ask for three key takeaways that I can quickly share with stakeholders."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"Working with CEOs like Mark Templeton is like Dancing with the Stars — an interpretive dance of translating fuzzy ideas."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"No official kickoff was held, which meant shifting expectations and lack of alignment."
Davis Neable Guy SegalHow to Drive a Design Project When you Don’t Have a Design Team
June 10, 2021
"TripAdvisor is really nine major business units each thinking like sub companies instead of one end-to-end user experience."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Design Ops people want to standardize processes and reuse organizational knowledge for clarity and confidence."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
