When hired, the first thing I did was a full platform level analysis which allowed me to identify design issues with fresh eyes. My main takeaways were that the platform was built to 'work', but lacked design quality because InsuranceMenu is an engineering driven org with no previous designer. This resulted in many overly complex workflows, high data density without defined hierarchy, no clear color or typography system, and numerous alignment/spacing issues.

After my own platform analysis, I turned to our user base to test the existing product and determine current product impressions, identify significant pain points, and categorize our different user types.

Through this, two distinct user types emerged: one tech savvy persona looking for efficiency (Amelia), and another tech novice persona looking for simplicity and ease of use (Martin). As I was designing, I always had these 2 personas in the back of my mind so I could create a seamless, intuitive user flow for users like Martin, while also providing advanced features for users like Amelia.

At this point, I had enough confidence in my research findings to develop wireframes for testing. I created the entire flow using a Figma prototype and tested the design with a group of users.

After we completed testing and iteration on the wireframes, we felt confident moving into high-fidelity design. A big problem with the current platform was the inconsistency throughout the platform. An obvious approach to combat this (and modernize the design delivery process) was to build a scalable design system based on modular components.

After multiple rounds of testing, the designs were validated and finalized. Our team was now ready to begin working on the redesign project, but unfortunately there was a turn of events in the organization. Our VP of product left and the organization made the decision to redesign our platform from the ground up instead of the UI revamp I worked through. That work is continued in V2 project of InsuranceMenu.

Reflecting on this project a few years later, there are definitely quite a few design decisions that I would have made differently if I were to start the project again (it's always bittersweet looking at your designs of old!). In general, they revolve around some of the design fundamentals when it comes to designing SAAS software (i.e. alignment, typography, hierarchy, color usage).

One practical example would be around the decision to heavily rely on card containers and a center aligned layout. With current SAAS software, a more open layout that does not rely on cards is generally more effective to best utilize space and set up the platform for future success.

Beyond that, I would generally take a more subtle approach to some of my design decisions (i.e using simple text links instead of overt buttons). Overall, I am happy with the result and feel there were significant improvements to the platform.