Rosenverse

This video is only accessible to Gold members. Log in or register for a free Gold Trial Account to watch.

Log in Register

Most conference talks are accessible to Gold members, while community videos are generally available to all logged-in members.

An Organizational Story: Salesforce Lightning Design System

Gold
Thursday, June 9, 2016 • Enterprise UX 2016
Share the love for this talk
An Organizational Story: Salesforce Lightning Design System
Speakers: Nalini P. Kotamraju
Link:

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."

Ask the Rosenbot
Jilanna Wilson
Distributed Design Operations Management
2019 • DesignOps Summit 2019
Gold
Marina Martin
Lives on the Line: The Stakes of UX at the Scale of Government
2018 • Enterprise Experience 2018
Gold
Bria Alexander
Theme Two Intro
2022 • DesignOps Summit 2022
Gold
Tristin Oldani
Turning awareness into action with Climate UX
2025 • Climate UX Interest Group
Brigette Metzler
Research Repositories: A global project by the ResearchOps Community
2020 • Advancing Research Community
Bria Alexander
Day 3 Welcome
2024 • DesignOps Summit 2024
Gold
Steve Sanderson
Discussion
2015 • Enterprise UX 2015
Gold
Bria Alexander
Opening Remarks Day 2
2024 • Advancing Research 2024
Gold
Laine Riley Prokay
Carving a Path for Early Career DesignOps Practitioners
2022 • DesignOps Summit 2022
Gold
Erika Flowers
Introduction to MURAL for UX
2021 • Design at Scale 2021
Gold
Ricardo Martins
Unlocking the power of advanced quantitative methods
2025 • Advancing Research 2025
Gold
Ted Neward
Theme 4: Enterprise Organizational Journey
2019 • Enterprise Experience 2019
Gold
Courtney Maya George
Scale Your Organization and Grow Your Designers
2022 • DesignOps Summit 2022
Gold
Sarah Coyle
Design and Analytics with Sarah Coyle
2020 • DesignOps Community
Elizabeth Sklar
Co-creating research enablement with your tech org: a case study
2026 • Advancing Research 2026
Gold
John Mortimer
Panel Discussion
2024 • Advancing Service Design 2024
Gold

More Videos

John Cutler

"You have to go from being able to deliver a message in three bullets and then turn around in the next moment and deliver a massive service blueprint or customer journey."

John Cutler

Oxbows, Rivers, and Estuaries: How to navigate the currents of change (without burning out)

December 3, 2024

Darian Davis

"Taking responsibility for our behaviors starts with an apology and continues with regular feedback and action."

Darian Davis

Lessons from a Toxic Work Relationship

January 8, 2024

Dave Gray

"You don’t have to sit through two hours a day; we’ll spend about 15 minutes on setup then you’ll pair up and do the exercise."

Dave Gray

Group Activity: Making Sense of DesignOps

November 7, 2017

John Cutler

"I never thought I'd say this, but can someone please for love of God, just make a RACI so we can align on who's responsible for things."

John Cutler

The Alignment Trap

November 29, 2023

Abby Covert

"Diagrams help when we feel stuck—providing stability, transparency, understanding, clarity, and kindness."

Abby Covert

Stuck? Diagrams Help

October 27, 2022

Mark Interrante

"Side-pav proposals answer what’s going on, why it matters now, what you propose, what action to take, and what benefit comes from it."

Mark Interrante

Collaboration Flows in Product Development

June 9, 2017

Devon Powers

"If I do a project today on 2025, you’re not going to be in that chair in 2025 and neither am I."

Devon Powers

Imagining Better Futures

March 9, 2022

Prayag Narula

"Bring your research team as note takers and facilitators—they make excellent collaborators and help build feedback loops."

Prayag Narula

How to Empower Your Designers to Do Good Research – And Why You Want To

June 10, 2022

Peter Van Dijck

"You can’t just be a designer adapting UX workflows assuming everybody else’s workflow stays the same; everything is changing with AI."

Peter Van Dijck

Hands on AI #3: Claude Code for UX people

October 22, 2025