It was by far my most intense experience with rewarding challenges. It lasted almost two years, but it feels like, I don't know, five?
Here, I briefly present some of my key contributions during the journey of evolving Hotmart's promising design system, Cosmos.
Previously, there was a component library in Storybook, but without Sketch assets for the design team to use. This library was a legacy adaptation of Bootstrap to Hotmart's style.
During this task, based on past experiences and conversations with other product designers and developers, I noticed some inconsistencies in Cosmos. The library was created without a deep understanding of the product team's needs and presented a verbose and confusing component structure. With that, I moved on to the next steps that I'll share below.
I decided to conduct research with the product designers (there were 17) to better understand the needs and opportunities of the DS. It consisted of two phases:
The library was clearly wordy, and I needed to understand the team's real need with the components. I launched a form with objective questions about the critical component variants. The results primarily showed: unnecessary variants, those that made sense, and those that needed adjustments.
A form question about choosing a button style for the course delete modal on the platform.