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."
Or choose a question:
More Videos
"We had no budget, no backing, but we started looking at competitors and created something ourselves."
Jennifer KanyamibwaCreating the Blueprint: Growing and Building Design Teams
November 8, 2018
"Maintaining a repo often requires 100% manual participation from researchers and that can be hard to enforce and monitor."
Brigette Metzler Dana ChrisfieldResearch Repositories: A global project by the ResearchOps Community (Videoconference)
August 27, 2020
"Taking meeting minutes and assigning action items with director names reduced arguing and helped move things forward."
Carl TurnerYou Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
March 28, 2023
"Gina was closing the dots and shifting perspective from a designer closer to the business."
John Mortimer Milan Guenther Lucy Ellis Patrick QuattlebaumPanel Discussion
December 3, 2024
"Recruiters are often optimized for technical hiring and design is only one percent of the company’s population."
Dante GuintuHow to Crush the Talent Crunch
September 8, 2022
"The new marketing is about preparing users or customers for the new kinds of products that will emerge as time moves forward."
Richard BuchananCreativity and Principles in the Flourishing Enterprise
June 15, 2018
"Sharzad is going to share wisdom earned the hard way from working inside and outside."
Dan WillisTheme 3: Intro
January 8, 2024
"I may have failed, but I am not a failure."
Dan WardFailure Friday #1 with Dan Ward
February 7, 2025
"This is a weird time for research. Layoffs have torn through our field. I've been laid off too."
Chris GeisonTheme Two Intro
March 28, 2023
Dig deeper with the Rosenbot
What mindset shifts are helpful for qualitative researchers moving towards quantitative methods?
How can organizations use thinking styles to better support caregivers with varying cognitive approaches?
How do you identify which data service module to build first when designing a genomic data platform?