An Organizational Story: Salesforce Lightning Design System
Summary
The speaker, drawing on sociological research and internal interviews at Salesforce with UX designers, engineers, and executives, explores how the Salesforce Lightning Design System (SLDS) was conceived and successfully adopted. Unlike a typical executive-driven rollout, SLDS began as a scrappy, grassroots initiative by designers tackling concrete problems such as the disconnect between design and implementation, and the complexity of CSS for engineers. Salesforce’s history as a cloud-based CRM expanding into diverse customer success tools contextualizes this effort. The team learned from challenges faced by customers and partners who reverse-engineered Salesforce’s UI to maintain brand consistency. Trust among team members was crucial, fostered through clear design principles (clarity, efficiency, consistency, beauty) and transparent collaboration methods, including an internal “giving a blank” scale to evaluate passion on issues. The team prioritized building live components to demonstrate value instead of just documentation. Sharing via presentations, internal tools, and Salesforce’s Trailhead platform extended adoption beyond the core team, even as rapid scaling created new documentation challenges. Importantly, the design system elevated UX’s organizational role, securing a consistent presence in company decisions. The speaker highlights ongoing experimentation, including using the design system flexibility for user research. They close noting that despite the system’s maturity, no one has fully figured out design systems yet, underscoring an exciting phase for this evolving practice.
Key Insights
-
•
The Salesforce Lightning Design System succeeded primarily due to addressing real problems for people, not just technological innovation.
-
•
SLDS originated as a scrappy grassroots initiative rather than a top-down executive mandate.
-
•
A core internal challenge was bridging the gap between what designers envisioned and what engineers implemented, especially with CSS complexities.
-
•
Trust within the design system team, supported by explicit communication methods like the ‘giving a blank’ scale, was fundamental for productive collaboration.
-
•
Salesforce’s design principles (clarity, efficiency, consistency, beauty) served as a unifying language across teams and stakeholders.
-
•
Building live components early and fast helped the design system team demonstrate value and gain buy-in rather than relying on documentation alone.
-
•
Sharing extensively using internal communications, office hours, and the Trailhead learning platform accelerated adoption inside and outside Salesforce.
-
•
The design system helped unify disparate codebases and acquired companies, preserving brand consistency at scale.
-
•
The existence of the design system strengthened the organizational role of UX, ensuring UX teams have a seat at the decision-making table.
-
•
Ongoing challenges include managing rapid adoption scale and integrating user research creatively using the design system’s flexibility.
Notable Quotes
"I’m exceptionally qualified to talk about design systems because I’ve never used one until recently."
"The success of SLDS is not about the technology itself but about people and relationships."
"The design system started as a scrappy corner initiative of designers doing the right thing."
"Engineers don’t want to mess with CSS; they want to write business logic."
"One of the biggest problems was the gap between what designers designed and what got built."
"Trust was cultivated with design principles like clarity, efficiency, consistency, and beauty serving as a North Star."
"We built living components as conversation starters, showing instead of telling."
"Sharing is hustle — holding brown bags, office hours, town halls, and surveys to get feedback."
"Making the design system open source put Salesforce and the UX team on the map."
"UX now has a seat at the table — maybe not next to the CEO, but definitely in the room — thanks in large part to the design system."
Or choose a question:
More Videos
"Managing up assumes research is below something, but I see advising as partnerships and equals."
Christian MadsbjergInfluencing Strategy
March 31, 2020
"Start every project by asking What about women?"
Mansi GuptaWomen-Centric Research: What, Why, How
March 29, 2023
"We’ve learned that clear communication about roles and process is key to reduce confusion between regular design work and self-service."
Nora Tejeda Giovanna AlonsoScaling Design Capabilities at BBVA Through a Self-service Design Model
June 10, 2021
"Many ethical and practical issues prevent us from conducting longitudinal research with children under 18 in foster care."
Sarah FathallahA Typology of Participation in Participatory Research
March 28, 2023
"Changing people’s relationship with change is key, especially where rules-based culture can stifle innovation and risk-taking."
Alison Rand Sarah BrooksScaling Impact with Service Design
March 25, 2021
"A smaller screen means fewer distractions, making it easier for people with cognitive challenges."
Sam ProulxMobile Accessibility: Why Moving Accessibility Beyond the Desktop is Critical in a Mobile-first World
September 8, 2022
"Genesys includes a fake tool in the software list to stop incentive-driven participants from checking all boxes."
Sydney LawsonAnatomy of a Strong User Panel
March 10, 2026
"Expert intuition can be right or wrong because it relies on cues and heuristics in uncertain contexts."
Kristen Guth, Ph.D.Out of the FOG: A Non-traditional Research Approach to Alignment
March 28, 2023
"The purpose of research is paramount; it guides the choice of methods and how rigorously to apply them."
Sam Ladner Megan Blocker Tanvi Dhond Katie Hansen Ricardo MartinsMethodologies: Beyond the interview [Advancing Research Community Workshop Series]
September 4, 2024
