Tweet
Tweet

Slide 1

Slide 1 text

SMASHING CONFERENCE SAN FRANCISCO 04.06.2016 living design systems @JINA LEAD DESIGNER, DESIGN SYSTEMS #designsystem

Slide 2

Slide 2 text

Forward-Looking Statements Statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements. #designsystem

Slide 3

Slide 3 text

user experience #designsystem

Slide 4

Slide 4 text

@salesforceux #designsystem #designsystem

Slide 5

Slide 5 text

@jina LEAD DESIGNER, DESIGN SYSTEMS SALESFORCE #designsystem

Slide 6

Slide 6 text

“It used to be that designers 
 made an object and walked away. Today the emphasis must shift to designing the entire life cycle.” — PAUL SAFFO #designsystem

Slide 7

Slide 7 text

why did salesforce need a design system? #designsystem

Slide 8

Slide 8 text

product design in an enterprise organization can be tricky! #designsystem

Slide 9

Slide 9 text

17
 years of legacy #designsystem

Slide 10

Slide 10 text

20K+
 employees #designsystem

Slide 11

Slide 11 text

lots of products #designsystem

Slide 12

Slide 12 text

sales #designsystem Sales Cloud SalesforceIQ Data.com

Slide 13

Slide 13 text

service Service Cloud Desk.com #designsystem

Slide 14

Slide 14 text

marketing Marketing Cloud Pardot #designsystem

Slide 15

Slide 15 text

community Community Cloud Chatter #designsystem

Slide 16

Slide 16 text

analytics Wave Analytics Wave Apps #designsystem

Slide 17

Slide 17 text

apps App Cloud Force.com Heroku Enterprise #designsystem

Slide 18

Slide 18 text

internet
 of things IoT Cloud Thunder #designsystem

Slide 19

Slide 19 text

lots of
 platforms & devices #designsystem

Slide 20

Slide 20 text

lots of people #designsystem

Slide 21

Slide 21 text

dozens of scrum teams hundreds of developers small team of designers #designsystem

Slide 22

Slide 22 text

design for scale #designsystem

Slide 23

Slide 23 text

design for configuration #designsystem

Slide 24

Slide 24 text

#designsystem

Slide 25

Slide 25 text

#designsystem Where can I find the icons? What color is the button border? Where can I find the icons?

Slide 26

Slide 26 text

redlines? #designsystem

Slide 27

Slide 27 text

#designsystem

Slide 28

Slide 28 text

#designsystem

Slide 29

Slide 29 text

#designsystem

Slide 30

Slide 30 text

#FML #designsystem

Slide 31

Slide 31 text

#designsystem design pages

Slide 32

Slide 32 text

“A fractured process makes for a fractured user experience” — NATE FORTIN #designsystem

Slide 33

Slide 33 text

#designsystem design systems

Slide 34

Slide 34 text

style guides are all
 the rage …and they have come a long way #designsystem

Slide 35

Slide 35 text

styleguides.io #designsystem

Slide 36

Slide 36 text

#designsystem

Slide 37

Slide 37 text

alistapart.com/article/writingainterfacestyleguide

Slide 38

Slide 38 text

brand & design standards front-end standards keep your style guide current & useful #designsystem

Slide 39

Slide 39 text

former salesforce1 style guide

Slide 40

Slide 40 text

#designsystem How do I get my app
 to look like this?

Slide 41

Slide 41 text

#designsystem Can I use the CSS
 in my app?

Slide 42

Slide 42 text

our partners & customers want: to look & feel like salesforce our design guidelines & best practices resources & tools to get it done to keep up with our design iterations to do it the official salesforce way #designsystem

Slide 43

Slide 43 text

trustworthy #designsystem

Slide 44

Slide 44 text

zombie style guides #designsystem

Slide 45

Slide 45 text

it must be living #designsystem

Slide 46

Slide 46 text

“…style guides. Now, it’s design systems. Is this just a change in
 the marketing, or are these 
 things actually different from 
 one another?” — JARED SPOOL
 “BUILDING SCALABLE DESIGN SYSTEMS AND STYLE GUIDES - A UI20 PODCAST WITH NATHAN CURTIS” #designsystem

Slide 47

Slide 47 text

#designsystem

Slide 48

Slide 48 text

lightning experience #designsystem

Slide 49

Slide 49 text

salesforce.com/designsystem

Slide 50

Slide 50 text

consistent with the salesforce lightning UI #designsystem

Slide 51

Slide 51 text

