Claim Tracking Redesign

Claim process redesign for large insurance company


The Problem

For a large insurance company, tracking claims are integral to customer security and trust. Customers want to know when their claim has been processed, when it’s moving along, and when they have items in the claim that they need to address. However, for customers using the app, there were a lot of issues with the claim tracking process. Steps were not clear, and it was hard to see how much time a certain process would take. In addition, information about a claim was hard to find through the current organization of the page.

The Solution

During my internship, a UX designer, content strategist, and I were tasked with coming up with a redesign for this process that would align with brand standards and website standards, and would create a better user experience. We would collaborate with developers, technology analysts, and UX researchers to determine the best solution that would help customers better understand where they were in the claims process and help better find important information relating to their claim.

My Roles

• UX Designer

My Team

• Me

• 1 UX Designer

• 1 Content Strategist

• 2 Mobile Developers

• 2 UX Researchers

• 1 Technology Analyst

Methods Used

• Understanding the Claims Process

• Preliminary Research on Current State of Claims Process

• Exploratory Design

• Information Architecture

• Usability Testing

• Iteration on Design from Usability Testing

Research Process

Understanding the Claims Process

Before I could design anything, I needed to understand how the claims process worked. How do customers file a claim? Once they file a claim, what are the next steps that they take? What are the different kinds of claims, and how are they different? Is there anything the customer has to do for the claim to keep progressing? How does the customer talk to the company, get repairs, and pay for services for their claim? In addition to learning all of this, I also had to understand

Steps were used to indicate where the user was in their claims process. In this redesign, we decided to also change the way that we designate the steps in the process. The old process consisted of 3 steps, but in the new progress, we decided to go with 5 steps that would be more descriptive of the status of the claim. The change would be as follows:

Old Claim Steps

1. Received

2. Recovery

3. Payment

New Claim Steps

1. Claim Filed

2. Estimate

3. Repair and Rental

4. Payment

5. Follow Up

Preliminary Research on Current State of Claims Process

I also needed to understand the current state of the process in the app, as well as what research and design had been done before I began my internship. I did a review of the current claims process in the app, and spoke with UX researchers about their criteria for a redesign.

Screenshot of the current claims tracking screen in the app

UX Researchers were able to supply me with key criteria for the redesign. Based on previous iterations of the claim tracking for the web, we were able to gather these facts from past usability tests:

1. Make sure the action items are visible on the screen

Most users were confused by red and gray bars only to indicate “Required” and “Recommended” tasks, so make sure the wording is present for each task

2. Make sure users know what tasks are “Required” and “Recommended”

Most users claimed they would click on ”Repair and Rental” in the timeline to request a rental, and some went to the action item for “Request a Rental”, so it was important to make the action items obvious.

3. Make sure there is a visual status to show the user’s position in the claim process

Most users preferred the page to have a visual indicator for the status.

4. Make sure all steps are shown on the screen with sufficient detail

Most users preferred seeing both completed and future steps in the claims process, and liked having lots of details about each step pertaining to their claim.

Design Process

Exploratory Design

Since this redesign was to take a new direction, I needed to understand how best to tackle the different sections of the process.

Visual Tracking

First, I explored the different ways I could design the visual tracking steps for the claims process. I researched competitors in order to understand how competitors were designing their tracking processes on mobile. This included Domino’s pizza tracker and Delta’s flight tracker.

The blue was an integral part of the design since blue was the design standard for insurance on the app. However, given the newfound design direction that the app was undergoing in order to align better to brand and alleviate colors, like blue, for different uses, I decided to shift the colors to red. Numbered steps were also important to include on the visuals, since it can better show the idea of progress towards the last numbered goal.

Circular Progress Indicator

Next, I explored the different ways I could design a visual to quickly represent the step the user was currently on. Since the web team was exploring the same topic, I collaborated with them to come up with a solution. The web team had come up with the idea of the circular progress indicator to denote the steps. In order to maintain consistency across channels, I adopted the circular progress indicator, and brainstormed different color treatments that would best indicate completed steps and current steps.

Accessibility issues caused me to stay away from different colors that could be misinterpreted through color-blindness for past, current, and future steps. I landed on a solution that maintained consistent colors, but clearly indicated the current step in the middle of the circle.

Action Items

