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
"The persona of a goalkeeper is helping to triage and prioritize strategy and work for the executive."
Isaac HeyveldExpand DesignOps Leadership as a Chief of Staff
September 8, 2022
"If you build for the next model, even if it can hardly do something now, it will probably do it well in the future."
Peter Van DijckHands on AI #3: Claude Code for UX people
October 22, 2025
"The higher up you are in an organization, the more distorted your reality is likely to be."
Dave GrayLiminal Thinking: Sense-making for systems in large organizations
May 14, 2015
"Bringing people with disabilities into ideation and prototyping helps build accessibility by design and eliminates costly retrofits."
Sam ProulxAccessibility: An Opportunity to Innovate
June 8, 2022
"Turning generalists into specialists starts by understanding what they’re good at and what motivates them."
Wendy JohanssonAn Education on Design Education for Orgs
June 10, 2021
"Learning is a marathon, not a sprint, especially in the context of online conferences."
Bria Alexander Louis RosenfeldWelcome
January 8, 2024
"Can we just hang out, get on the tube, and hang out at Heathrow? He looked at me very strangely."
Stephen PollardClosing Keynote: Getting giants to dance - what can we learn from designing large and complex public infrastructure?
November 7, 2017
"Designers are theorists whether they realize it or not — they create solutions that have intended and unintended consequences."
Uday Gajendar Adam RichardsonFrom AI to Zeitgeist: Theory as the design antidote to AI hype
March 27, 2025
"There’s no good answer yet for how to resolve the inequities created by differential access to digital technology."
Leah BuleyClosing Plenary: The Crisis of Digital
March 31, 2020
Latest Books All books
Dig deeper with the Rosenbot
How can I leverage my professional network to find consulting or fractional leadership opportunities?
Why do job descriptions for UX research lag behind actual AI-influenced work and how to address that?
What challenges do proprietary AI companies pose for compatibility and user experience consistency?