<?xml version="1.0" encoding="utf-8"?>
Open full project

This project was born out of my personal experience as an independent adjuster in the auto insurance industry. For years, I've witnessed firsthand the confusion and frustration that car repair estimates cause for insured customers. After an accident, the last thing people need is to be bombarded with a five-page document filled with technical jargon and convoluted processes. It's like trying to read a foreign language while still recovering from a concussion (which, ironically, is how I felt when I first saw my car repair estimate after an accident!).

I was driven by empathy for insured customers and a desire to improve their experience. I took on this project independently. No external client or boot camp was involved; it was purely a self-initiated endeavor fueled by my passion for user-centered design.

The main objective of this project was to increase user comprehension of car repair estimates by 50%, as measured by a post-use questionnaire. I wanted to create a digital tool that would translate the complexities of these estimates into a clear, concise, and user-friendly format. Essentially, I aimed to empower insureds to understand the "what" and "why" of their repairs, giving them the knowledge to navigate the process confidently.

Goal

To achieve this objective, I focused on several key areas:

  • Simplifying language: Replacing technical jargon with plain language and providing clear definitions for any unavoidable technical terms.
  • Improving visual clarity: Using visuals like diagrams, illustrations, and interactive elements to explain the damage and repair process.
  • Enhancing navigation: Creating a user-friendly interface with a clear information hierarchy and intuitive navigation.
  • Building trust: Presenting information transparently fosters confidence in the estimate and trust in the repair process.

As the sole designer on this project, I wore many hats. My responsibilities included:

  • User Research: Conduct surveys with insured customers to understand their pain points and needs regarding repair estimates.
  • Persona Development: Creating representative user personas based on my research to guide the design process.
  • Information Architecture: Defining the structure and organization of information within the tool to ensure clarity and ease of use.
  • Prototyping: Designing and developing prototypes to test and refine the user experience.
  • Visual Design: I created a visually appealing and user-friendly interface, considering factors like color scheme, typography, and imagery. I also made the logo, branding, and company name.

This project was my passion. It allowed me to combine my industry expertise with my growing UX/UI skills to create something that could benefit people. It was a challenging but rewarding experience, and I'm excited to share the outcomes and insights I gained.

Visit my website for the entire project. Thanks for stopping by!

https://www.jonathandavila.com/p/c6eb1b9b/c2718097

Tools used

Figma

Topics

Share

Share your insights — leave a project review and help others grow their skills

Reviews

2 reviews


Hi Jonathan! This is amazing how inner passion drives truly meaningful solutions. Great storytelling! I admire how you identified the problem and took actionable steps to address it. One suggestion: consider complementing the UI screen with UX elements, like user flows and insights into how the app will function. Highlighting relevant features and workflows will make your project even more impactful!

Yuliia

Ahh, you're right! Thank you very much for the encouragement and advice. I have noted this and will get to it soon enough. I'll be honest: putting my work out there is intimidating, but this helped. Thank you for being kind and honest. I also noticed I spoke SO much about estimates. I didn't stop to think that most people don't know what an estimate looks like in car insurance. I feel I need to add that to contrast and make it more transparent. Would a carousel or a before-and-after mockup of the estimate and our estimate suffice? Sorry in advance if I'm asking too much.
Hi Jonathan. The question you asked fits perfectly into the ideation phase of your project. At this stage, with research insights, competitive analysis, and an understanding of your target users' perceptions in hand, you can start to brainstorm broadly and creatively on potential solutions. Before diving into design, it’s worth exploring how users perceive and interact with estimates. For example: - How do users think about estimates? - Does the perception of an estimate vary between different users? - Is there a difference in how users feel about estimates immediately after an incident versus a few days later when filling out a form? - Could someone other than the car owner be responsible for filling out the form? How these people think about estimates? By answering questions like these, you will likely already have the artefacts needed to visualize how the product could look based on these findings. Hope this answer was helpful :) Yuliia
It sure was ty! I've added a user flow for now and will keep at it over time.

Hi Jonathan,

The design shows great improvement and thoughtful execution. The dark theme with contrasting accents feels modern, while the clean typography (Lexend Giga and Poppins) ensures clarity.

The accordion structure for "Areas Damaged" simplifies navigation, and using plain language and visuals enhances user understanding.

A few tweaks could make it even better:

  • The light blue (#00FFFF) on black struggles with contrast—adjusting the color slightly could improve accessibility.
  • The "Create Estimate" button is bold but competes visually with smaller icons nearby. Increasing its prominence would strengthen the call to action.
  • The "Total Cost" section could benefit from more visual emphasis to guide user attention effectively.

Overall, a strong, user-centered design with room for minor improvements! Great job!

Thanks a million for the input. I see what you mean by light blue; it is a bit aggressive now that I look at it. Thankfully, the initial contrast ratio was 16:45:1, but I got it to 17:78:1 by changing it. It looks much better, ty! Edit: Total cost- I increased the font size, gave the stroke more weight, and bolded the cash amount. Create estimate: I filled the button with light blue and bolded the font. I will review it and get feedback to assess whether it helps. Thanks again.
(edited)
Glad that was helpful

18 Claps
Average 3.6 by 5 people
5 claps
4 claps
3 claps
2 claps
1 claps
<?xml version="1.0" encoding="utf-8"?>