Establishing and advocating for the design system value and ROI.
Role: Product Designer
This project aimed to standardize all rInsights products for multiple brands, using the same base of components to create a unified language and a robust ecosystem. Using MUI V5.9.0 as a base, I set up our component library to set the ground rules for the components. After further auditing rInsights platforms' current uses and gaps, I created a design system using reusable patterns.
“A scalable framework of decisions & team behaviors across a product portfolio to converge on a cohesive experience.“
Nathan Curtis
A design system will save us time and money while improving UX. Without a Design System, designers and developers spend about 30 minutes a day on one of the following:
Can we rebuild this? It doesn’t match the design.
What’s the latest documentation?
Where are our components?
Was this pattern used somewhere else?
What’s the latest documentation?
Where are our components?
Was this pattern used somewhere else?
Some of the significant questions that designers and developers may have during the collaboration process, and with proper design system setup and documentation, can be faster and more efficiently resolved.
During this project, I adjusted the design system components. I developed documentation defining component usages, states, specs, and general principles to guide design and development teams during the implementation phases. The system was a single source of truth for designers, developers, and all other stakeholders. It was also an educational tool and reference, e.g., for quicker onboarding.
This project allowed me to define and standardize design patterns and component behaviors in similar products for multiple brands. Additionally, through this exercise, I further learned that a design system has a huge impact on creating more quality and consistency across products, channels, and teams, and faster time to market.
