Leading a Design System Initiative
Problem Statement:
How might we develop a comprehensive design system that provides a unified set of design principles, components, and guidelines tailored to the diverse needs of our brands, enabling:
-
Consistent and high-quality user experiences across all touchpoints.
-
Streamlined collaboration between design and development teams.
-
Enhanced scalability to support future growth and new partnerships.
-
Efficient utilization of resources, allowing teams to focus on innovation rather than redundancy.
Old Netspend System
Netspend had just been purchased, 2 weeks after I was hired, and the new leadership launched a huge rebranding initiative with a very tight deadline of 3 months. As a new employee I wanted to hit the ground running and use my unique skillsets to be of immediate value, however, with all the moving pieces, hires (and departures), I found myself caught in the riptide of production.
I noticed that designers were creating the same elements, and with no rules or orchestration, and set out to create that value I sought to contribute.
New Netspend Design System
New Netspend Design System
My process was simple. Design systems weren't unprecedented, and so I took some of the best in class design systems to audit and see what we could fashion at Ouro.
Documentation
I also had to document, not only the process, but also our principles and guidelines for our Foundational elements and our components. And so I opened a zeroheight account to try and platform our work so all stakeholders could access. Currently working on the content deck to present for platform procurement.
In the meantime...
Our developers and designers still needed guidance with component anatomy and behavior and we still needed to host our documentation somewhere, so I took the work I had started in Zeroheight and surfaced them in a Figma file to share out to our teams, until Zeroheight is brought online.
UI Components in play:
P2P
Under construction:
Stay tuned!
New updates and Insights being added to this use case.