Yes, design systems need to be consistent and stable, but they shouldn’t move fast. If a design system team were to constantly make changes and updates at a rapid pace, it could cause chaos and confusion for those who rely on the system. Users need to have a sense of predictability and reliability when it comes to design systems, so moving fast is definitely not something a design system team should do.
The second thing a design system team shouldn’t do is ignore feedback. Design systems are meant to be collaborative and iterative. They should be constantly evolving based on user feedback and changing needs. If a design system team ignores feedback from users, designers, or stakeholders, then the system will become stagnant and ineffective. Feedback is crucial for improving and refining a design system, so it should never be disregarded.
The third thing a design system team shouldn’t do is prioritize aesthetics over functionality. While it’s important for a design system to be visually appealing and consistent, it should never prioritize aesthetics over functionality. Design systems exist to create efficiency and usability, not just to look pretty. If a design system team focuses too much on aesthetics at the expense of functionality, then the system may not be as effective as it could be. Functionality should always be the top priority when it comes to design systems.
The fourth thing a design system team shouldn’t do is work in silos. Design systems require collaboration and communication between designers, developers, and other stakeholders. If a design system team works in silos, then it will be difficult to create a cohesive and unified system. Design systems are meant to be shared and used by multiple teams and individuals, so it’s important for the design system team to work together and not in isolation. Collaboration is key when it comes to creating a successful design system.
In conclusion, there are many things a design system team shouldn’t do in order to create an effective and efficient system. Moving fast, ignoring feedback, prioritizing aesthetics over functionality, and working in silos are just a few of the things that can lead to a problematic design system. By avoiding these pitfalls and focusing on collaboration, consistency, and functionality, a design system team can create a system that is truly beneficial and valuable to all who use it.
