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
"It’s our job to see the person in front of us, and if that means having an uncomfortable conversation, have that conversation."
Lin NieWhen Thought-worlds Collide: Collaborating Between Research and Practice
March 10, 2021
"Can you testify right now that all your digital properties are accessible to disabled users?"
Suzan Bednarz Hilary SunderlandAccessibilityOps for All
January 8, 2024
"Data entry is the enemy; automation is the key to making research repositories successful."
Sofia QuinteroThe Product Philosophy Behind EnjoyHQ
March 10, 2021
"Flexibility is not about using the same methodologies; it’s about moving together towards the same goal."
Sol MeszHands or Brains? How to Hire for Strategy, Strategically
January 8, 2024
"Trauma is a response to anything that's overwhelming—too much, too fast, too soon, or too long coupled with a lack of protection or support."
Matt Bernius Sarah Fathallah Hera Hussain Jessica Zéroual-KaraTrauma-informed Research: A Panel Discussion
October 7, 2021
"Grandmas provide grounding, resilience, and long-term perspective often through rituals and storytelling."
Gina MendoliaTherapists, Coaches, and Grandmas: Techniques for Service Design in Complex Systems
December 3, 2024
"Sometimes turning off the camera in interviews helps participants feel more comfortable and open."
Verónica Urzúa Jorge MontielThe B-side of the Research Impact
March 12, 2021
"We need more co-conspirators who actively use their privilege to interrupt microaggressions and bias."
Lisanne NormanWhy I Left Research
March 27, 2023
"Our goal is not to be right, but to make others less wrong and give confidence in design direction."
Ovetta SampsonTurning UX Passion into Real Product Influence
June 7, 2023