Table of contents
Today, I heard a product designer complaining, “design systems are good, but sometimes I feel limited by them. I cannot be creative and I cannot innovate. All those guidelines prevent me from creating the best user experience ever.”
It wasn’t the first time I’d heard this. So, what’s going on?
Unpacking this kind of comment can lead you to three very different interpretations that show a different understanding of the design system and the role of designers.
First case: You don’t actually want a design system
Many product designers feel limited by the guidelines that need to be followed while crafting mockups and UI screens. You don’t feel free to do “your best work” simply because you cannot do what you want, case by case.
With a design system, you cannot choose the precise hex of blue you want, you cannot use a different button shape just for that one page. As a designer, you aren’t the decision maker - the guidelines are fixed and shared with everyone in the design and development teams.
If you are feeling this frustration it means you are not understanding your company’s goals, and you haven’t bought into the design system mindset.
You are working on your part of the product without considering that success is not dependent on the best user experience alone. Success means working within limitations, like time, budget, and technical feasibility. You are refusing to accept that design is not always the top priority.
Designers bring the most value when they can create the best possible user experience within all the unavoidable constraints. This means partnering with developers and the rest of the team to figure out the best solution. A design system does that too: it is a tool to build a product, help designer and developer communicate, and make sure what’s designed and what’s in production is aligned.
Think of it this way. A design system allows you to unlock new ways of being creative. Without being hyper-focused on the spacing of each button, you can focus on the user journey and overall experience.
Second case: Your design system needs to evolve
Sometimes, designers are complaining because the design system is not expressive, or complete, or adequate in all its parts. Some components may be outdated or useless for the current project. There might even be patterns and components that are misunderstood.
If sticking to the design system means damaging the user experience, something has gone very wrong.
This case is not a matter of creativity; it is a matter of usability. Using the design system isn’t helping you reach your product goals, and it’s limiting the product evolution.
If you’re using a design system that is not well maintained, is managed too rigidly, or does not accept modifications of any kind, your frustration and complaints are valid.
Ask yourself, why can’t your design system be modified?
Third case: You’re going off-road
Not all product initiatives need to stick to the design system like glue. There, I said it.
There are times where you need to launch divergent (and maybe a little crazy) experiments to feel out a new opportunity. Before you go fully off-road, you need to test it properly with an excellent user experience to see if it works.
Technical debt is not a huge concern in these situations, so these initiatives are often lavished with special treatment that goes beyond the design system. It’s a chance for the designer to prioritize freedom of exploration and creating an outstanding user experience.
If a designer is asked to go off-road but still navigate with the design system, it just isn’t going to work.
What are you complaining about?
Designers complain about the design system because they want to create unique experiences in total freedom, and they’re not really keen to talk to developers and product managers about the technical feasibility and budget for their wild ideas.
If you’re relying on your Figma file as the gold standard, you’ll only perceive the design system as a limitation. It’s time to be a team player and work with the design system. Design systems should support you in building most of your product interfaces.
If your design system is inexpressive, damaging the user experience, and doesn't evolve with the team, make sure your team and manager know. Try a UI upgrade. Your design system is not fixed in stone!
Finally, think about whether it’s worth using the design system and calibrating it for experimental projects. There are times when a business opportunity overrides the importance of sticking to the design system. Sometimes, you’ve got to color outside the lines.
∗ ∗ ∗
Want more insights?
- Why the marketing team just ruined everything
- Why is nobody using your incredible design system documentation?
- How do you know if your design system is giving you a return on investment?
Want a safe pair of hands to help with your own design system?
Check Design System Audit, our service to make sure your design system brings you results.
