Novo Driver App

Designing the core experience of a telematics-based insurance app. Where driving behavior determines your insurance premium.

Lead Product Designer
iOS & Android
Shipped
Novo Driver App held in a cafe: the Driver Board screen showing a Safety Score of 88 and the latest trip

Defining the driver experience

Novo Driver App home screen: driving summary with a live Safety Score of 90, estimated premium, upcoming payment, and rate simulator Novo Driver App Driver Board screen: a Safety Score of 90 with breakdown cards for hard brakes, rapid acceleration, high speeds, and distance driven Novo Driver App Insurance screen: policy vehicles with coverage details for bodily injury, property damage, and medical payments Novo Driver App Billing screen: upcoming autopay, billing history, and managed payment methods Novo Driver App Trips screen: a list of recent trips with route maps, distance, event counts, and points earned

The Novo Driver App is the policyholder's core experience. Telematics data tracks real driving behavior, hard braking, rapid acceleration, speeding, and feeds a live Safety Score that influences the premium.

Safety Score gauge legend: Min 1 to 50 in the red zone, 51 to 61 average in the yellow zone, 62 to 100 above average in the green zone, max 100 Safety Score gauge design spec: 50 degree center arc, 65 degree side arcs, and 8px border-radius on the segment ends
Safety Score card showing a low score of 30, needle in the red zone Safety Score card showing a mid score of 60, needle in the yellow zone Safety Score card showing a high score of 90, needle in the green zone

The app also handles onboarding, document upload, insurance documents, claims filing, and personalized engagement. I own the end-to-end design.

Enabling self-service everywhere

The core principle is self-service first: instead of customer service reps shepherding users through each step, in-app flows let customers complete critical tasks themselves, on their own time.

01

Document & Photo Upload

Document & Photo Upload interaction flow

New customers need to provide supporting documents: vehicle photos, proof of prior insurance, driver license. Previously a rep collected them by email or phone after signup, and completion hovered in the low forties.

Building upload directly into onboarding, surfaced immediately after the app download, moved the task to when attention and motivation are highest.

Before
  • CSR contacts customer post-signup by phone or email
  • Customer manually sends documents on their own
  • No in-app prompt or guidance
  • Momentum lost between signup and outreach
After
  • Upload step presented immediately after app download
  • In-app guided flow with clear instructions
  • Task completed while intent is highest
  • No dependency on CSR scheduling
Design Principle

Timing is a design decision. The right task at the right moment often matters more than the task itself.

02

Multi-Driver Policy Setup

Multi-driver policy setup flow: the blocked-access screen gating insurance documents until every driver on the policy completes app setup and vehicle pairing

Every driver on a policy must install the app and pair it to a vehicle. For multi-driver households, completion collapsed, because you can't control what other people do: under 10% of multi-driver policies finished setup.

My redesign gated the value: the primary policyholder can't access their insurance documents until every driver completes setup. That one change put direct, personal motivation to follow up exactly where it belongs.

Multi-driver setup screen: all drivers must download the app and enable permissions, with a remind drivers action Multi-driver setup screen: pairing each vehicle so Novo can calculate the premium accurately Multi-driver setup screen: setup complete, the Novo account is now active
Design Principle

When you need multiple people to act, find the one with the most to lose and make sure they feel it. Peer accountability does the rest.

03

In-App Claims Filing

End-to-end crash-detection claims flow: a crash-detection screen branching through emergency triage into 911 and Novo CSR paths, then a self-service sequence covering incident details, vehicle drivability, damage capture, other-driver details, and submission

Filing a claim is one of the highest-stress moments a customer has with their insurer, and there was no in-app path: call or email, then wait.

I designed an end-to-end claims flow covering collision, glass, and comprehensive damage. It opens with an emergency triage step that confirms the customer is safe, then routes to a CSR or self-service.

The self-service flow captures all necessary information:

01Date, time, and location of the incident
02Which vehicle was involved (covered policy vehicle or rental)
03Visible damage: location on vehicle and description
04Photo uploads of the damage
05Vehicle drivability and airbag deployment status
06Injury reporting
07Third-party information: driver's license and insurance card upload
08Police report confirmation
Claims flow screen: when did the accident happen, date and time inputs Claims flow screen: where did the accident happen, address field with map and adjustable pin Claims flow screen: which vehicle was involved, choosing between policy vehicles or other Claims flow screen: who was driving the vehicle at the moment of the accident Claims flow screen: is there visible damage to the vehicle, yes or no Claims flow screen: tap to highlight all damaged areas on a top-down diagram of the car Claims flow screen: describe damages free-text field with voice input Claims flow screen: upload photos of the damage Claims flow screen: is the vehicle drivable, yes or no Claims flow screen: were the airbags deployed, yes or no Claims flow screen: were there any injuries, yes, no, or not sure Claims flow screen: upload the other party's driver license and insurance card Claims flow screen: was a police report filed, yes or no

After submission, customers track claim status and an estimated resolution timeline in the app. The feature is designed and ready for launch.

Stakeholder Impact

In design reviews, customer service reps consistently reported these features cut their inbound volume of routine requests, freeing them for the issues that genuinely need human expertise.

Results that speak for themselves

Each metric reflects a fundamental redesign of how customers move through a step.

Document Upload Completion
Was: low 40s%
90%+
From reactive CSR outreach to in-app, immediate onboarding prompt.
Multi-Driver Policy Setup
Was: <10%
68%
Gating policy access drove peer accountability and full household setup.
Customer Churn Rate
Was: 25%
5%
Across all features shipped, churn dropped from a quarter of users to nearly negligible.
Novo Driver App screen: confirming the 2023 Ford Escape is connected so only trips taken in that vehicle count toward the Safety Score
NPS Score
50+
App Store Rating
4.5★
Churn Reduction
20%
Setup Improvement
2x

What pulls users back?

There's no inherent reason to open an insurance app every day; most are opened reactively. The safety score creates a pull-based engagement loop: it updates with every drive, so customers have an ongoing reason to return. Did that commute help or hurt?

Personalized coaching reinforces the loop. The more driving data accumulates, the more targeted the feedback, a habit grounded in genuine usefulness rather than manufactured urgency.

Novo Driver App trip detail screen: a mapped route with time, distance, event counts, a 5-star rating, and points earned Novo Driver App Insights screen: monthly trend charts for Safety Score and hard brakes with a tooltip showing a daily score
Design Rationale

A score that changes every time you drive is a variable reward. Real stakes, real feedback, and a visible number to improve: a retention mechanism that doesn't feel artificial, because it isn't.

What worked (and what I'd revisit)

The self-service model produced step-change improvements every time it was applied, consistent enough to become a design principle: if a task can be completed in-app, it should be. The safety score loop worked too, but mostly for customers who already drive safely.

Known Limitation

The experience is optimized for drivers who score well. For those who don't, it risks feeling punitive: a constant record of what they're doing wrong, pushing out the customers most in need of improvement.

The business model self-selects: better drivers stay, worse drivers churn. Workable short term, but not the vision. That's the challenge behind Good Miles: using positive reinforcement to retain the drivers who are struggling instead of letting the product push them away.