Design System (Web) - Design System for a PRM Software Client

The Problem

Impartner faced years of inconsistency across its product offerings—no UI standards, interaction design best practices, or reusable components to streamline work for designers and developers. Consequently, as Impartner grew, they became more of a custom-dev shop for most new clients. This was one of a few reasons that Impartner was unable to easily support multitenancy. I was hired to create and implement a design system to serve as the foundation for new products and guide a company-wide refactoring of existing ones.

The Solution

Within months, I developed a TailwindCSS-based design system, documented it for designers and developers, and built a reusable component library in Storybook, all while designing Impartner's first multi-tenant PRM offering. Once adopted, the design system drastically reduced build times, simplifying onboarding and enabling faster client delivery. This efficiency allowed Impartner to launch its multi-tenant SaaS product more quickly, showcasing the power of an organized, versatile design system in streamlining processes and accelerating time-to-market.

My Role

Upon first joining the team, my role was Sr. UX tasked with creating the organization's first design system. As the design system gained adoption throughout several teams, my role naturally began to expand and I was promoted to UX Manager. I then began leading a team of talented product designers on multiple sub teams across a larger product team in building and expanding the design system to support our industry-leading SaaS product in the PRM space. My role consisted of creating, managing, and facilitating training of our design system across multiple teams of designers, PMs, and developers. I also began establishing new standards of UX research and testing.