Keeping your design system alive

A presentation at Pixel Pioneers in June 2018 in Bristol, UK by Inayaili de León

Slide 1

Slide 1

Keeping your design system alive @yaili Pixel Pioneers — Bristol, June 2018

Slide 2

Slide 2

Keeping your design system alive @yaili Pixel Pioneers — Bristol, June 2018

Slide 3

Slide 3

© bit.ly/banksyvbristol

Slide 4

Slide 4

About you…

Slide 5

Slide 5

About me…

Slide 6

Slide 6

/

Slide 7

Slide 7

Slide 8

Slide 8

Slide 9

Slide 9

Slide 10

Slide 10

Slide 11

Slide 11

Slide 12

Slide 12

Slide 13

Slide 13

Slide 14

Slide 14

Slide 15

Slide 15

What are design systems

Slide 16

Slide 16

A design system is not a pattern library, brand guidelines or a Sketch file.

Slide 17

Slide 17

A design system is a system of living principles, guides and components used by designers and developers to build consistent products and experiences.

Slide 18

Slide 18

A design system is a product . It has users, roadmaps, releases, features, maintenance, bugs, documentation and support.

Slide 19

Slide 19

Slide 20

Slide 20

Slide 21

Slide 21

Slide 22

Slide 22

  1. Put someone in charge

Slide 23

Slide 23

Slide 24

Slide 24

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

Slide 25

Slide 25

  1. Define a roadmap

Slide 26

Slide 26

Slide 27

Slide 27

Slide 28

Slide 28

  1. Be open

Slide 29

Slide 29

Slide 30

Slide 30

Slide 31

Slide 31

Slide 32

Slide 32

  1. Explain how to contribute

Slide 33

Slide 33

Slide 34

Slide 34

Slide 35

Slide 35

Slide 36

Slide 36

  1. Love your docs

Slide 37

Slide 37

Slide 38

Slide 38

Slide 39

Slide 39

Slide 40

Slide 40

Slide 41

Slide 41

  1. Plan for maintenance

Slide 42

Slide 42

“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 43

Slide 43

Slide 44

Slide 44

Slide 45

Slide 45

You’re going to make mistakes. That’s OK.

Slide 46

Slide 46

  1. Learn from others

Slide 47

Slide 47

Slide 48

Slide 48

  1. Put someone in charge
  2. Have a roadmap
  3. Be open
  4. Explain how to contribute
  5. Love your docs
  6. Plan for maintenance
  7. Learn from others

Slide 49

Slide 49

Thank you! @yaili

github.com/yaili/speaking/references