Like the real estate industry before Zillow, the insurance industry is a black hole of guarded data, reliant on error prone email chains and phone calls to solve problems for employees whose lives sometimes depend on timely info.
Fortunately we had years of research and CS data to guide the scoping and requirements process. We were able to quickly define goals for our users, our business, and our teams.
The system map highlighted existing features, those necessary for V1 , and ideas for future versions. This guided the design of a flexible interface, a robust data architecture, and scalable APIs.
These brought to life core task flows, ux interactions, and helped development teams spec their work. This is a great phase for collaboration where good annotations/communication are key to success.
At this stage part of the design team could move on to wire framing the next needed sections while some stayed on to keep up with needs of the final implementation and testing.
Making Health Care Coverage Work for Employers and Employees
Our goal was to take the complexity out of selecting medical insurance for both employers and employees. To achieve this, I conducted as much research as time allowed and leveraged the knowledge of our CS and Sales teams to design more personalized experiences for our users.
In the benefits industry things happen in a yearly cycle, so the product needed to meet people where they were throughout the year. This chart identified our core users in each phase of the cycle and features they needed to support them.
Presenting the data from different carriers in a clear format and enabling employers to interact with it helped them compare options, leading to more informed decisions about what they could offer their employees and increased satisfaction.
High Fidelity Wireframes helped us run usability tests. From those brief tests it was clear that we needed to lift the burden of comparing details of plans from the employees and give them a guided experience based on their needs.
As one of two designers that designed the original Zillow experience I was responsible for overall site architecture, core task flows, and personalizing property detail pages for different core personas.
Documenting the process for agents and owners included identifying the necessary screens, what data needed to be collected, and possible page states in the process. This helped define requirements and engage with development early on so we could meet target dates.
The posting process was put into a single work area rather than multiple pages to increase chances of completion. If I were designing this today I would utilize AI to auto generate a listing page for the owner or agent to approve and remove the tedious task of filling in information.