Product Design Case Study

Digital Auto Insurance Quote

Quoting car insurance asks a lot of questions for good reasons. My job was to make that complexity feel less like paperwork and more like a clear, predictable conversation.

RoleProduct Designer / UX/UI
CompanyTokio Marine
ScopeUX · UI · Prototyping · User Flows · Usability
PlatformResponsive Web
Duration16 weeks
Year2025
My Role

I led the product design work across the quote journey, translating business, user, and technical constraints into flows, prototypes, and final experiences. I worked closely with Product, Business, and Engineering to define priorities, evaluate trade-offs, validate design decisions, and evolve the experience through iteration. My responsibilities included journey definition, UX/UI design, prototyping, interaction design, usability validation, design handoff, and maintaining consistency with the broader product ecosystem.

Built around real people,
not perfect scenarios.
Product thinking + craft

Interface studyScroll to unpack the thinking ↓

The setup

What was really going on.

The business wanted to expand direct digital sales without losing the confidence customers expect when purchasing a financial product. The experience needed to collect accurate underwriting information, explain coverage responsibly and keep people moving through a relatively long quotation flow.

Key constraints

  • Mandatory underwriting and consent data
  • Pricing depends on vehicle, driver and location variables
  • Insurance language needed to remain precise but understandable
  • The journey had to support both confident and first-time buyers
01

Where it got messy

Buying auto insurance is a high-consideration journey involving vehicle information, driver profiles, coverage decisions, pricing, and regulatory requirements. The challenge was to reduce the perceived complexity while preserving the information required by the business. The experience needed to explain what was being asked, maintain confidence, and reduce unnecessary cognitive load throughout the quote.

02

What I designed

The solution reorganized the quote into a clear step-by-step journey using progressive disclosure, stronger information hierarchy, contextual guidance, and predictable interaction patterns. Long forms became manageable stages, related information was grouped, progress remained visible, and plan options were structured for clearer comparison across responsive layouts.

03

What changed

The redesign made the quote more consistent and easier to follow while preserving underwriting and business requirements. Performance numbers are confidential, so I am careful not to claim a conversion uplift here. What I can show is the reasoning, interaction model and clearer journey that became part of Tokio Marine’s evolving digital experience.

  • Clearer journey structure
  • Reduced cognitive complexity
  • More consistent interaction patterns
  • Stronger responsive experience
  • Reusable patterns for future quote improvements
From complexity to clarity

What changed

The redesign was less about removing required information and more about changing how and when that information was presented.

Before

A long, cognitively heavy quote flow

After

A progressive journey broken into clear, manageable stages

Before

Too much information to process at once

After

Related information grouped and progressively disclosed when needed

Before

Vehicle and profile information that could feel repetitive

After

Lookup, prefilled information, and confirmation patterns that reduce unnecessary effort

Before

Coverage choices that were difficult to compare

After

Plans, benefits, and relevant information structured for clearer comparison

Before

Limited sense of progress through the quote

After

A persistent, predictable progress structure across the journey

How I worked

Messy problem, clear path.

  1. 01Funnel & Behavioral Analysis
  2. 02Journey Simplification
  3. 03Conversion-focused Prototyping
  4. 04Usability Testing & Launch
Discovery

Before opening Figma.

I started by listening for the moments where the experience stopped making sense.

Methods

Research details are intentionally omitted pending factual confirmation.

Key insight

Customers were willing to provide detailed information when they understood why it was needed and could see meaningful progress. Abandonment increased when questions felt repetitive or when coverage differences appeared only at the end.

Opportunity

Build trust progressively: explain each data request in context, reuse known information and introduce plan value before asking the customer to commit.

Design rationale

Why it works this way.

01

One clear objective per stage

Problem
The quote required users to process several categories of information in one journey.
Decision
Separate personal, vehicle, driver, coverage, and quote information into focused stages.
Rationale
Grouping related questions made the journey more predictable and reduced what users needed to process at once.
Effect
Users could focus on one decision at a time while maintaining a clear sense of progress.
02

Vehicle data without repetition

Problem
Entering and validating detailed vehicle information created repetitive effort.
Decision
Use license-plate and reference-data lookup to prefill vehicle details for confirmation.
Rationale
Reusing available information reduced typing while keeping users in control of corrections.
Effect
Vehicle identification became a shorter confirmation task instead of a long data-entry step.
03

Guidance at the moment of doubt

Problem
Insurance questions and terminology could interrupt the journey when users needed clarification.
Decision
Place concise contextual guidance from Marina alongside complex questions.
Rationale
Answering questions in context avoided sending users to a separate help flow.
Effect
Users could understand the request and continue without losing their place.
04

Plans designed for comparison

Problem
Coverage, deductible, price, and optional services were difficult to evaluate together.
Decision
Organize the choices in parallel plan cards with a consistent information hierarchy.
Rationale
A shared structure made meaningful differences easier to scan without hiding important details.
Effect
Users could compare value and make a more informed coverage decision.
Product decisions

Key trade-offs

Simplifying the quote did not mean removing business-critical information. Several decisions required balancing user simplicity with underwriting, technical, and commercial requirements.

User simplicity vs. required data

We reduced perceived complexity through grouping and progressive disclosure while preserving the information required for pricing and underwriting.

Speed vs. confidence

The journey needed to feel fast without hiding coverage information users needed to make confident decisions.

Flexibility vs. consistency

Interaction patterns needed to support different insurance scenarios while remaining predictable across the journey.

Mobile space vs. information density

Complex insurance information had to remain understandable on smaller screens without overwhelming the interface.

Test, learn, repeat

What feedback changed.

The design evolved through iterative evaluation of the flow, hierarchy, guidance, controls, and recovery patterns.

Initial approach

The early direction organized the required quote information but still placed too much content and guidance within individual steps.

What we learned

The experience needed a stronger sense of progress, shorter supporting copy, and clearer controls at key decision points.

How the design changed

The flow was divided into more focused stages, helper content was reduced, selection patterns became more explicit, and recovery information remained available.

Final direction

The final structure made each step easier to scan while preserving the data, coverage detail, and continuity required by the product.

What we could verify
Business metrics are confidential. The redesigned experience established a clearer and more consistent foundation for Tokio Marine’s digital quote journey.
Looking back

What I’d carry forward.

This project reinforced that simplifying a complex product is not the same as removing complexity. Insurance still requires detailed information, business rules, and confident decision making. The design challenge was to reveal that complexity progressively — giving users the right information at the right moment while keeping the journey understandable and predictable. If I were evolving the product today, I would continue looking at where users hesitate or abandon the journey, validate opportunities for greater personalization, and use behavioral data to inform the next iterations.

Want the full story?

I’m happy to walk through the decisions, constraints and details behind the work.