Next, I explored the different ways I could integrate the action items into the new design. Previously, the action items were placed on cards, but had no indication whether or not the items were required or optional. There were also some concerns on the length of the screen, so I decided in addition to redesigning the cards, I would also come up with ideas to make the list of cards less minimal on the screen.

Since action items are so crucial, we decided that they needed to be more front and center than other items related to the claims process. Because of this, we decided to go with the redesigned cards that would clearly define which actions are required, and which are recommended.

Information Structure

In addition to the items important for tracking, I also needed to provide quick access to information related to the claim, like coverages, photos, payments, and claim information. I designed many interations in conjunction to the pieces above to understand the best heirarchy and importance of accessible information.

Information Architecture

1. What is the most important information to the user? This was deemed to be the current step the user was on in their claim, and what they needed to do next to keep their claim moving along. Because of this, we highlighted the current step and the action items all at the top.

2. How were we going to label certain items on the page? We had to ensure that the labeling was consistent in tone and voice, and was succinct enough for the user to accurately find information without overcrowding the screen.

3. What else is important for a user’s claim? Aside from tracking, we also had to consider the information contained within the claim, such as policy info, pictures, and payments, and how to properly convey where that information was stored. We created a hierarchy of information in order of most relevance for the user based on data gained from analysts.

Usability Testing

Usability Testing


1Hour In-Person Sessions

For these usability tests, one UX researcher asked each participant to perform a series of tasks on the claim tracking screen, including tasks such as viewing their progress on their claim, or uploading a picture to their claim. The UX Research time compiled the results of the test, and shared it to the design team.

Updates were made to create the final version of the screen as seen at the top of the page.

Claim Tracking Overview

Priority Level: Low

• Users liked the information on the page and thought it was useful.

• All users understood they were on step 1 out of 5 in the claims process.

• Users understood that they had 1 required action item and 1 recommended to complete.

• Users didn’t immediately notice the color differentiation between required and recommended. However, the recommended color bar was below the fold.

• In addition, most users mentioned wanting “Required” and “Recommended” to be larger and/or bolder on each card.


• Consider making the wording “Required” and “Recommended” slightly larger or in color on each card.

Claim Tracking Overview and Timeline

Priority Level: Low

• All users noticed “View your Timeline” and said they would click on it to view the full claims process.

• All users liked being able to see every step in the process, as well as what step they were currently on.

• Once viewing the timeline, a few users stated they would prefer to see the timeline before the claims details page.

• These users felt the timeline showed the action items and next steps more clearly.


• Consider showing customers the timeline first and giving them the option to view all details, if needed.

• OR consider giving customers information about the next step on the claims details screen.

Claim Timeline

Priority Level: Low

• All users liked having links embedded within the timeline.

• However, users thought these links were action items they needed to complete before moving on to the next step.

• Some users were confused about why “upload damage photos” was a link in the timeline, but not an action item.


• Align action items with timeline links whenever possible.

Steps in the Process

Priority Level: High

• Many users were confused about which step they were on in the process.

• Users assumed the action items were part of Step 1 until they saw the timeline.

• Although users understood they needed to get an estimate, when they saw the timeline, they felt they had to upload photos first.


• Allow users to see a visual representation of their in-progress step on the status icon (e.g., partially filled out line, dashes, etc.).

Uploading Files and Photos

Priority Level: Low

• All users said they would click on “Files and Photos” and “hope” it would give them an option to upload files and photos.

• A few users assumed it would have wording to add files/photos when no files/photos have been uploaded yet.


• Consider adding wording or an “add” button, so users know they have the option to add photos. As a possible alternative, add photo uploads as a recommended action item.


What I Learned

• Collaboration across teams is essential to align with design goals and to make sure everyone is on the same page.

• Designing in industry is a lot different from designing in academia. A lot of shortcuts have to be made for the sake of time and resources. However, as designers, we have to be flexible and adapt to achieve great experiences for our users.

• For every questioned answered about the product space, there will be 10 more to take its place. Communication is key to understanding the problem space to address it properly and holistically.

• My Sketch and Invision skills improved as I learned more about symbols, libraries, and plugins to streamline the prototyping process.

Future Considerations

• Based on UX research, users liked seeing the timeline more than the overview. How might be design the timeline into the forefront of the experience?

• How might be integrate all aspects of the claim process (action items, uploads, steps, and timeline) into one seamless experience?

• How might be redesign the circular progress indicator to be more indicative of the user's steps in the process (if a visual indicator is needed at all)?