Digital teams do not have centralized guidelines and resources for design and code leading to tech debt and decreased efficiencies. By designing, building, and implementing a design system we are creating centralized design and code guidelines allowing product teams to streamline the design and development process.

Adopting a design system will streamline the design and development process leading to lower overall project costs. A unified look and feel will also lead to a more cohesive user experience leading to higher user satisfaction.

Claims

Diana Rios, Product Manager
Lazarus Pachigalla, Product Manager
Talia Bowles, Product Designer
Jennifer Chapman, Content Strategist
Vikas Lnu, Angular Developer
Mahmud Karim, Angular Developer
Rajini Challa, QA Analyst

03/08 - Medical claims summary and claim details
04/12 - Medical out-of-network claim form and claims you submitted
06/06 - Prescriptions claims summary
08/09 - Medical medical claim summary and claim details
09/13 - Dental claim summary and claim details
10/18 - Vision claim summary and claim details

QA collects screenshots and data of the current experience. Some parts of claims had not been touched in years so it was important for us to understand all the logic and function in the current claims experience.

Functional changes were out of scope. The two main priorities were: create a choesive look and feel, and implement the design system in the code.

Although functional changes were out of scope, we were able to implement some impactful content updates since content is a low development lift. Examples included simplifying paragraph-long error messages and creating an "out-of-network" claim form callout card on all of the claim summary pages.

As we finalized designs or questions came up, we worked with claims partners and past product owners to ensure that we were going in the right direction with the visual design and any content updates.

This was especially important while working on Medicare because of the added complexities of medicare compliance.

I joining daily stand-ups and weekly refinement calls to make sure the developers had time to ask questions and to address any edge cases that were revealed during the development process. I also owned the UAT process to ensure the designs were followed correctly in the development process

The QA Analyst, Lead Developer, and I conducted stakeholder demos prior to release for digital and non-digital stakeholders to share what changes were being implemented. This helped to demonstrate the power of the design system and also emphasize that we were not making any functionality changes.