Summary
In this talk, panelists including Nathan, Don, and Nalini explore the complexities behind building, adopting, and maintaining design systems in large organizations. Don shares his experience at Salesforce where engineering non-adopters initially resisted design systems due to power dynamics, but the enthusiasm from teams eventually marginalized resistance. Nalini highlights that many design systems originate from backend development teams focused on preventing duplication through modularity, while Nathan emphasizes engaging creative designers by framing design systems as enablers rather than constraints. The panel discusses the challenge of applying design systems across diverse platforms (iOS, Android, web) and how to accommodate platform-specific overrides while maintaining a cohesive experience. They underline the importance of treating design systems as living products that evolve and are never truly “done.” Accessibility baked into design systems is presented as a significant business and compliance win. The speakers caution against solely relying on pattern libraries or documentation without code integration, sharing that a single source of truth in production code prevents deviations over time. They explain how atomic design facilitates organizing components by hierarchy and how teams need tools and cultures that sustain continuous iteration. Finally, they advise pitching ROI by starting small to prove savings and efficiency gains, using metrics like reduced support costs and engineering time spent on CSS fixes, and embedding the system within organizational workflows and culture through activities like studio office hours. Overall, the session offers practical insights into overcoming human, technical, and process roadblocks to make design systems successful and scalable.
Key Insights
-
•
Design system resistance often stems from engineering stakeholders valuing organizational power over efficiency, but healthy cultures marginalize such resistance.
-
•
Many design systems have origins in backend or development teams striving to eliminate duplication through modular, reusable components.
-
•
Engaging talented UI designers requires framing design systems as enablers that empower creative problem-solving rather than constraints.
-
•
Cross-platform design systems need allowances for deliberate platform-specific overrides to respect native conventions while maintaining cohesion.
-
•
Legacy technology can be a major barrier to adoption, and investing in system re-architecture is justified by future efficiency and agility gains.
-
•
A design system must be treated as a living product, continuously evolving rather than a finished artifact.
-
•
Embedding design systems in code with a single source of truth prevents teams from dropping standards or taking shortcuts over time.
-
•
Atomic design is a useful conceptual framework to explain component hierarchy and facilitate collaboration among diverse teams.
-
•
Accessibility built into design systems helps both compliance and business cases, reducing last-minute fixes and rework.
-
•
Running ‘studio office hours’ or collaborative sessions helps sustain design systems by educating users and evolving patterns collaboratively.
Notable Quotes
"Almost all the non-adopters were in engineering — they were more interested in their power within the organization than efficiency for users."
"If your organization is healthy, the haters pretty quickly get marginalized when everyone else is excited about the design system."
"I try to position the system as an enabling force for designers to do their work better and succeed better."
"Sometimes clarity trumps consistency depending on the context or specific use case in the system."
"A pattern library is not a design system — you need the code as a single source of truth to prevent people dropping the ball."
"The design system is a living, breathing thing that evolves constantly because you’re constantly learning and responding to needs."
"When you have a success, measure time saved and reduction in bugs to build your internal business case for the system."
"You have to treat the design system as a product that delivers features and releases over increments, never really done."
"Design principles are guiding tools for conversation rather than strict rules with objective scores."
"Can a designer make a pull request and have it reviewed? That open boundary between design and code is key to unlocking design system potential."
Dig deeper—ask the Rosenbot:
More Videos
"This conference is as much about community as it is about content."
Bria Alexander Louis RosenfeldWelcome
September 8, 2022
"I helped a company save 12 million dollars by not investing in an iris scanner after just one week of research."
Mike OrenWhy Pharmaceutical's Research Model Should Replace Design Thinking
March 28, 2023
"Technology is often blamed, but many issues come from uneven training, misunderstandings, and poor configurations."
Jodi ForlizziDesign and AI innovation
June 5, 2024
"If you ever feel uncomfortable or subjected to bullying, please let us know. It’s very important to keep the vibes positive."
Bria AlexanderOpening Remarks
October 3, 2023
"When cognitive load is high, people blink less because their brain is working harder."
Michael WeirMixed Methods and Behavioural Science (Videoconference)
May 26, 2023
"Success metrics for research marketing are still emerging, but insights traffic and engagement are early indicators."
Molly FargotsteinMultipurpose Communication & UX Research Marketing (Videoconference)
September 12, 2019
"The Silicon Valley dream is not the reality we are living in Latin America in terms of technology, culture, resources, mindset, and people."
Verónica Urzúa Jorge MontielThe B-side of the Research Impact
March 12, 2021
"Enterprise IA focuses on refining information organization across geographies, silos, cultures, languages, and personalities."
Husani OakleyTheme Two Intro
June 6, 2023
"We support data binding so lists and other components can be populated with real content from JSON or CMS."
George Abraham Stefan IvanovDesign Systems To-Go: Reimagining Developer Handoff, and Introducing App Builder (Part 2)
October 1, 2021
