Neha Sharma
nehasharma.dev

nehasharma.dev

Day 5: What Design System should not have #25DaysofDS

Neha Sharma's photo
Neha Sharma
·Jul 9, 2021·

3 min read

Subscribe to my newsletter and never miss my upcoming articles

PS: I am republishing my 2019 blogs on the Design system at the Hash node. However, these blogs are still valid.


Most of the authors of the Design system try to fit everything in the design system. The success parameter of the design system is not how many features it has, how many components it has etc. Instead of adding more and more components and features the Design System author should focus on the quality.

Today I am going to share what Design System should not have:

A lot of components

Once your design system will be in place. Trust me you will get a lot of push to add as many as components the company can. As a Design system author, you need to make sure that the Design system should not be overcrowded by the components which are not getting used by more than 2-3 projects (depend upon the company's size). Also, when you are getting the list of the components to feel free to drop the components which you think can be developed by the developers by using just atoms.

Patterns that are not reusable

Similarly like components, you will see the push from the projects and developers to have the patterns which they are supposed to develop. Remember design system should be non-bias to the projects. Do not add a pattern that is unique to only 1 product or project. Look for the patterns which are generic and reusable across the company such as login page, signup, etc.

Documentation of unnecessary things

Do not overwhelm the design system with the documentation. Only provide the necessary and important information only. Developers won't be interested and have the time to read lengthy documentation. Try to have the documentation from the user's perspective and try to break the documentation in What? When? How?

Do not provide the documentation about the tech and designs about how to do the X. Talk about

Styles

Your Design system should speak about your product or company's unique identity. Do not add as many different styles as you can. Always have only limited styles such as buttons - might be you just need buttons with sharp and rounded corners and not with the shadow.

Your Design system should speak about your product or company's unique identity. Do not add as many different styles as you can. Always have only limited styles such as buttons - might be you just need buttons with sharp and rounded corners and not with the shadow.

Similarly, do not keep every content related to the designers only. Your design system should be well balanced for the development and the designer.

Happy Learning

 
Share this