It Takes a Village: Building Organizational Buy-In For Your Design System

Slide 1

Slide 1 text

It Takes a Village: Building Organization Buy-In For Your Design System

Slide 2

Slide 2 text

Lina Calin, Project Manager

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

1. Why building buy-in for your design system is important 2. How to build buy-in for your design system 3. A real world example of building organizational buy-in Agenda

Slide 5

Slide 5 text

Why is Buy-In Important?

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

+ +

Slide 8

Slide 8 text

● Buy-in shows us we built the right thing. ● Buy-in shows us we built it the right way. ● Buy-in leads us towards a better user experience.

Slide 9

Slide 9 text

Steps to Build Investment

Slide 10

Slide 10 text

1. Document your “why”

Slide 11

Slide 11 text

‘Why’ ■ What existing problems will your design system solve? ■ What future problems can the design system mitigate? ■ What other beneﬁts can a design system bring?

Slide 12

Slide 12 text

Document your “why” Have an immediate example of a problem a design system will solve

Slide 13

Slide 13 text

2. Build allies

Slide 14

Slide 14 text

Build allies 1. Pick someone(s) powerful and inﬂuential 2. Pick someone(s) who, with access to a design system, will have a lot of impact 3. Pick someone(s) who can explain the technical beneﬁts

Slide 15

Slide 15 text

3. Identify key stakeholders

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

4. Understand limitations & requirements ☑

Slide 18

Slide 18 text

Understand the build requirements ➔ Any features need to get to integration quicker? ➔ Any needs of your allies that should be prioritized? ● Tech-speciﬁc or tech-agnostic? ● Budget constraints? ● Urgency?

Slide 19

Slide 19 text

5. Make a support plan

Slide 20

Slide 20 text

Support Plan ● Platform & browser support ● Regular newsletter with updates ● Dedicated Slack channel ● “Oﬃce hours” with support team ● Versioning ● Documented process for contribution ● Regular user surveys

Slide 21

Slide 21 text

“Your technical approach doesn’t matter as much as creating a living, breathing system that’s flexible, maintainable, stable, scalable, and successful in the long-term.” - Katie Sylor-Miller, Senior Software Engineer – Design Systems at Etsy

Slide 22

Slide 22 text

Case: University of Georgia

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

Document your “why”

Slide 25

Slide 25 text

Build allies & identify key stakeholders

Slide 26

Slide 26 text

“It's helpful to recognize that you don't have to get everyone's buy-in all at once. But you do want to be strategic about who you build your partnerships with and in what order.” - Nancy Byron | Marketing and Communications Manager - UGA Online Learning

Slide 1

Slide 1 text

Slide 2

Slide 2 text

Slide 3

Slide 3 text

Slide 4

Slide 4 text

Slide 5

Slide 5 text

Slide 6

Slide 6 text

Slide 7

Slide 7 text

Slide 8

Slide 8 text

Slide 9

Slide 9 text

Slide 10

Slide 10 text

Slide 11

Slide 11 text

Slide 12

Slide 12 text

Slide 13

Slide 13 text

Slide 14

Slide 14 text

Slide 15

Slide 15 text

Slide 16

Slide 16 text

Slide 17

Slide 17 text

Slide 18

Slide 18 text

Slide 19

Slide 19 text

Slide 20

Slide 20 text

Slide 21

Slide 21 text

Slide 22

Slide 22 text

Slide 23

Slide 23 text

Slide 24

Slide 24 text

Slide 25

Slide 25 text

Slide 26

Slide 26 text

Slide 27

Slide 27 text

Slide 28

Slide 28 text

Slide 29

Slide 29 text

Slide 30

Slide 30 text

Slide 31

Slide 31 text