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
"What would it look like if we could ask, how do I make this the absolute best environment for complex problem solving, instead of how do I take away all the annoying hard problems?"
John CutlerThe Alignment Trap
November 29, 2023
"Our mission is to empower everybody to learn; not the few learning on behalf of the many."
Monty HammontreeThe Future of UX Research
December 3, 2020
"We created advocacy networks that allowed directional communication and peer-to-peer sharing of how roles would change."
Matt StoneScaling Empathy, A Case Study in Change Management
June 11, 2021
"We found a three percent decrease in time to market using our design system, which translates into measurable business savings."
Gonzalo GoyanesDesign ROI: Cover a Little, Get a Lot
September 8, 2022
"Commercial buyers evaluate products primarily on needs first; certifications like Energy Star are bonuses."
Amy ParnessScaling Sustainability: Complementary strategies that drive long-term success
May 29, 2025
"We heard from the community through surveys which helped us understand what you hope to see at this year's Design Ops Summit."
Alana WashingtonTheme 3 Intro
October 1, 2021
"Speed is not everything we need velocity—speed plus direction is key."
Patrizia BertiniDesigning Within the Lines: How the EU AI Act Can Spark Better AI Innovation
December 11, 2025
"If you’re not okay as a researcher, the interview won’t be okay."
Jane Reid Janice HannawaySelf-care in User Research
April 2, 2020
"Don’t just think about design systems as an artifact but as a living ecosystem connecting people, tools, and products."
Nathan CurtisBeyond the Toolkit: Spreading a System Across People & Products
June 9, 2016
