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
"A principal has built a boat on their own and rode it around the world—demonstrating autonomy and expertise."
Edward CuppsThe Principal Path: Journeying from Management to Individual Contributor
June 11, 2021
"We need to get really good at strategy board games to outsmart threat actors."
Heidi TrostTo Protect People, You Have to Protect Information: A Human-Centered Design Approach to Cybersecurity
January 23, 2025
"Designer Luna Moore transformed our COVID-19 emails and noticeably changed employee behavior."
Emily Danielson“I mean, I can lift a shovel”: Design Skills in Disaster Response
June 9, 2022
"Imagine a world where the government prototypes and iterates the whole time."
Sofía Delsordo Kassim VeraPublic Policy for Jalisco's Designers to Make Design Matter
December 8, 2021
"I was ready to capture this fatal flaw that this fellow had discovered. It was so horrible it made him sigh. But it wasn’t."
Susan Simon-DanielsWar Stories LIVE! Susan Simon-Daniels
March 30, 2020
"The team was defunded partly because we didn’t engage enough internally to make the case for our work."
Kara KaneCommunities of Practice for Civic Design
April 7, 2022
"Evaluation is vital now because without it, you don’t know if adding a skill or changing a model makes the system better."
Paz PerezContext Architecture for AI systems
September 11, 2026
"If you’re generating buy-in, don’t forget what it will mean for your difficult stakeholders—they may have external pressures you don’t know about."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"One design at scale advisor supports about 12 scrum teams, which is rewarding but cognitively demanding."
Nora Tejeda Giovanna AlonsoScaling Design Capabilities at BBVA Through a Self-service Design Model
June 10, 2021
