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 talk centers on the Salesforce Lightning Design System and highlights how its success was driven by an organizational approach rather than just technological solutions. The speaker, who has a background in sociology, shares insights from interviews with various stakeholders within Salesforce to reveal three core themes: addressing user needs, cultivating trust, and proactive sharing. The implementation started as a grassroots, scrappy initiative driven by designers addressing real problems faced by customers and internal teams alike. Instead of a top-down approach, it evolved through collaboration, trust-building, and a culture of sharing and feedback. This involved recognizing internal conflicts between design and development, improving communication, and introducing effective design principles. The speaker concludes by addressing the challenges of managing rapid adoption and the future of design systems at Salesforce.

Key Insights

  • The Lightning Design System's success hinged on addressing real user problems rather than just system-wide issues.

  • Trust is crucial in collaborative environments, allowing teams to communicate effectively and resolve conflicts.

  • Sharing knowledge and progress with the entire organization fosters engagement and helps iterate on design systems faster.

  • Proactive feedback loops helped refine the design system by actively listening to criticism from developers and users.

  • A grassroots approach in initiating the design system outlined the importance of solving immediate, practical concerns first.

  • Evaluating design system functionality through traditional user research ensures practical usability before public release.

  • Bridging the gap between design intent and development execution was a key challenge addressed by the design system.

  • Salesforce's culture of transparency and sharing enhanced the internal understanding and adoption of the design system.

  • The use of design tokens streamlines processes and builds trust in design consistency and implementation.

  • Innovation often arises from solving specific internal and external organizational problems rather than broad, abstract challenges.

Notable Quotes

"I'm exceptionally qualified to talk about design systems because I've never used one."

"The birth of the design system at Salesforce was not a top-down event."

"We didn't foresee the adoption, both internally and externally."

"Trust in people and cultivate trust is what people needed to do."

"Building components quickly created living conversations."

"The challenge of managing the incredibly fast rate of adoption is ongoing."

"Making it open source established us as a community member."

"We need to address people's needs to initiate change."

"We are seen as the standard bearer of what the experience should be like for our customers."

"Design systems are only getting traction now and taking various forms."

More Videos