30
An Organizational Story: Salesforce Lightning Design System Enterprise UX 2016, San Antonio, UX, USA - June 9, 2016 Nalini Kotamraju, Ph.D. Senior Director, User Research & User Experience, Salesforce [email protected] @nkotamraju

An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

Embed Size (px)

Citation preview

Page 1: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

An Organizational Story: Salesforce Lightning Design SystemEnterprise UX 2016, San Antonio, UX, USA - June 9, 2016

Nalini Kotamraju, Ph.D.Senior Director, User Research & User Experience, [email protected]@nkotamraju

Page 2: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

Salesforce. What do they do, again?

Page 3: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

user experience

designers | researchers | prototypers | ux engineers

Page 4: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

Researcher encounters Design Systems !

Design Systems ! CSS ! Framework ! Subclasses !

People ! Relationships ! Organizations ! Politics !

Page 5: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

A good year for Salesforce Lightning Design System

Page 6: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

Why did the Salesforce Lightning Design System Succeed?Question

Page 7: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

It’s not about technologyHint

Page 8: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

It’s about people Answer

Page 9: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

Solving problemsTheme 1

Page 10: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

Solving Problems

Page 11: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

Addressing People’s Needs

Page 12: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

Customer & Partner’s Needs

Page 13: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

Solving problemsAddressing people’s needsTheme 1

Page 14: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

Addressing Salesforce Employee’s Needs

Page 15: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

“Designers were frustrated at the delta between what they envisioned and what actually got built.”

- Salesforce UX Team Member

Page 16: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

“CSS is a bear. Engineers want to write business logic and sexy back-end code. They don’t want to mess with moving stuff around on a screen.”

– Salesforce UX Team Member

Page 17: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

“We removed the gap between what designers want and developers deliver”

- Salesforce UX Team Member

Page 18: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

Trust in people &cultivate people’s trustTheme 2

Page 19: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

Trust in Design

Page 20: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

Trust within the Design Systems Team

Sliding scale of giving a f&*!

Page 21: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

Build on Engineering’s Existing Trust

Page 22: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

Create Trust by Showing (Not Telling)

“Living components were a conversation starter. We built them as quickly as possible. The faster we worked, the more we got done, the better the conversations went.”

- Salesforce UX Team Member

Page 23: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

Share. With people. Lots of people.Theme 3

Page 24: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

Share Often & Document

Brown bags CSS office hours Chatter group Slack channel Town halls Sprint reviews Bug bashes Document. Document. Document.

Page 25: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

“Giving it back to the community. That’s why it’s open source.”

- Salesforce UX Team Member

“Going open source made all the difference.”

- Salesforce Executive

Page 26: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

Sales is in the name.

Page 27: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

Summary

Addressing People’s Needs• Theme 1

Trust in People & Cultivate Trust in People• Theme 2

Share. With People. Lots of People.• Theme 3

Page 28: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

“No one has it all figured out yet.”Design Systems

Page 29: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

thank y u

Page 30: An Organizational Story: Salesforce Lightning Design (Nalini Kotamraju at Enterprise UX 2016)

An Organizational Story: Salesforce Lightning Design SystemEnterprise UX 2016, San Antonio, UX, USA - June 9, 2016

Nalini Kotamraju, Ph.D.Senior Director, User Research & User Experience, [email protected]@nkotamraju