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
"Operational success cannot always be quantified through numbers; people are messy and complicated."
Amy ThibodeauOpening Keynote: Process and Ambiguity
October 23, 2019
"Managers were asking for user stories but hadn’t done any analysis or design — they didn’t understand the scope."
Carl TurnerYou Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
March 28, 2023
"Rank your information physically from most important to least important to gain clarity."
Bruce GillespieLearning from journalism: Balancing impactful communication with compassionate storytelling
March 13, 2025
"Product managers often see design work as a black box and want transparency and accountability."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
"Drag and drop ease, and collaborative affinity diagramming in the tool, were unexpected but very welcome advantages."
Taylor Jennings Joe Nelson Alex KnollRepository Retrospective: Learnings from Introducing a Central Place for UX Research
March 9, 2022
"If patients stop using the app because they’ve got their health under control, that’s like a dating app success — they got married, not that the app failed."
Daniel J. RosenbergDigital Medicine Design
September 26, 2019
"UX is more than UI; it's the entire product, including marketing, documentation, and architecture."
Jack MoffettUX Metrics That Matter and The Future of our Design at Scale Conference: A Community Conversation
September 22, 2022
"Vibe coding turns the conversation 'should designers code?' on its head — now designers can just talk to bots."
Christian CrumlishThe Pygmalion Effect: In Which a Vibe Coding Experiment Becomes a Million Lines…
August 14, 2025
"We aimed for a fifth grade reading level to make materials accessible."
Alexia Cohen Adriane AckermanIncreasing Health Equity and Improving the Service Experience for Under-Served Latine Communities in Arizona
December 4, 2024
