Summary
In this talk, Rebecca explains her unique perspective on design systems from a sociological standpoint, having never directly used one but deeply studying people's interactions with technology at Salesforce. She describes Salesforce's evolution from a CRM to a broad customer success platform and how their Lightning Design System was born amid a company-wide UI overhaul called Lightning. Instead of a top-down directive, the design system emerged from a scrappy, grassroots team addressing concrete problems faced by customers, partners, engineers, and designers. Rebecca emphasizes the core themes that led to success: solving real people’s problems (like reducing the CSS friction for engineers and maintaining design fidelity), cultivating trust across disciplines using shared design principles and transparent communication, and relentless sharing through various means like brown bags, documentation, and Salesforce’s Trailhead learning platform. She highlights that the design system helped UX gain a stronger organizational voice within Salesforce. Looking ahead, Rebecca notes challenges in scaling adoption and experimenting with user research to improve the system further. The talk underscores the importance of relationships, trust, and communication over just technology when implementing a design system.
Key Insights
-
•
Salesforce's Lightning Design System was not a top-down initiative but grew organically from a scrappy grassroots team effort.
-
•
Addressing concrete user problems — such as reducing the CSS workload for engineers — was key to the design system's adoption.
-
•
The biggest internal challenge before SLDS was the gap between what designers created and what developers actually built.
-
•
Trust was cultivated through shared design principles like clarity, efficiency, consistency, and beauty, facilitating better cross-team communication.
-
•
Design tokens built initially for the Salesforce mobile app (S1) helped establish trust and consistency in the design system.
-
•
Demonstrating working living components early accelerated buy-in more effectively than just documentation or talking.
-
•
Relentless sharing using internal tools (Slack, town halls), external tools (Trailhead), and open source enabled both internal and external engagement.
-
•
Salesforce’s culture of transparency and willingness to receive, respond to, and integrate feedback was crucial to the system's refinement.
-
•
The design system empowered the UX team to have a meaningful seat at the organizational decision-making table.
-
•
Scaling adoption across a rapidly growing company requires partner experts in different product areas contributing back to the design system.
Notable Quotes
"I’m exceptionally qualified to talk about design systems because I never used one before."
"The success of the Lightning Design System was about people and relationships, not just technology."
"The biggest internal problem was the gap between what designers designed and what actually got built."
"Engineers want to write back-end code, not mess with CSS — CSS is a bear."
"It was the easiest win-win: take away what engineers don’t want to deal with and make their life easier."
"We built living components fast to show, not tell, and that accelerated conversation and buy-in."
"We learned that customers and partners were reverse engineering our CSS to make their products look like Salesforce."
"Trust comes from having design principles that give us a way to have less ‘I want it this way’ arguments and more about user experience."
"Making the design system open source put Salesforce’s UX team on the map representing our company."
"The design system helped UX get a seat at the table — not right next to the CEO, but definitely in the room."
Dig deeper—ask the Rosenbot:
More Videos
"Survey question volume can range from one question to up to 40, but most participants answer around 20 questions."
Wyatt HaymanGlobal Research Panels (Videoconference)
August 8, 2020
"We’re far from done; evolving foundational elements, accessibility, and customization tools will drive Spectrum’s future."
PJ Buddhari Nate BaldwinMeet Spectrum, Adobe’s Design System
June 9, 2021
"Government often moves slowly and struggles to communicate future intent amid short-term sustainability concerns."
Sarah GallimoreInspire Progress with Artifacts from the Future
November 18, 2022
"UX directors often feel like this poor person in the middle here getting pulled in all these directions."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Time poverty is a huge problem for women, especially those from marginalized backgrounds, and researchers must ask how much time they can give."
Dr. Jamika D. Burge Mansi GuptaAdvancing the Inclusion of Womxn in Research Practices (Videoconference)
September 15, 2022
"You have to understand how your company actually makes money."
Amy MarquezINVEST: Discussion
June 15, 2018
"The Pokémon anime was essentially a game manual, walking players through the journey with emotional stakes."
Dane DeSutter Natalie Gedeon Deborah Hendersen Cheryl PlatzBeyond the Console: The rise of the Gamer Experience and how gaming will impact UX Research across industries (Videoconference)
May 17, 2024
"Burnout really exists because we made rest a reward rather than a right."
Zariah CameronReDesigning Wellbeing for Equitable Care in the Workplace
September 23, 2024
"Having ADHD is like having a race car engine for a brain but with the brakes of a bicycle."
Jessica NorrisADHD: A DesignOps Superpower
September 9, 2022
