Tweet
Tweet

Slide 1

Slide 1 text

  DESIGN SYSTEMS  FLUXIBLE, TORONTO SEPTEMBER 21, 2017 @BENNOLOEWENBERG

Slide 2

Slide 2 text

@BennoLoewenberg  BUTTON  even “simple” things can become complicated

Slide 3

Slide 3 text

Danger DANGER Danger Danger Positive Good Positive positive Source: Richard Saunders This Not this

Slide 4

Slide 4 text

Source: Dominic McPhee

Slide 5

Slide 5 text

Source: David Roessli website investors shop mobile app

Slide 6

Slide 6 text

  DIVERSE CLUTTER  Source: open device lab Helsinki Products, Platforms, Devices

Slide 7

Slide 7 text

“HISTORICALLY GROWN” @BennoLoewenberg Code, Tech, Design, Org

Slide 8

Slide 8 text

  UX & DESIGN DEBT  – Lots of people and tools involved – Little-to-no testing (technical and UX) – Minimal-to-no documentation or specification – Disparate components across all lines of business @BennoLoewenberg

Slide 9

Slide 9 text

  COSTLY CHAOS  – Time – Focus – Brand - Money – Engagement – Value and quality – Customer satisfaction @BennoLoewenberg

Slide 10

Slide 10 text

@BennoLoewenberg   UI-ELEMENTS DETERMINE    IF & HOW FUNCTIONS CAN BE USED 

Slide 11

Slide 11 text

  EU SHOWER TAP  @BennoLoewenberg any amount of water at any temperature can be chosen …

Slide 12

Slide 12 text

  US/CA SHOWER FAUCET  @BennoLoewenberg … easier to use, but limited set of choices (just a bit of hot water connot be selected)

Slide 13

Slide 13 text

  MULTI-SCREEN & OMNI-CHANNEL  UI design becomes increasingly important for products and services. UX determines the value of digital offerings and is their key differentiator . @BennoLoewenberg

Slide 14

Slide 14 text

 GOALS  + Design debt reduction (cohesive brand & UX) + More focus on UX & specialties (no redundancies) + Speeding up the processes (design, handover, code) + Increasing business value (maintainability, scalability) @BennoLoewenberg

Slide 15

Slide 15 text

Alta, Ant, Apex, Axiom, Backpack, Binary, Blueprint, Boundless, Build, Canvas, Carbon, Chameleon, Cirrus, Clarity, Cosmos, DressCode, Fabric, Feelix, Fiori, Fleet, Fluent, Garden, Gel, Glue, Gravity, Grommet, Harmony, Honeycomb, Kotti, Lightning, Material, Mind, Nachos, Northstar, Nova, Opattern, Origami, PatternFly, Photon, Plasma, Polaris, Predix, Primer, Purple, Rizzo, Scooter, Show- Car, Solar, Solid, SolidWork, Spark, Spectrum, Stacks, ingWorx, Uniform, Unity, Quik, Vanilla … @BennoLoewenberg   DESIGN SYSTEMS 

Slide 16

Slide 16 text

@BennoLoewenberg  DEFINITION    OF A DESIGN SYSTEM 

Slide 17

Slide 17 text

 DE-TERMINATION  Design System ≠ Style Guide Design System ≠ Pattern Library Design System ≠ System Design @BennoLoewenberg read: does NOT equal

Slide 18

Slide 18 text

Source: Nathan Curtis (commented)

Slide 19

Slide 19 text

 INTERPLAY  + Blueprint for baseline UI and interaction patterns + Rules defining the interplay of technological and visual components for consistent UX + Codify a system to encourage re-use across products for a cohesive UX Source: Emily Maxie

Slide 20

Slide 20 text

 FACILITATION  + Standardisation of basics frees up to focus on e. g. research, inspiration for new concepts, handoff process, holistic view on features and their impact to the system. + Structure for the foundation of all products and product versions, without requiring a lot of efford each time. @BennoLoewenberg

Slide 21

Slide 21 text

 ANATOMY    OF MODULAR DESIGN  @BennoLoewenberg

Slide 22

Slide 22 text

Source: Hidde de Vries (commented) Design system

Slide 23

Slide 23 text

  INSTEAD OF FIXED LAYOUTS …  @BennoLoewenberg

Slide 24

Slide 24 text

  … FLEXIBLY USABLE ELEMENTS  @BennoLoewenberg

Slide 25

Slide 25 text

@BennoLoewenberg  ADAPTABILITY  Designing for modules and their interplay in different screens, not static pages. Design for change of products, platforms and user-related affordances.

Slide 26

Slide 26 text

  INTERRELATED INDEPENDENT PARTS  @BennoLoewenberg (aft. Diana Mounter) Element Component Page layout Interaction model

Slide 27

Slide 27 text

  DESIGN TOKENS  @BennoLoewenberg (aft. Jina Anne) NO hard coded values

Slide 28

Slide 28 text

@BennoLoewenberg (aft. Sophia Voychehovski Prater)  RESPONSIVE  Teaser box Search results grid Landing page

Slide 29

Slide 29 text

@BennoLoewenberg (aft. styltil.es)  THEMABLE  LOGO LOGO LOGO Partner Site Product B Product A

Slide 30

Slide 30 text

@BennoLoewenberg  COMPOSITION    OF A DESIGN SYSTEM 

Slide 31

Slide 31 text

SOME RESOURCES @BennoLoewenberg STYLE GUIDE & PATTERN LIB   MANY “DESIGN SYSTEMS” 

Slide 32

Slide 32 text

Source: Jeremy Keith

Slide 33

Slide 33 text

