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
"Senior employees should hold difficult conversations questioning processes that may be harmful to others."
Laine Riley ProkayHow DesignOps can Drive Inclusive Career Ladders for All
September 30, 2021
"Colonial ways of being, knowing, and valuing will never produce emancipatory methodologies."
Victor UdoewaBeyond Methods and Diversity: The Roots of Inclusion
March 26, 2024
"How can machines be our trusted partners in this new world? That’s where human-centered design comes in."
Husani OakleyTheme Three Intro
June 6, 2023
"Without attribution you can’t get funding, and if it’s not funded, it’s not a priority."
Jess GrecoCreating a Basis for Change: Scaling Design Maturity
June 8, 2022
"Research insights should belong to the team, not just the researcher."
Shipra KayanMake your research synthesis speedy and more collaborative using a canvas
January 24, 2025
"If you are building a product for someone, there's always context loss when problem identification and solutioning are done by different teams."
Prayag Narula Abhinav KrishnaDialing for Research: How to Reach the Unreachable
March 10, 2022
"If you falsely think you are having the same experience as a native user, you become afraid of accessibility and say it's impossible."
Sam ProulxUnderstanding Screen Readers on Mobile: How And Why to Learn from Native Users
June 6, 2023
"Async communications helped us reduce emails and meetings, improving overall efficiency."
Amy EvansHow to Create Change
September 25, 2024
"Machine learning is moving so fast that systems can learn whole codgers of content and change how we think about experiences."
Greg PetroffEverything is About to Change: Software as Material
June 8, 2016
