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

In this talk, Rebecca explains her unique perspective on design systems from a sociological standpoint, having never directly used one but deeply studying people's interactions with technology at Salesforce. She describes Salesforce's evolution from a CRM to a broad customer success platform and how their Lightning Design System was born amid a company-wide UI overhaul called Lightning. Instead of a top-down directive, the design system emerged from a scrappy, grassroots team addressing concrete problems faced by customers, partners, engineers, and designers. Rebecca emphasizes the core themes that led to success: solving real people’s problems (like reducing the CSS friction for engineers and maintaining design fidelity), cultivating trust across disciplines using shared design principles and transparent communication, and relentless sharing through various means like brown bags, documentation, and Salesforce’s Trailhead learning platform. She highlights that the design system helped UX gain a stronger organizational voice within Salesforce. Looking ahead, Rebecca notes challenges in scaling adoption and experimenting with user research to improve the system further. The talk underscores the importance of relationships, trust, and communication over just technology when implementing a design system.

Key Insights

  • Salesforce's Lightning Design System was not a top-down initiative but grew organically from a scrappy grassroots team effort.

  • Addressing concrete user problems — such as reducing the CSS workload for engineers — was key to the design system's adoption.

  • The biggest internal challenge before SLDS was the gap between what designers created and what developers actually built.

  • Trust was cultivated through shared design principles like clarity, efficiency, consistency, and beauty, facilitating better cross-team communication.

  • Design tokens built initially for the Salesforce mobile app (S1) helped establish trust and consistency in the design system.

  • Demonstrating working living components early accelerated buy-in more effectively than just documentation or talking.

  • Relentless sharing using internal tools (Slack, town halls), external tools (Trailhead), and open source enabled both internal and external engagement.

  • Salesforce’s culture of transparency and willingness to receive, respond to, and integrate feedback was crucial to the system's refinement.

  • The design system empowered the UX team to have a meaningful seat at the organizational decision-making table.

  • Scaling adoption across a rapidly growing company requires partner experts in different product areas contributing back to the design system.

Notable Quotes

"I’m exceptionally qualified to talk about design systems because I never used one before."

"The success of the Lightning Design System was about people and relationships, not just technology."

"The biggest internal problem was the gap between what designers designed and what actually got built."

"Engineers want to write back-end code, not mess with CSS — CSS is a bear."

"It was the easiest win-win: take away what engineers don’t want to deal with and make their life easier."

"We built living components fast to show, not tell, and that accelerated conversation and buy-in."

"We learned that customers and partners were reverse engineering our CSS to make their products look like Salesforce."

"Trust comes from having design principles that give us a way to have less ‘I want it this way’ arguments and more about user experience."

"Making the design system open source put Salesforce’s UX team on the map representing our company."

"The design system helped UX get a seat at the table — not right next to the CEO, but definitely in the room."

Ask the Rosenbot
Alissa Briggs
How to Coach Enterprise Experimentation
2015 • Enterprise UX 2015
Gold
Megan Blocker
What UX research maturity looks like and how we get there [Advancing Research Community Workshop Series] (Videoconference)
2023 • Advancing Research Community
Maria Skaaden
Continuous Design: One eye on the horizon and the other on the next wave
2018 • DesignOps Summit 2018
Gold
Carol Smith
Operationalizing Responsible, Human-Centered AI
2023 • Enterprise UX 2023
Gold
Isaac Heyveld
Expand DesignOps Leadership as a Chief of Staff
2022 • DesignOps Summit 2022
Gold
Louis Rosenfeld
Coffee with Lou: Should You Write a (UX) Book? (Videoconference)
2024 • Rosenfeld Community
Shanti Mathew
Civic Design at Scale: Introducing the Public Policy Layer Cake
2021 • Civic Design 2021
Gold
Alnie Figueroa
Teamwork: Strategies for Effective Collaboration with Other Program Management Teams
2022 • DesignOps Summit 2022
Gold
Kate Koch
Flex Your Super Powers: When a Design Ops Team Scales to Power CX
2021 • DesignOps Summit 2021
Gold
Indi Young
Thinking styles: Mend hidden cracks in your market
2025 • Rosenfeld Community
Peter Merholz
Customer-Centered Design Organizations
2017 • Enterprise Experience 2017
Gold
Adam Cutler
People + Places + Practices = Outcomes
2016 • Enterprise UX 2016
Gold
Melissa Schmidt
How UX Research Hit It Big in Las Vegas
2019 • Enterprise Experience 2019
Gold
Jose Coronado
From Zero to Hero
2022 • DesignOps Summit 2022
Gold
Victor Udoewa
Theme One Intro
2023 • Advancing Research 2023
Gold
Laureen Kattan
Centering Patients and Clinicians in a Complex Government Ecosystem
2023 • Design in Product 2023
Gold

More Videos

"Designers rarely take the time to self-reflect, but visual tools help engage them in the process."

Shaping design, designers and teams

November 8, 2018

Sabrina Mach

"A hackathon with designers, developers, business and architects can accelerate UI coded component delivery."

Sabrina Mach Nina Wainwright

How to Design Your Design Operating Model

September 29, 2021

Samuel Proulx

"Disability isn’t a problem with a person; it’s something that happens when we fail to enable them."

Samuel Proulx

Invisible barriers: Why accessible service design can’t be an afterthought

December 3, 2024

Saara Kamppari-Miller

"Nothing about us without us is the mantra we are embracing when doing our inclusive design operations."

Saara Kamppari-Miller

DesignOps for Inclusive Design and Accessibility (Videoconference)

May 26, 2022

Briana Thomas

"We didn’t chase shiny objects; we gave creatives access to tools to inspire the future of creativity."

Briana Thomas

The Quiet Force: Uncovering Hidden Leadership in High-Impact Design Teams

September 24, 2024

Adam Cutler

"The 1500 are designers, we don't distinguish strictly between UX or visual or industrial—they all bring design to the org."

Adam Cutler Karen Pascoe Ian Swinson Susan Worthman

Discussion

June 8, 2016

"Designers can focus on designing and developers can focus on developing — people are getting paid to do their jobs now."

Operationalizing DesignOps

November 7, 2018

Leah Buley

"This is not brain cancer. Nobody dies if we get it wrong — the worst is taking a different approach."

Leah Buley Joe Natoli

Ask Me Anything with Leah Buley and Joe Natoli, co-authors of The User Experience Team of One (2nd edition)

October 8, 2024

Nathan Shedroff

"Rather than aiming for the chief strategy officer directly, build relationships with junior strategists who are more accessible."

Nathan Shedroff

Double Your Mileage: Use Your Research Strategically

March 31, 2020