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
"Employees can take as much or as little time off as they want, so long as their job gets done."
Lavy Kumar Kat Temple Shan Sebastian Tara Jensen Jenn ChouFuture of Work
June 9, 2021
"Leadership buy-in now means we get to focus on bigger, generative research questions instead of just tactical usability studies."
Andreas Huebner Amy Takata Craig BrookesWhat Is It Like To Be Part of The UX Team at Compass?
March 11, 2021
"Conjoint analysis reveals how consumers make choices by examining trade-offs they are willing to make."
Ricardo MartinsUnlocking the power of advanced quantitative methods
March 12, 2025
"People will work harder for people than they will for a number."
Monty HammontreeThe Future of UX Research
December 3, 2020
"We didn’t explain the philosophy behind the design ops activities, so others didn’t understand why some activities couldn’t be done outside design."
Benjamin RealShowing the Value of DesignOps by Not Having a DesignOps Team
October 21, 2020
"Research ops is like the most punk thing you can do in the experience design space."
Kate TowseyAsk Me Anything (AMA) with Kate Towsey
April 2, 2025
"The core of it is really putting yourself in that other person’s shoes—it’s basic but essential empathy."
Steve Portigal Chris Chapo Kelly Goto Christian RohrerDiscussion
May 13, 2015
"If it didn’t come from Amazon or Costco, I probably don’t own it because I know the experience will be consistent."
Sam ProulxOnline Shopping: Designing an Accessible Experience
March 28, 2023
"For screen reader users, you often need to build entirely new prototypes using systems like Microsoft Word or Google Docs to convey semantic information."
Sam ProulxPrototype Reviews, People With Disabilities, and You
October 1, 2021
