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
"By observing Jeff's concerns and asking questions, I was able to show empathy and distract myself from getting defensive."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"Friction in a situation can cause a person to switch thinking styles, not personality types."
Indi YoungThinking styles: Mend hidden cracks in your market
January 8, 2025
"I want you to have the best time possible and bring your fullest self to our conference today."
Louis Rosenfeld Bria AlexanderDay 1 Welcome
September 23, 2024
"Some of the same things that help you scale can also feel like they get in your way."
Melissa Schmidt Adam MenterHow UX Research Hit It Big in Las Vegas
June 4, 2019
"Shared outcomes and shared goals are critical to any measurement initiative."
Kristin Skinner Kamdyn Moore8 Types of Measures in Design Operations
April 16, 2020
"If research findings aren’t connected to action, then you’re just planning and not actually doing strategy."
Dave HoraAdvice for Establishing Research
December 8, 2022
"We treated the different types of information about jobs as transparency layers, like in an anatomy textbook."
Sean Fitzell Sarah Han Kayla FarrellCraft of User Research: Building Out Jobs to be Done Maps
March 12, 2021
"People rarely spend time to self reflect, but visual tools help engage them."
Jason MesutShaping design, designers and teams
November 8, 2018
"Employees with exceptional onboarding are 2.6 times more likely to be extremely satisfied with their workplace."
Dante GuintuHow to Crush the Talent Crunch
September 8, 2022
Latest Books All books
Dig deeper with the Rosenbot
How does Sentient Design suggest balancing AI-generated content flexibility with consistent user experience?
What does the builder team model with AI in the loop look like compared to traditional product teams?
How have historic social contracts marginalized Black Americans compared to white Americans?