The document discusses five rules for effectively assimilating a design system into an organization: 1. Provide stability and flexibility using major and minor versions to allow for changes while maintaining consistency. 2. Resist FOMO (fear of missing out) by regulating what components teams can update to in order to prevent breaking changes. 3. Become a gatekeeper by applying "Noah's challenge" - evaluating if new requirements can be met within the existing design system before making exceptions. 4. Provide incentives for teams to use the design system components by making them off-the-shelf, native, and tailored to technology. 5. Squeeze the design system into the organization gradually from the bottom-up while

1. Design System as a Product
How to effectively assimilate a Design System in
your organization

2. Liran Elboym
UX Manager | Cognitive Psychologist

3. UNIVERSITY OF MINIMIZING THE BASA

7. * * * *
* *
* * ___
* * | | |
* _________## * / | |
@## * | |--o|===|-|
* @@@## |/|/ |---| |d|
@@ @@ ||//|/ * / |w|
* @@@@@@@ ||/|/ | U | |b|
@@@@@@@@@----------| |// | S |=| |
__ @@ @@@ @@__________| |/ | A | | |
____|_@|_ @@@@@@@@@__________| |/ |_______| |_|
=|__ _____ |= @@@@ .@@@__________| | |@| |@| | |
____0_____0__|/__@@@@__@@@__________|_|/__|___|/__|/___________|_|_

8. Design System Adoption Survey

9. Some Numbers
Design System is in place
100%
Have:
- Visual guidelines
- Design Patterns
- Description of controls
100%
Also have a library of working
controls and components
70%

10. Some Numbers
Avg. rate of partial adoption
40%
Avg. time to get to these rates
2 Years
Avg. rate of full adoption
50%

11. Avg. Adoption Rate
70%

14. Five Rules
Provide stability
and flexibility using
versions
Resist FOMO by
regulation
Become a gate
keeper by applying
Noah’s challenge
Provide incentive Squeeze your
Design System into
the organization
01. 02. 03. 04. 05.

15. “You’re changing the guidelines too often”

16. Fundamental Paradox – Stability vs. Flexibility
Why Stability
- Less changes = less effort
- Same UX solutions = consistency
- Alignment across products becomes easier
Why Flexibility
- Different products have different requirements
- Requirements evolve
- We want to improve our solutions
- New UX trends are introduced

17. Provide Stability and Flexibility Using Versions
Major Version
- Happen rarely
- Major changes are allowed
Minor Version
- Happen frequently
- Changes between minor versions are minimal
- No enforcement on the latest minor version
- Design Patterns from different minor versions co-exist

19. Changes in navigation model
Changes to existing Design Patterns and controls/components
Changes to Look and Feel
Introduce new Design Patterns
Major Version Minor Version
Provide Stability and Flexibility Using Versions
Allowed
Allowed
Allowed
Allowed
Not Allowed
Rarely
Only Minor
Allowed

20. Example of a Major Change – Design Patterns

21. Example of a Major Change – Look and Feel

22. Examples of Minor Changes
Old New

23. Five Rules
Provide stability
and flexibility using
versions
Resist FOMO by
regulation
Become a gate
keeper by applying
Noah’s challenge
Provide incentive Squeeze your
Design System into
the organization
01. 02. 03. 04. 05.

24. “But I want the latest and greatest!”

25. Resist FOMO by Regulation
Win XP
Win 8
Win 7
Win 10

26. Five Rules
Provide stability
and flexibility using
versions
Resist FOMO by
regulation
Become a gate
keeper by applying
Noah’s challenge
Provide incentive Squeeze your
Design System into
the organization
01. 02. 03. 04. 05.

27. “But my requirements are different!”

28. Become a Gate Keeper by Applying Noah’s Challenge
Make sure the requirement is valid
Look for a good-enough approximation
Couldn’t find?
Congratulations!
Slight deviation?
Consider a compromise
Consider expansion
Make an exception

29. Five Rules
Provide stability
and flexibility using
versions
Resist FOMO by
regulation
Become a gate
keeper by applying
Noah’s challenge
Provide incentive Squeeze your
Design System into
the organization
01. 02. 03. 04. 05.

30. “Why should I use it?”

31. Provide Incentive
- Off-the-shelf controls and components
- Native
- Tailored to technology

32. Five Rules
Provide stability
and flexibility using
versions
Resist FOMO by
regulation
Become a gate
keeper by applying
Noah’s challenge
Provide incentive Squeeze your
Design System into
the organization
01. 02. 03. 04. 05.

33. “Bottom-up or top-down?”

34. Squeeze Your Design System Into the Organization
- Start bottom-up
- Work gradually. Don’t wait until you have everything in place
- Look for an opportunity to influence top-down
- Look for an opportunity to nail it
- Create an objective measuring tool

35. Five Rules
Provide stability
and flexibility using
versions
Resist FOMO by
regulation
Become a gate
keeper by applying
Noah’s challenge
Provide incentive Squeeze your
Design System into
the organization
01. 02. 03. 04. 05.

36. Goodbye 