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
"Nobody’s gonna listen to you people until you start speaking in the language of business."
Mark Interrante Harry MaxAI for Prioritization (3rd of 3 seminars)
July 11, 2024
"Building product today is getting more and more complex, and organizations desperately need professionals who speak compliance and product."
Patrizia BertiniThe (r)evolution of designOps: It’s Time to Think (really) BIG
September 11, 2025
"A tree test focuses on intuitive navigation while a prototype aims for the desired modality of an end solution."
Shan ShenTranslating UX Terms into Business Contexts
November 29, 2023
"Everyone has a plan until they get punched in the mouth, said Mike Tyson."
Adam ThomasSurvival Metrics – Making Change in a Fast, Data-Informed, and Politically Safe Way
December 6, 2022
"The Business Roundtable radically redefined the purpose of a corporation — it’s to promote an economy that serves all Americans, not just shareholders."
Robin BeersResearch as a Catalyst for Organizational Transformation
March 12, 2021
"Accessibility isn’t just about visible disabilities; it’s about invisible disabilities and situational impairments too."
Sheri Byrne-HaberAccessibility at Scale
June 9, 2021
"Design shares are more about presenting finished work and practice defending it, not about peer-to-peer feedback."
Joseph MeersmanSweating the Pixel: Scaling Quality through Critique
June 10, 2021
"Don't reinvent the wheel all the time; build on top of what others have built."
Deanna Washington Bria Alexander Jon Fukuda Saara Kamppari-Miller Farid SabitovConnecting the Ops: Plenary Panel and Closing Circle
September 9, 2022
"We have the responsibility to redistribute our power and include those who have a stake in the work we do."
Aaron Stienstra Lashanda HodgeLeveraging Civic Design to Advance Equity and Rebuild Trust in the US Federal Government
December 8, 2021
Latest Books All books
Dig deeper with the Rosenbot
What unique features does the Rosenbot chatbot provide for UX learners?
What are the core UX research tools essential for managing participant recruitment and study logistics in large companies?
Why is assessing design students challenging, and what are the limitations of traditional grading systems?