Keeping your design system alive

A presentation at DIGICOM in November 2017 in Barcelos, Portugal by Inayaili León

Slide 1

Slide 1

Keeping your design system alive @yaili DIGICOM, Barcelos, November 2017

Slide 2

Slide 2

About me…

Slide 3

Slide 3

Slide 4

Slide 4

Slide 5

Slide 5

Slide 6

Slide 6

Slide 7

Slide 7

Slide 8

Slide 8

Slide 9

Slide 9

Slide 10

Slide 10

Slide 11

Slide 11

Why design systems

Slide 12

Slide 12

“A design system offers a library of visual style, components, and other concerns documented and released by an individual, team or community as code and design tools so that adopting products can be more e ffi cient and cohesive. ” — Nathan Curtis

Slide 13

Slide 13

“Almost always, a design system offers a library of visual style and components documented and released as reusable code for developers and/or tool(s) for designers. A system may also offer guidance on accessibility, page layout, and editorial and less o

en branding, data viz,   UX patterns, and other tools. ” — Nathan Curtis

Slide 14

Slide 14

Slide 15

Slide 15

Slide 16

Slide 16

Slide 17

Slide 17

Slide 18

Slide 18

Slide 19

Slide 19

Slide 20

Slide 20

A quick note

Slide 21

Slide 21

“design system”

Slide 22

Slide 22

Slide 23

Slide 23

Slide 24

Slide 24

  1. Put someone in charge

Slide 25

Slide 25

Slide 26

Slide 26

“System enthusiasts must become entrepreneurs, pitching and selling ideas that get a possibly resistant organization to commit. ” — Nathan Curtis

Slide 27

Slide 27

  1. Have a roadmap

Slide 28

Slide 28

Slide 29

Slide 29

Slide 30

Slide 30

  1. Be open

Slide 31

Slide 31

Slide 32

Slide 32

Slide 33

Slide 33

Slide 34

Slide 34

  1. Define contribution process

Slide 35

Slide 35

Slide 36

Slide 36

Slide 37

Slide 37

  1. Look a

er the docs

Slide 38

Slide 38

Slide 39

Slide 39

Slide 40

Slide 40

Slide 41

Slide 41

  1. Make things easy to find

Slide 42

Slide 42

Slide 43

Slide 43

Slide 44

Slide 44

  1. Plan maintenance

Slide 45

Slide 45

“A system isn’t a project with an end, it’s the origin story of a living and evolving product that’ll serve other products. ” — Nathan Curtis

Slide 46

Slide 46

Slide 47

Slide 47

Slide 48

Slide 48

  1. Learn from others

Slide 49

Slide 49

Slide 50

Slide 50

  1. Put someone in charge
  2. Have a roadmap
  3. Be open
  4. Define contribution process
  5. Look a

er documentation 6. Make things easy to find 7. Plan maintenance 8. Learn from others

Slide 51

Slide 51

@yaili

github.com/yaili/speaking

— designers: bit.ly/mup-jobs

developers: bit.ly/yld-jobs

Slide 52

Slide 52

Thank you!