-
Notifications
You must be signed in to change notification settings - Fork 12
Why Nucleus?
Every system ultimately boils down to the user. In this case, the users aren’t necessarily the people buying our product (although a design system will help them too), but the people within the organization.
Creating a unified design system will speed-up the design and development process while also helping build bridges amongst teams. Good design is a language, and when everyone is speaking the same language, that’s when things get done.
When the entire organization is on the same page, teams can move faster, communicate better and ultimately increase the speed at which products are updated and released.
With a majority of our products being built using Ember JS, sharable and reusable components would not only bring down the development time & effort, but also improve the maintainability of the components.
For instance, take the modal component which is used throughout our app to show sliding panel information. Hypothetically, if Freshdesk, Freshsales and other apps use the same component, a bug fixed by Freshdesk dev team would benefit the entire suite of apps and individual product developers won't have to apply the same patch to their products.
Instead of repeatedly building similar components from scratch, Design Systems enable designers & developers to reuse components and thereby increase efficiency. Increased efficiency and consistency would enable us to build faster products at scale.
Typically, creating a design system begins with an audit of all the visual components within the product which helps accomplish a number of things.
One of the most obvious benefits is that an audit can show you where the biggest inconsistencies within your designs are. It also helps teams see the most important and most commonly used elements and components of the product.
An audit can also reveal the weaknesses of the existing visual system, which can be communicated to the business at large, and help gain support for moving forward with a unified system.
Design debt is real, and it is a huge problem especially as organizations scale. New features get added, old features become outdated and, standards can change.
Since design systems are constantly being maintained and updated, either through a solitary, centralized team or federalized model, they can grow with the products they are being built to support.
Now how does better internal communication help the external customer?
By creating a consistent experience for the customer, we can reduce the cognitive load created when switching from one product to another or even from a mobile app experience to a desktop browser experience.