I was responsible for developing the initial web component library for our design system using React. To showcase the available components, I created a "Storybook," a tool to build and display UI components in isolation. I worked closely with the design team to define the different types of components, such as primary, secondary or tertiary for a button component. We also defined their expected behavior, visual style, and accessibility features. Accessibility was crucial, especially in healthcare applications, so we ensured every component was fully accessible to the user.

My role also involved getting the developers' buy-in. I met with various development teams across Aetna to understand their diverse component requirements. After the components were ready, I guided teams on how to use them, answered their questions, and persuaded them to use the updated components in their library. Persuading the developers was challenging at times because replacing the old components with new ones increased the teams' tech debt. However, due to the components' code quality, ease of use, and reliability, we gained more trust with each new component released.