Background
Problem
When buying auto insurance, choosing one that meets your needs and your budget is important. Unfortunately, most insurance buyers get confused by the insurance jargon and don't understand their insurance options well. In addition, some don't know what they need. As a result, buying policies online seemed complicated and they relied on agents to assist with the process.
RBC Auto Insurance spends considerable time and money on onboarding policies offline. Ontarians have been reluctant to purchase policies online, but post-pandemic digitalization has grown. Therefore, this is an opportunity for RBC to digitalize sales and offer lower premiums to customers as they can now reduce overhead charges and commissions by selling policies online.
Our goal was to make it easier for buyers to understand and customize their auto coverages online for a convenient purchase.
My role & process
I worked alongside my UX manager, a content writer, a team of front-end and back-end engineers, and a legal team as the UX/UI designer.
Design reviews were conducted with the stakeholders.
Problem statement
Defining success
Value proposition
Research
From Guidewire's database, we extracted a list of coverages that fall mainly into two categories:
- Coverages applied to all vehicles in Ontario
- Coverages applied to per vehicle in Ontario
As you can see from the screenshot below, the coverage options are unstructured, and the page lacks organization.
We started by interviewing the underwriters and sales team to learn more about the coverages and how the underwriting rules play out. Here is the list of questions we posted to understand their approach when customizing the coverages with the customers:
We also studied our competitors to identify barriers and derive insights and potential points of emulation from competitive experiences.
Analyzing the data, we inferred that customers expect insurers to offer fast, adaptable, and up-to-date customization. To add value, we must assist customers in anticipating and eliminating risks rather than just paying compensation when things go wrong.
Exploration
After gathering data, we sketched low-fidelity wireframes on paper. We tested different layouts and finally decided on Layout 2, which we found is skimmable and displays coverages at the summary level initially, with the ability to drill into the details and customize options as needed. Development was made for a responsive website.
In the meantime, I worked with our content writer and legal team to thoughtfully analyze and simplify the coverages' copy to correspond to the design.
Converging on a design
After finalizing Layout 2, we focused on each component on the page to make it discoverable and easy to understand. Below is the design with our list of design considerations.
Evaluation and Findings
One-on-one, remote user testing was undertaken with 17 Ontarians. Participants used laptop/desktop/mobiles to interact with desktop or mobile versions of the website page:
4/5 participants felt that the layout and design made them feel compelled to review each coverage section.
We simplified the layout to create only two main categories - Included and Additional coverages. Also, the card designs have created a visual demarcation between different sections.
4/5 participants felt that there was an ample amount of scrolling required and the layout did not allow them to easily get a sense of was included / not included in their policy as they were customizing their coverage options.
We removed segmented controls as the exposed options increased the page length, and the customers had to read through the default options to find out what was included/ not included. On the other hand, checked boxes were easily perceivable as included and increased readability.
3/5 participants enquired about the discounts they qualify for.
Discounts played a significant role in making the purchase decision. Thus, adding discounts to the list of coverages gives a holistic view of the policy.
3/5 participants tried to return to the initial recommendations after making several changes.
Added a dynamic Reset button to reset to default selections.
3/5 participants missed the bottom section containing a list of documents to keep handy before buying as they were engrossed in the coverages.
Designed the list as a reminder that pops up on clicking 'Buy now' and proceeding.
On mobile screens, it took some time for users to scroll back to the top of the page.
Saw the opportunity to add a 'Jump to top' button.
Final design
We leveraged our Design systems that enabled shorter timelines and produced consistent design output across the journey. It also complies with Web Content Accessibility Guidelines (WCAG) AA standards to increase usability and reach a larger audience by requiring:
Currently, in the development stage, a demo of coverage customization with auto-updating price is shown below.
Next Steps
My closing thoughts: Document every little change and why it was made. This can save a lot of time when you circle back on an issue in a collaborative environment.