@BennoLoewenberg most important HOW TO USE HOW TO USE HOW IT LOOKS & SOUNDS MADE TO USE

Slide 34

Slide 34 text

@BennoLoewenberg most important HOW TO USE GUIDELINES STYLE & PATTERNS DES & DEV RESOURCES

Slide 35

Slide 35 text

BUILDING BLOCKS (STYLE GUIDE) Color Pallettes Typographic Scales Grid Definitions Icons & Assets UI PATTERNS (LIBRARY) Elements Components Modules Templates RULES (GUIDELINES) Design Principles Implementation Guidelines Editorial Guidelines @BennoLoewenberg (aft. UXpin)

Slide 36

Slide 36 text

@BennoLoewenberg (aft. Dominic McPhee) STYLE GUIDE PATTERN LIBRARY Design Language Making it real PRINCIPLES DOCUMENTATION LIVING STYLEGUIDE UI & UX KITS major success factor GOVERNANCE

Slide 37

Slide 37 text

@BennoLoewenberg  EXAMPLES    OF DESIGN SYSTEMS 

Slide 38

Slide 38 text

@BennoLoewenberg HOW IT LOOKS

Slide 39

Slide 39 text

 STYLEGUIDE  Source: Atlassian Design

Slide 40

Slide 40 text

 STYLEGUIDE  Source: Atlassian Design

Slide 41

Slide 41 text

  PATTERN LIBRARY  Source: IBM Carbon

Slide 42

Slide 42 text

  PATTERN LIBRARY  Source: IBM Carbon

Slide 43

Slide 43 text

  ANIMATION GUIDELINES  Source: Google Material Design

Slide 44

Slide 44 text

Source: Google Material Design   ANIMATION GUIDELINES 

Slide 45

Slide 45 text

HOW TO USE @BennoLoewenberg HOW TO USE

Slide 46

Slide 46 text

  DESIGN PRINCIPLES  Source: Apple Human Interface Guidelines (commented)

Slide 47

Slide 47 text

  DESIGN PRINCIPLES  Source: Apple Human Interface Guidelines (commented)

Slide 48

Slide 48 text

Source: SAP Fiori   UX GUIDELINES 

Slide 49

Slide 49 text

Source: SAP Fiori   UX GUIDELINES 

Slide 50

Slide 50 text

Source: Shopify Polaris   CONTENT GUIDELINES 

Slide 51

Slide 51 text

Source: Shopify Polaris   CONTENT GUIDELINES 

Slide 52

Slide 52 text

@BennoLoewenberg MADE TO USE

Slide 53

Slide 53 text

  LIVING STYLEGUIDE  Source: Salesforce Lightning

Slide 54

Slide 54 text

  LIVING STYLEGUIDE  Source: Salesforce Lightning

Slide 55

Slide 55 text

  UI KITS  Source: Material Design Themer – Sketch Library

Slide 56

Slide 56 text

  PROTOTYPING KITS  Source: SAP Fiori – Axure Widgets

Slide 57

Slide 57 text

Source: Facebook Design – Sound Files   MEDIA ASSET KITS 

Slide 58

Slide 58 text

@BennoLoewenberg  CREATING    A DESIGN SYSTEM 

Slide 59

Slide 59 text

  BIG PICTURE  + Establish a baseline framework + Care for company-wide awareness of it and its use + Institute a global design and development tool set + Implement a “single source of truth” across all LOBs + Constanly review and maintain the design system @BennoLoewenberg

Slide 60

Slide 60 text

Source: Nathan Curtis   DEFINED WORKFLOW 

Slide 61

Slide 61 text

 INITIATION  1. Element audit 2. User research and features determination 3. Object-repository identification 4. Minimum viable design system 5. Pilot project (reference design showcase) @BennoLoewenberg

Slide 62

Slide 62 text

  AUDIT & REPOSITORY  Source: Design System Worksheet – Nathan Curtis

Slide 63

Slide 63 text

  LITTLE STEPS  Start small core elements & assets everyone can understand & use Make it usable tokenize design options & showcase pages & elements Use it prioratize it, conduct design clinics, demos & audits to foster design & development convergence Source: Nathan Curtis

Slide 64

Slide 64 text

@BennoLoewenberg  ASPECTS    OF A DESIGN SYSTEM 

Slide 65

Slide 65 text

 PRODUCT  It is NOT a simple side project ! A design system is a full-blown product serving other software products. It significantly influences the quality of the products, that are built with it and therefore is a success factor @BennoLoewenberg

Slide 66

Slide 66 text

  SUCCESS FACTORS  A design system needs strategy and resources as every “regular” product. For it’s successful realisation many participants need to contribute to it. Designers and developers will keep supporting it , only if they have ownership of the design system. @BennoLoewenberg

Slide 67

Slide 67 text

  NEVER DONE  It is NOT a one-off ! To keep a design system alive, relevant, it constantly needs to be maintained . The bigger it grows, the shorter the cycles need to be for checking its affordances, quality and updating it . @BennoLoewenberg

Slide 68

Slide 68 text

@BennoLoewenberg (aft. Ken Skistim)  BALANCE  Flexibility Consistency Design System Create everthing from scratch Only use what comes in-the-box

Slide 69

Slide 69 text

@BennoLoewenberg (aft. Firefox Photon)  BALANCE  Similarity Platform Product Familiarity 0 Design System Bad Usability No Brand

Slide 70

Slide 70 text

  SCALING UX  Design Systems are a way to make UX tangible to teams and to make brand values actionable . @BennoLoewenberg

Slide 71

Slide 71 text

  BENNOLOEWENBERG   LINKEDIN / XING / TWITTER  @ Design Sprint