“…great design systems 
 are usable by your 
 entire team.” — MARK OTTO #designsystem

Slide 52

Slide 52 text

medium.com/eightshapes-llc/team-models-for-scaling-a-design-system-2cf9d03be6a0

Slide 53

Slide 53 text

team model #1: solitary a solitary model sees a one team make 
 a system available, but with efforts focused 
 primarily on that team’s needs #designsystem VIA TEAM MODELS FOR SCALING A DESIGN SYSTEM BY NATHAN CURTIS

Slide 54

Slide 54 text

team model #2: centralized a single, central design team produces 
 and supports a system used by others 
 as a part of their job #designsystem VIA TEAM MODELS FOR SCALING A DESIGN SYSTEM BY NATHAN CURTIS

Slide 55

Slide 55 text

team model #3: federated designers from multiple product teams 
 decide on the system together #designsystem VIA TEAM MODELS FOR SCALING A DESIGN SYSTEM BY NATHAN CURTIS

Slide 56

Slide 56 text

medium.com/salesforce-ux/the-salesforce-team-model-for-scaling-a-design-system-d89c2a2d404b

Slide 57

Slide 57 text

a cyclical team model design system informs product design product design informs design system #designsystem

Slide 58

Slide 58 text

our centralized design systems team acts as a librarian, distributor, and facilitator, and we make sure it is maintained and crafted with quality #designsystem

Slide 59

Slide 59 text

our centralized team product design frontend developers (css framework) accessibility visual design ux engineers (infrastructure & distribution) #designsystem

Slide 60

Slide 60 text

our federated design systems contributors distributed throughout the organization keep the Design System accurate, current, & actually useful #designsystem

Slide 61

Slide 61 text

our federated team product & platform designers prototypers researchers additional ux engineers #designsystem

Slide 62

Slide 62 text

“A Design System isn’t a project. It’s a product, serving products.” — NATHAN CURTIS #designsystem

Slide 63

Slide 63 text

to design at salesforce
 is to consider the
 whole ecosystem #designsystem

Slide 64

Slide 64 text

plan with a roadmap #designsystem

Slide 65

Slide 65 text

do user research #designsystem

Slide 66

Slide 66 text

“Design considerations beat design patterns. Test and decide; don’t just copy things like the hamburger icon.” — LUKE WROBLEWSKI #designsystem

Slide 67

Slide 67 text

“While a company is growing fast, there is nothing more important than constant communication and complete alignment.” — MARC BENIOFF #designsystem

Slide 68

Slide 68 text

have a clear vision to
 align efforts #designsystem

Slide 69

Slide 69 text

lists in priority order #designsystem

Slide 70

Slide 70 text

bring designers, engineers, 
 & product managers together around a single goal #designsystem

Slide 71

Slide 71 text

drive design decisions with design principles #designsystem

Slide 72

Slide 72 text

clarity Eliminate ambiguity. Enable people to see, understand, and act 
 with confidence. #designsystem

Slide 73

Slide 73 text

efficiency Streamline and optimize workflows. Intelligently anticipate needs to help people work better, smarter, and faster. #designsystem

Slide 74

Slide 74 text

consistency Create familiarity and strengthen intuition by applying the same solution to the same problem. #designsystem

Slide 75

Slide 75 text

beauty Demonstrate respect for 
 people’s time and attention through thoughtful and 
 elegant craftsmanship. #designsystem

Slide 76

Slide 76 text

UI inventory Audit your UI by categorizing all the different types of components you have, along with their variants. #designsystem

Slide 77

Slide 77 text

#designsystem

Slide 78

Slide 78 text

#designsystem

Slide 79

Slide 79 text

#designsystem

Slide 80

Slide 80 text

standardize
 & consolidate #designsystem

Slide 81

Slide 81 text

take component notes layouts, responsive behaviors, visual differentiation, states, 
 keyboard navigation, usage guidelines, and accessibility requirements #designsystem

Slide 82

Slide 82 text

open-ended questions
 & action items #designsystem

Slide 83

Slide 83 text

list the people involved especially design and engineering leads #designsystem

Slide 84

Slide 84 text

it’s all components #designsystem

Slide 85

Slide 85 text

design patterns & guidelines #designsystem

Slide 86

Slide 86 text

color neutrals #designsystem primaries secondaries

Slide 87

Slide 87 text

visual messaging #designsystem

Slide 88

Slide 88 text

visual differentiation #designsystem

Slide 89

Slide 89 text

visual hierarchy #designsystem

Slide 90

