Discussion
Summary
During the talk, panelists Nathan, Don, and Nalini explored the multifaceted challenges and strategies involved in creating and scaling design systems within organizations. Don reflected on how at Intuit their design system journey started from backend engineering, demonstrating the importance of organizational alignment and addressing legacy technologies. Nalini shared insights from interviewing non-adopters, identifying engineering resistance often rooted in power dynamics rather than process inefficiency, and emphasized the importance of repeated demonstration of benefits to overcome such resistance. Nathan highlighted engaging creative UI designers by framing design systems as enabling rather than constraining, encouraging contribution and shared ownership. They also discussed the difficulties in maintaining consistency across platforms like iOS, Android, and web through extensible systems that balance shared elements and necessary divergences. Questions of product lifecycle, ROI justification, and system evolution surfaced, with the panelists agreeing design systems are living products that require ongoing stewardship, evolving with business and user needs. Key success factors include embedding accessibility, making the system the single source of truth via code, and providing ongoing support such as office hours, which transform the system from static documentation to an active design culture. Throughout, the dialogue emphasized the necessity of a collaborative boundary between design and development, the challenge of navigating subjective principles like beauty versus clarity, and how to communicate design system value effectively to leaders.
Key Insights
-
•
Engineering non-adopters often resist design systems due to power dynamics rather than efficiency concerns.
-
•
Design systems frequently emerge from backend engineering efforts aiming to reduce repetition and improve reuse.
-
•
Legacy technology can be a major roadblock to adopting design systems, sometimes requiring costly re-architecture.
-
•
Making the design system a single source of truth embedded in code prevents drifting from standards and ensures adoption.
-
•
Framing design systems as enabling tools rather than constraints helps engage highly creative UI designers.
-
•
Design systems must account for platform-specific divergences while maintaining a cohesive shared core.
-
•
Design principles are interpretive and should guide conversations rather than dictate absolute rules.
-
•
Success in design systems requires treating them as living products with ongoing maintenance, not one-off projects.
-
•
Accessibility baked into design systems becomes a strong motivator for organizational adoption and compliance.
-
•
Supporting users with mechanisms like studio office hours helps translate design systems into practical design solutions.
Notable Quotes
"Almost all the non-adopters were in engineering. They were the haters, interested in power within the organization more than efficiency."
"If your organization is healthy, the haters pretty quickly get marginalized."
"A pattern library is not a design system. Relying on documentation alone leads to inconsistency and erosion over time."
"Design systems are an investment in the future; re-architecture today pays dividends in nimbleness tomorrow."
"I try to position the system as an enabling force for designers to succeed better, not as confines or limits."
"Design principles have to be guiding ways and opportunities for conversations, not a strict scorecard."
"The design system is a living, breathing thing that should constantly evolve based on learning and user needs."
"The boundary between design and development must open up; I ask if designers can make pull requests to code."
"We get accessibility baked in, so if you use the design system properly, you pretty much guarantee compliance."
"When I heard ‘when are you going to be done?’ my answer is it’s never really done if you do it well."
Or choose a question:
More Videos
"Always design a thing by considering it in this next largest temporal context — a day in a month, a decade in a century."
Sarah Auslander Betsy Ramaccia Gordon RossInsights Panel
November 18, 2022
"It is very important to be aware of augmentations because otherwise they can feel very intrusive to the user."
Lukas Moro“Feels Like Paper!”: Interfacing AI through Paper
June 11, 2025
"Design and research at Compass have become so integrated that we become these powerful partners driving the product vision."
Andreas Huebner Amy Takata Craig BrookesWhat Is It Like To Be Part of The UX Team at Compass?
March 11, 2021
"We were lost in the forest and you come across this compass, maybe all time rusty, but still something a little bit useful."
Benjamin RealMaturity Models: A Core Tool for Creating a DesignOps Strategy
October 1, 2021
"Remote work can uplift psychological safety through flexibility, or erode it if in-person connection is lost."
Alla WeinbergDesign Teams Need Psychological Safety: Here’s How to Create It
September 8, 2022
"When hiring, we want candidates who know the product well — both what works and what doesn’t."
Meredith BlackScaling Design Culture
November 6, 2017
"There’s no good or bad data, there’s how you use it and how you come together to create shared understanding."
Jill FruchterInconvenient Insights: The Researcher's Role is to Stay Curious
March 29, 2023
"You don't want to hide away for six months and try to build the perfect documentation. It won't work."
Gabrielle VerderberDocumentation Your Team Will Actually Use
October 3, 2023
"Now a year later, the landscape is completely different with dozens of new AI design tools for all stages."
Llewyn PaineDay 1 Using AI in UX with Impact
June 10, 2025
Latest Books All books
Dig deeper with the Rosenbot
Why is the absence of self-governing professional institutions a challenge for the design field?
What historical precedents can help us understand current wealth concentration and potential progressive responses?
How can AI personas help UX design teams prepare before subject matter experts are available?