Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Living Design Systems

67bb0a8cd6c1993dba0bfe302852f729?s=47 jina
March 17, 2016

Living Design Systems

Made by Few, CSS Conf EU, Nordic.js, Cascade SF UX Night, Camp Sass, So Coded, Smashing Conference Barcelona, Smashing Conference Oxford, Smashing Conference San Francisco



March 17, 2016

More Decks by jina

Other Decks in Design


  1. SMASHING CONFERENCE SAN FRANCISCO 04.06.2016 living design systems @JINA LEAD

    DESIGNER, DESIGN SYSTEMS #designsystem
  2. 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
  3. user experience #designsystem

  4. @salesforceux #designsystem #designsystem


  6. “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
  7. why did salesforce need a design system? #designsystem

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

  9. 17
 years of legacy #designsystem

  10. 20K+
 employees #designsystem

  11. lots of products #designsystem

  12. sales #designsystem Sales Cloud SalesforceIQ Data.com

  13. service Service Cloud Desk.com #designsystem

  14. marketing Marketing Cloud Pardot #designsystem

  15. community Community Cloud Chatter #designsystem

  16. analytics Wave Analytics Wave Apps #designsystem

  17. apps App Cloud Force.com Heroku Enterprise #designsystem

  18. internet
 of things IoT Cloud Thunder #designsystem

  19. lots of
 platforms & devices #designsystem

  20. lots of people #designsystem

  21. dozens of scrum teams hundreds of developers small team of

    designers #designsystem
  22. design for scale #designsystem

  23. design for configuration #designsystem

  24. #designsystem

  25. #designsystem Where can I find the icons? What color is

    the button border? Where can I find the icons?
  26. redlines? #designsystem

  27. #designsystem

  28. #designsystem

  29. #designsystem

  30. #FML #designsystem

  31. #designsystem design pages

  32. “A fractured process makes for a fractured user experience” —

    NATE FORTIN #designsystem
  33. #designsystem design systems

  34. style guides are all
 the rage …and they have come

    a long way #designsystem
  35. styleguides.io #designsystem

  36. #designsystem

  37. alistapart.com/article/writingainterfacestyleguide

  38. brand & design standards front-end standards keep your style guide

    current & useful #designsystem
  39. former salesforce1 style guide

  40. #designsystem How do I get my app
 to look like

  41. #designsystem Can I use the CSS
 in my app?

  42. 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
  43. trustworthy #designsystem

  44. zombie style guides #designsystem

  45. it must be living #designsystem

  46. “…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
  47. #designsystem

  48. lightning experience #designsystem

  49. salesforce.com/designsystem

  50. consistent with the salesforce lightning UI #designsystem

  51. “…great design systems 
 are usable by your 

    team.” — MARK OTTO #designsystem
  52. medium.com/eightshapes-llc/team-models-for-scaling-a-design-system-2cf9d03be6a0

  53. 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
  54. team model #2: centralized a single, central design team produces

 and supports a system used by others 
  55. 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
  56. medium.com/salesforce-ux/the-salesforce-team-model-for-scaling-a-design-system-d89c2a2d404b

  57. a cyclical team model design system informs product design product

    design informs design system #designsystem
  58. our centralized design systems team acts as a librarian, distributor,

    and facilitator, and we make sure it is maintained and crafted with quality #designsystem
  59. our centralized team product design frontend developers (css framework) accessibility

    visual design ux engineers (infrastructure & distribution) #designsystem
  60. our federated design systems contributors distributed throughout the organization keep

    the Design System accurate, current, & actually useful #designsystem
  61. our federated team product & platform designers prototypers researchers additional

    ux engineers #designsystem
  62. “A Design System isn’t a project. It’s a product, serving

    products.” — NATHAN CURTIS #designsystem
  63. to design at salesforce
 is to consider the
 whole ecosystem

  64. plan with a roadmap #designsystem

  65. do user research #designsystem

  66. “Design considerations beat design patterns. Test and decide; don’t just

    copy things like the hamburger icon.” — LUKE WROBLEWSKI #designsystem
  67. “While a company is growing fast, there is nothing more

    important than constant communication and complete alignment.” — MARC BENIOFF #designsystem
  68. have a clear vision to
 align efforts #designsystem

  69. lists in priority order #designsystem

  70. bring designers, engineers, 
 & product managers together around a

    single goal #designsystem
  71. drive design decisions with design principles #designsystem

  72. clarity Eliminate ambiguity. Enable people to see, understand, and act

 with confidence. #designsystem
  73. efficiency Streamline and optimize workflows. Intelligently anticipate needs to help

    people work better, smarter, and faster. #designsystem
  74. consistency Create familiarity and strengthen intuition by applying the same

    solution to the same problem. #designsystem
  75. beauty Demonstrate respect for 
 people’s time and attention through

    thoughtful and 
 elegant craftsmanship. #designsystem
  76. UI inventory Audit your UI by categorizing all the different

    types of components you have, along with their variants. #designsystem
  77. #designsystem

  78. #designsystem

  79. #designsystem

  80. standardize
 & consolidate #designsystem

  81. take component notes layouts, responsive behaviors, visual differentiation, states, 

    keyboard navigation, usage guidelines, and accessibility requirements #designsystem
  82. open-ended questions
 & action items #designsystem

  83. list the people involved especially design and engineering leads #designsystem

  84. it’s all components #designsystem

  85. design patterns & guidelines #designsystem

  86. color neutrals #designsystem primaries secondaries

  87. visual messaging #designsystem

  88. visual differentiation #designsystem

  89. visual hierarchy #designsystem

  90. accessibility #designsystem

  91. localization & internationalization #designsystem

  92. “…Creating a positive experience
 is not about having best practices.

    It’s about putting those practices into the right hands.” — BRENDON CORNWELL #designsystem
  93. resources including HTML, CSS, icons, & fonts #designsystem

  94. empower designers design & iterate more efficiently in the browser

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

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

  97. how do we keep 
 our design
 system agnostic? #designsystem

  98. single source of truth #designsystem

  99. assets are stored in repository & automatically updated in the

    app & style guide #designsystem
  100. design tokens the basic atoms of the Lightning Design System

  101. design tokens help us scale design across both web &

    native applications #designsystem
  102. 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
  103. designers refer to
 design tokens in
 their specifications #designsystem

  104. #designsystem

  105. theo open source tool by salesforce UX to generate design

    tokens #designsystem
  106. theo JSON file converts to: Lightning Sass Less Stylus JSON

    (iOS) XML (Android) style guide color swatches (Photoshop & Sketch) #designsystem
  107. THEO { "name": "COLOR_TEXT", "value": "#000", "category": "text-color", "comment": "Body

    text" } #designsystem LIGHTNING <!-- Body text color --> <aura:var name="colorText" value="#000" /> SASS // Body text $color-text: #000;
  108. CSS — hex iOS — RGBA Android — 8-digit hex

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

  110. design tokens

  111. design tokens: background colors

  112. design tokens: font sizes

  113. design tokens: radiuses

  114. color swatches #designsystem

  115. framework agnostic #designsystem

  116. no more
 hard-coded values #designsystem

  117. empower developers provide developers scalable & accessible code at beginning

 development cycle #designsystem
  118. design system components our ui library/css framework #designsystem

  119. building an enterprise framework is tricky! #designsystem

  120. clarity efficiency consistency beauty #designsystem

  121. clarity > brevity #designsystem

  122. namespaced classes with scoping option #designsystem

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

  124. scoping Wrapping styles in a class for components that live

    in an environment that uses other CSS frameworks or legacy code. #designsystem
  125. HTML <div class="slds"> <!-- Your components here --> </div> #designsystem

    SASS ul li { margin-left: 20px; } .slds li { margin-left: 0; }
  126. living style guide #designsystem + =

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

  128. living specifications #designsystem

  129. #DeathToRedlines #designsystem

  130. “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
  131. living #designsystem

  132. how do we lower the bar for adoption? #designsystem

  133. minimize dependencies #designsystem

  134. you don’t know what you don’t know What makes up

    your ecosystem? Who are your customers? Where are your potential footprints? #designsystem
  135. Tokens Icons HTML CSS Guidelines #designsystem

  136. no JavaScript‽ #designsystem

  137. Lightning React Angular jQuery etc. #designsystem

  138. information architecture + documentation to demonstrate outcome #designsystem

  139. component states

  140. component states

  141. component states

  142. component states

  143. component states

  144. component states

  145. component states

  146. we have to be 
 forward thinking while backward compatible

  147. 3
 supported versions #designsystem

  148. current
 production release #designsystem

  149. previous
 production release #designsystem

  150. future
 production release #designsystem

  151. deprecation #designsystem

  152. 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
  153. 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
  154. component states

  155. Sass Deprecate! #designsystem

  156. $app-version: '1.0.0'; #designsystem

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

  158. $message reason why, or possible workaround #designsystem

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

    version 1.0.0
  160. #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
  161. #designsystem 0 15 30 45 60 Release 1 Release 2

    Release 3 Release 4 Release 5 Normal CSS Deprecated CSS
  162. medium.com/@kaelig/introducing-design-systems-ops-7f34c4561ba7

  163. distance from concept to user #designsystem fidelity fades as it

    gets closer to the user
  164. distance with design systems #designsystem fidelity keeps a lot steadier

    along the way
  165. distance with design systems + ops #designsystem reduced inefficiencies, increasing

    fidelity of software delivery
  166. #designsystem CODE LINE

 FREEZE engineering design system MARKUP HANDOFF
  167. make better
 design decisions #designsystem

  168. “The more decisions you put off, and the longer you

    delay them, the more expensive they become.” — CRAIG VILLAMOR, CHIEF DESIGN ARCHITECT, SALESFORCE #designsystem
  169. clarity > efficiency > consistency > beauty #designsystem

  170. design principles > design standards #designsystem

  171. evangelize internally 
 & to your external partners #designsystem

  172. support adoption through education & consultation #designsystem

  173. advisory boards
 & office hours #designsystem

  174. show the impact through examples & metrics #designsystem

  175. onward & upward #designsystem

  176. “Be regular and orderly in your life so that you

 be violent and original in your work.” — GUSTAVE FLAUBERT #designsystem
  177. open source #designsystem

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

  179. designsystems.herokuapp.com #designsystem

  180. #designsystem

  181. @themixinsf #designsystem

  182. thank you! @jina @salesforceUX #designsystem