Slide 90 text

accessibility #designsystem

Slide 91

Slide 91 text

localization & internationalization #designsystem

Slide 92

Slide 92 text

“…Creating a positive experience
 is not about having best practices. It’s about putting those practices into the right hands.” — BRENDON CORNWELL #designsystem

Slide 93

Slide 93 text

resources including HTML, CSS, icons, & fonts #designsystem

Slide 94

Slide 94 text

empower designers design & iterate more efficiently in the browser #designsystem

Slide 95

Slide 95 text

how do we maintain consistency across a massive organization? #designsystem

Slide 96

Slide 96 text

how do we make future visual design
 changes faster? #designsystem

Slide 97

Slide 97 text

how do we keep 
 our design
 system agnostic? #designsystem

Slide 98

Slide 98 text

single source of truth #designsystem

Slide 99

Slide 99 text

assets are stored in repository & automatically updated in the app & style guide #designsystem

Slide 100

Slide 100 text

design tokens the basic atoms of the Lightning Design System #designsystem

Slide 101

Slide 101 text

design tokens help us scale design across both web & native applications #designsystem

Slide 102

Slide 102 text

some types of design tokens font weights, sizes, families, & line-heights colors for background, text, & borders shadows spacing & sizing animation durations z-indexes breakpoints #designsystem

Slide 103

Slide 103 text

designers refer to
 design tokens in
 their specifications #designsystem

Slide 104

Slide 104 text

#designsystem

Slide 105

Slide 105 text

theo open source tool by salesforce UX to generate design tokens #designsystem

Slide 106

Slide 106 text

theo JSON file converts to: Lightning Sass Less Stylus JSON (iOS) XML (Android) style guide color swatches (Photoshop & Sketch) #designsystem

Slide 107

Slide 107 text

THEO { "name": "COLOR_TEXT", "value": "#000", "category": "text-color", "comment": "Body text" } #designsystem LIGHTNING SASS // Body text $color-text: #000;

Slide 108

Slide 108 text

CSS — hex iOS — RGBA Android — 8-digit hex #designsystem

Slide 109

Slide 109 text

CSS — rem/em/px iOS — pt Android — sp/dip #designsystem

Slide 110

Slide 110 text

design tokens

Slide 111

Slide 111 text

design tokens: background colors

Slide 112

Slide 112 text

design tokens: font sizes

Slide 113

Slide 113 text

design tokens: radiuses

Slide 114

Slide 114 text

color swatches #designsystem

Slide 115

Slide 115 text

framework agnostic #designsystem

Slide 116

Slide 116 text

no more
 hard-coded values #designsystem

Slide 117

Slide 117 text

empower developers provide developers scalable & accessible code at beginning of 
 development cycle #designsystem

Slide 118

Slide 118 text

design system components our ui library/css framework #designsystem

Slide 119

Slide 119 text

building an enterprise framework is tricky! #designsystem

Slide 120

Slide 120 text

clarity efficiency consistency beauty #designsystem

Slide 121

Slide 121 text

clarity > brevity #designsystem

Slide 122

Slide 122 text

namespaced classes with scoping option #designsystem

Slide 123

Slide 123 text

.slds-button__icon--x-small #designsystem NAMESPACE BLOCK ELEMENT MODIFIER

Slide 124

Slide 124 text

scoping Wrapping styles in a class for components that live in an environment that uses other CSS frameworks or legacy code. #designsystem

Slide 125

Slide 125 text

HTML
#designsystem SASS ul li { margin-left: 20px; } .slds li { margin-left: 0; }

Slide 126

Slide 126 text

living style guide #designsystem + =

Slide 127

Slide 127 text

don’t make it until you need it! (be lean) #designsystem

Slide 128

Slide 128 text

living specifications #designsystem

Slide 129

Slide 129 text

#DeathToRedlines #designsystem

Slide 130

Slide 130 text

“Freed from some of the daily tedium that can come with being a designer, I can shift the bulk of my time and energy to looking at the bigger picture.” — KATEY BASYE #designsystem

Slide 131

Slide 131 text

living #designsystem

Slide 132

Slide 132 text

how do we lower the bar for adoption? #designsystem

Slide 133

Slide 133 text

minimize dependencies #designsystem

Slide 134

Slide 134 text

you don’t know what you don’t know What makes up your ecosystem? Who are your customers? Where are your potential footprints? #designsystem

Slide 135

Slide 135 text

Tokens Icons HTML CSS Guidelines #designsystem

Slide 136

