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
"When fellow co-workers label an individual as difficult, it's hard not to treat that individual as a problem."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"Customer experience cannot truly be good if some are left out or excluded, either intentionally or unintentionally."
Aaron Stienstra Lashanda HodgeLeveraging Civic Design to Advance Equity and Rebuild Trust in the US Federal Government
December 8, 2021
"Trying something new can feel very daunting, especially if you rarely interact with people who use assistive technology."
Kavana RameshMeaningful inclusion: Practicing accessibility research with confidence
September 24, 2024
"AI has no understanding of consequences — humans are the ones to bring that understanding."
Helen ArmstrongAugment the Human. Interrogate the System.
June 7, 2023
"You don’t need to be an expert in math to start making connections between math and UX."
Scott PlewesWhy Isn't Your UX Approach Going Viral?: A Mathematical Model
March 28, 2023
"Profit making and shareholder value have been a huge part of the problem if we want a sustainable world."
Christian BasonExpand—Rethinking Design for Public Challenges
September 14, 2022
"Context design and context engineering mean figuring out and building what needs to go into that text file sent to the model."
Peter Van DijckBuilding impactful AI products for design and product leaders, Part 3: Understand AI architectures: RAG, Agents, Oh My!
July 30, 2025
"AI doesn’t have a body or sensory experience, so it can’t replace human contextual understanding in research."
Soma Ghosh Savina Hawkins Dave Hoffer Rob Thomas Victor UdoewaWhat emerging methods are advancing UX research [Advancing Research Community Workshop Series]
September 28, 2023
"You have to deliberately quiet that noise in your head and focus on humans in a world of humans."
Steve Portigal Susan Simon-Daniels Tamara Hale Randolph Duke IIWar Stories LIVE! Q&A-Discussion
March 30, 2020
