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.
Design Systems for Us: How Many One-Source(s)-of-Truth Are Enough?
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
"Managers were asking for user stories but hadn’t done any analysis or design — they didn’t understand the scope."
Carl TurnerYou Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
March 28, 2023
"Most employees take at least 90 days to onboard and another 90 days to become productive — that’s half a year before you see impact."
Karen PascoeDeveloping Experience Teams and Talent in the Enterprise
June 8, 2016
"Support software used to be really shitty and expensive, and Zendesk set out to fix that by making it beautifully simple."
Jilanna WilsonDistributed Design Operations Management
October 23, 2019
"A government designer aims to reduce UX variation while a contractor may optimize only their single product, creating potential conflicts."
Shawna Hein Kevin HoffmanCreate a Cohesive Civic Design Practice Across Agency, Vendors, and Contracts
November 17, 2022
"I still kind of pause in my tracks when I see our corporate vision: a world without fear of cancer."
Barb SpantonDoing Work That Matters: A Look Beyond The Idealistic Notion of 'Doing Meaningful Work'
June 10, 2022
"We had no recipe, no formula, just vibes."
Briana ThomasThe Quiet Force: Uncovering Hidden Leadership in High-Impact Design Teams
September 24, 2024
"Therapists create space for clients to reflect and discover insights in a safe environment."
Gina MendoliaTherapists, Coaches, and Grandmas: Techniques for Service Design in Complex Systems
December 3, 2024
"UX researchers should learn Python or R and how to leverage AI APIs to process unstructured data."
Lija Hogan Milan Mijatovic Sam Proulx Louis RosenfeldThree Years Out: Perspectives on the Near-Term Future of User Research
March 15, 2024
"Design ops is always swinging wildly between priorities, making partners wonder why invest if you’re always going this way or that."
John Calhoun Rachel PosmanTwo Sides of the DesignOps Coin: Teams Ops and Product Ops
January 8, 2024