Slide 136 text

no JavaScript‽ #designsystem

Slide 137

Slide 137 text

Lightning React Angular jQuery etc. #designsystem

Slide 138

Slide 138 text

information architecture + documentation to demonstrate outcome #designsystem

Slide 139

Slide 139 text

component states

Slide 140

Slide 140 text

component states

Slide 141

Slide 141 text

component states

Slide 142

Slide 142 text

component states

Slide 143

Slide 143 text

component states

Slide 144

Slide 144 text

component states

Slide 145

Slide 145 text

component states

Slide 146

Slide 146 text

we have to be 
 forward thinking while backward compatible #designsystem

Slide 147

Slide 147 text

3
 supported versions #designsystem

Slide 148

Slide 148 text

current
 production release #designsystem

Slide 149

Slide 149 text

previous
 production release #designsystem

Slide 150

Slide 150 text

future
 production release #designsystem

Slide 151

Slide 151 text

deprecation #designsystem

Slide 152

Slide 152 text

as a developer How do I keep track of changes? When is the right time to deprecate? What kind of impact would deprecating a class have on a customers product? #designsystem

Slide 153

Slide 153 text

as a consumer How do I know what is deprecated? What kind of guidance will I be given? How long will I have to upgrade? #designsystem

Slide 154

Slide 154 text

component states

Slide 155

Slide 155 text

Sass Deprecate! #designsystem

Slide 156

Slide 156 text

$app-version: '1.0.0'; #designsystem

Slide 157

Slide 157 text

$version version in which you want code to deprecate #designsystem

Slide 158

Slide 158 text

$message reason why, or possible workaround #designsystem

Slide 159

Slide 159 text

#designsystem $app-version: '1.0.0'; .slds-button__icon { width: 1rem; height: 1rem; } version 1.0.0

Slide 160

Slide 160 text

#designsystem $app-version: '2.0.0'; @include deprecate('3.0.0', 'use .slds-icon instead') { .slds-button__icon { width: 1rem; height: 1rem; } } version 2.0.0

Slide 161

Slide 161 text

#designsystem 0 15 30 45 60 Release 1 Release 2 Release 3 Release 4 Release 5 Normal CSS Deprecated CSS

Slide 162

Slide 162 text

medium.com/@kaelig/introducing-design-systems-ops-7f34c4561ba7

Slide 163

Slide 163 text

distance from concept to user #designsystem fidelity fades as it gets closer to the user

Slide 164

Slide 164 text

distance with design systems #designsystem fidelity keeps a lot steadier along the way

Slide 165

Slide 165 text

distance with design systems + ops #designsystem reduced inefficiencies, increasing fidelity of software delivery

Slide 166

Slide 166 text

#designsystem CODE LINE
 OPENS CODE LINE
 OPENS FEATURE
 FREEZE RELEASE
 FREEZE GA &
 OPEN SOURCE UI FREEZE GA COMPONENT
 DESIGN FREEZE FEATURE
 FREEZE engineering design system MARKUP HANDOFF

Slide 167

Slide 167 text

make better
 design decisions #designsystem

Slide 168

Slide 168 text

“The more decisions you put off, and the longer you delay them, the more expensive they become.” — CRAIG VILLAMOR, CHIEF DESIGN ARCHITECT, SALESFORCE #designsystem

Slide 169

Slide 169 text

clarity > efficiency > consistency > beauty #designsystem

Slide 170

Slide 170 text

design principles > design standards #designsystem

Slide 171

Slide 171 text

evangelize internally 
 & to your external partners #designsystem

Slide 172

Slide 172 text

support adoption through education & consultation #designsystem

Slide 173

Slide 173 text

advisory boards
 & office hours #designsystem

Slide 174

Slide 174 text

show the impact through examples & metrics #designsystem

Slide 175

Slide 175 text

onward & upward #designsystem

Slide 176

Slide 176 text

“Be regular and orderly in your life so that you may 
 be violent and original in your work.” — GUSTAVE FLAUBERT #designsystem

Slide 177

Slide 177 text

open source #designsystem

Slide 178

Slide 178 text

github.com/salesforce-ux/theo github.com/salesforce-ux/sass-deprecate github.com/salesforce-ux/design-system #designsystem

Slide 179

Slide 179 text

designsystems.herokuapp.com #designsystem

Slide 180

Slide 180 text

#designsystem

Slide 181

Slide 181 text

@themixinsf #designsystem

Slide 182

Slide 182 text

thank you! @jina @salesforceUX #designsystem