Cambridge Mobile Telematics
2024–2026
DriveWell Advance
Implementing insurer-specific versions of a shared telematics product across 40+ customer-branded apps.
Role
Product Designer
Timeline
2024–2026
Team
Customer Success, Engineering, Product, and QA
Platform
iOS and Android
OVERVIEW
One platform, many insurance programs
DriveWell Advance gave insurers a shared telematics product that could be configured around their program, brand, and customer experience. Each implementation could vary in scoring, incentives, navigation, onboarding, policy states, content, colors, and imagery.
I owned the design implementation of approved customer configurations, translating solution specifications into complete application files and maintaining them as programs evolved.
Shared DriveWell Advance Foundation
Core product, established feature flows, components, and typography
Configurable Experience
Scoring, incentives, navigation, onboarding, policy states, content, colors, and imagery
Customer Implementation
A complete experience tailored to the insurer’s program and brand
SHARED PRODUCT
A shared product, configured for each insurer
Each customer implementation balanced a consistent DriveWell Advance foundation with insurer-specific decisions across scoring, driver value, navigation, onboarding, lifecycle, content, and brand expression.
Area
What could change
Scoring
Behavioral or Premium scoring
Driver value
Projected discount, estimated savings, or rewards progress
Navigation
Tab structure and access to features like Rewards or Family Sharing
Onboarding
Text message, email, or both
Policy lifecycle
Expiration timing, re-enrollment, and end states
Content
Labels, instructions, terminology, and program language
Brand expression
Colors and limited insurer-selected imagery
Typography, core components, and established product flows remained shared across implementations.
IMPLEMENTATION
From approved specification to maintained product file
My role began after major program decisions had been confirmed. I reviewed the specification, identified affected screens and states, applied the configuration across the product, prepared final files for delivery, and remained design owner as requirements and brands evolved.
01
Review
Review the approved specification, identify affected screens and states, and surface missing or conflicting requirements.
02
Configure
Apply scoring, incentives, navigation, onboarding, lifecycle, content, and brand decisions throughout the experience.
03
Deliver
Incorporate feedback, connect final designs to Jira, and support engineering with assets, styles, and implementation questions.
04
Maintain
Own the customer file as requirements changed, new features were introduced, or the insurer’s brand evolved.
Customer implementations extended across core journeys, feature details, and supporting states—not just the primary dashboard.
PUBLIC EXAMPLE
One implementation in the wild
COUNTRY Financial’s DriverIQ is one publicly released example of DriveWell Advance configured for a specific insurer program. It demonstrates how the shared product could be adapted through branded colors, program-specific language, navigation, scoring, and driver-value messaging.
Customer-branded work shown in this case study is limited to publicly released materials.
