SaaS companies are in the business of simplification. They make it easier for people to reach their goals, such as tracking sales performance, managing customer databases, and customizing marketing outreach.
According to Ryan Matthew, a founding partner at Neuron, a UX/UI design agency, design systems are a key factor in SaaS companies’ ability to maintain consistency and scale their product suites.
“A design system is essentially a collection of reusable elements that serve as the foundation for creating consistent and cohesive user experiences across various products and features,” Matthew says. “It includes everything from colors, typography, and spacing to icons, buttons, data tables, and every other UI element.
DESIGN SYSTEMS: LEGOS FOR PRODUCT DESIGN
Matthew compares design systems to Legos. Like elements of a design system, Lego pieces come in different shapes, sizes, and colors.
“Individually, each piece in a design system appears simple,” he says. “However, when thoughtfully compiled, they create a library of different elements that are the building blocks of a product’s interface.”
Matthew explains that design systems enable product managers, product design teams, and developers to streamline the development process, facilitate cross-collaboration, and maintain brand consistency at scale.
“By creating a unified set of rules within a design system, every aspect of a SaaS product’s interface can adhere to those established standards, resulting in a more cohesive and intuitive user experience,” he says. “Better user experiences translate to more revenue—in essence, design systems are one of the cornerstones of successful and scalable SaaS.”
THE IMPORTANCE OF CONSISTENCY FROM A USABILITY PERSPECTIVE
While the importance of consistency in a brand’s look and feel is widely understood, Matthew stresses that it’s also crucial from a product usability perspective.
Consider Adobe’s product suite—whether someone is in Photoshop or InDesign, they know they’re working in the same product universe.
“With Adobe’s product suite, the design standards are consistent—and predictable,” Matthew says. “From a usability standpoint, that’s vital because users can easily navigate between those different tools.”
“It also communicates a level of professionalism and togetherness that is somewhat subconscious and that ultimately helps build and maintain customer trust,” he says.
Matthew notes that it’s not “uncommon” for SaaS companies that have multiple products in their product suite to have different design elements in each, such as a different navigation structure or a different set of search controls. He stresses that it’s a matter of striking a balance between consistency and flexibility.
“It’s about finding that sweet spot,” Matthew says. “While it’s crucial to maintain consistency across products, it shouldn’t be overly prescriptive. There should be room for adaptation to accommodate unique features and use cases. Designers should also be able to address edge cases, such as a part of the product with certain UI elements that don’t exist elsewhere. But having a set of guidelines helps with alignment across all products and features.”
BEST PRACTICES FOR BUILDING DESIGN SYSTEMS
Over the years, the Neuron team has helped various SaaS companies build design systems.
“In our experience creating next-gen design systems for various companies, we’ve realized that there’s no one-size-fits-all way to create a design system,” Matthew says. “Every product is built differently, and every product team is structured differently, so the design system must be created with each company’s unique needs in mind. For a design system to be useful, it has to actually be used.”
However, Matthew notes that over the years, he and his team have found some “universal truths” about best practices for building design systems. First, he urges SaaS stakeholders to choose the right platform to build their design system.
“There are a few design tools that you can use, but we strongly recommend Figma,” Matthew says. “It’s the industry standard and is powerful and intuitive—it has all the essential capabilities you need to create and future-proof a design system. But that being said, it’s important to choose a design tool that your designers are familiar with.”
Matthew adds that Storybook, an open-source solution that developers can use to build, test, and document UI components, can be integrated with Figma—enabling developers and designers to work together more efficiently.
“Storybook is essentially a design system in coded form; it helps bridge the gap between design and development,” Matthew says.
Matthew also advises stakeholders to conduct due diligence on your DesignOps, specifically, auditing existing design elements and identifying opportunities for standardization.
“At a minimum, this would include solidifying factors like brand colors, typography, and spacing,” he says. “Having those elements in place before implementation will make restructuring and componentizing your design elements much easier. Additionally, it’s the key to creating consistent user experiences across all of your products and services.”
Then there’s adaptability.
“Coming up with clear naming conventions and standardized variables to facilitate reusability across different use cases is vital,” he says.
According to Matthew, design systems should not be set in stone. Instead, teams should always be updating them.
“Treat your design system as a living document,” Matthew says. “If design systems aren’t maintained and updated, they’ll lose value. It’s good practice to incorporate regular maintenance into your workflows and get buy-in from everyone on your team to ensure it’s being used and updated consistently.”
Finally, Matthew recommends that SaaS stakeholders not be afraid to seek expert advice when addressing design system deficiencies.
“Whether it’s tapping into internal expertise or partnering with external agencies, leveraging these insights from DesignOps specialists can accelerate the process and maximize the chances of success and longevity for the design system,” Matthew says.
HOW TO GET THE MOST OUT OF DESIGN SYSTEMS
Once a SaaS company has a design system in place, Matthew explains, they can get the most out of it via internal education and governance.
He says that education involves providing team members with training sessions and documentation to help them become familiar with the design system and how it’s intended to be used.
“Hands-on practice and feedback sessions can help boost confidence and ensure smooth integration into daily work,” Matthew says. “The last thing we want is to go to this great length of putting together a comprehensive design system only to have it fall apart when it’s put into use.”
He adds that as a design system evolves, key stakeholders need to stay in the loop about changes.
Regarding governance, Matthew recommends having a dedicated person or small team in charge of maintaining the design system over time.
“This team would be responsible for updates, troubleshooting, and making sure that the design system is meeting the needs of the team and company as a whole,” Matthew says. “Accomplishing that involves regular check-ins to get feedback from team members, as well as religious version control.”
Ultimately, Matthew stresses, design systems should help facilitate collaboration among teams so that companies can better serve their end users.
“A design system isn’t just a static rulebook,” Matthew says. “It’s a dynamic ecosystem intended to fuel efficiency and collaboration. By investing in design systems, companies can improve scalability, elevate the overall user experience, and ultimately, drive success in the very competitive landscape of SaaS.”