Dónal O'Mahony
Context

I joined Fleetmatics, now Verizon Connect, as Senior Director of UX Design, Content and User Research. It was a telematics fleet-tracking business. During my time there, it became an easy-to-use, modern AI and IoT company. This case study covers one product line central to that change: a video safety product that first had to earn customer trust.

The evolution of Verizon's AI dashcamfrom a hackathon entry to a life-saving system drivers trust

DÓNAL O'MAHONY · SENIOR DIRECTOR OF UX DESIGN, CONTENT & USER RESEARCH, FLEETMATICS / VERIZON CONNECT 2016-2022 · THIS INITIATIVE 2020 TO 2022

A 2020 hackathon idea became a video safety product. Research and a major redesign established customer trust. In 2022, we launched a driver-facing AI dashcam that saved a life in its first week.

Verizon Connect dual-facing AI dashcam hardware with live road detection, cab view and map replay
Six years00

Before and after

The two screens below show the change in the product during my time as Head of the global UX Design, Content and User Research team.

Before

Legacy telematics tracking

Fleetmatics live map from 2014 with a dense vehicle list, blue chrome and a cluttered map interface

After

Modern AI and IoT product

Verizon Connect Reveal AI video event page with road view, speed graph, trip details and plain-language analysis
01

Computer vision - The AI spark

The idea came from a hackathon, not a roadmap review. I developed the core concept with Alessandro Lori, then Head of AI and now CTO of Verizon Connect. I judged and sponsored the team before and after the event while the work was still a concept.

Driver-facing detection classifying phone distraction from presence of a phone in scene and phone handling
Phone distraction, defined precisely enough to be defensible: handling a device for at least two seconds.
Road-facing detection estimating headway and distance to the vehicle ahead to classify tailgating
TAILGATING, CLASSIFIED FROM HEADWAY, DURATION, SPEED AND DISTANCE THRESHOLDS RATHER THAN A GUESS AFTER THE FACT READING A REPORT.
Method02

The decision

A few weeks after the hackathon, we assessed the idea using the Dan Olsen Lean Product Playbook: identify the customer and need, define why we should solve it, prototype the product, validate it with customers, test the business case, then decide whether to proceed.

We framed the opportunity through the Kano model: reliable video evidence and an explainable safety score as the must-haves, speed and classification accuracy as the performance needs, and proactive alerts that stopped risky behaviour before it became an incident as the delighter worth chasing.

The customer need was concrete. Fleet managers were facing steadily rising insurance costs, needed evidence of liability when incidents happened, and were struggling with unsafe driving they had no reliable way to catch. What they had access to at the time, simple 3rd party dash cameras, separate map replay and generic safety-score reports, was meeting that need poorly or not at all. We set out to unify that experience. The opportunity was a multi-hundred-million-dollar market with a clear revenue target. It justified a significant multi-year investment. The hackathon idea became a funded roadmap item.

The Kano model chart showing must-have needs, performance needs and delighters across absence to fulfilment
Framing the opportunity through Kano: must-haves, performance needs and delighters.
03

What shipped first

The Integrated Dashcam MVP launched with a video browser, map replay, a mobile app and alerts. It worked, but customers did not yet trust it.

Reveal video event page showing road view, cab view, map location, playback controls and event details
Launch day, 2020: a single event with road view, cab view, map replay and the details behind it.
Reveal video list showing events by vehicle with triggers, classification badges, drivers and locations
The video list: every triggered event, with its classification, for a whole fleet.
The turn04

The trust problem

Behind the scenes, computer vision and AI models were auto-categorising thousands of hours of footage for fleet managers: collisions, phone use, tailgating, hard driving and more.

Users could rate the accuracy of those categories directly in the product, so we had a constant feedback loop. The feedback revealed a deeper problem: trust in the categories themselves was low. A classification that managers second-guessed was not saving them time; it was creating more work.

45 survey responses · 10 interviews

82% were satisfied overall. Only 6 out of 10 trusted the system to classify what it was showing them.

Customers who did not fully trust the classification started watching videos they did not need to, just in case. Eight in ten said they normally skipped reviewing minor events, and the two in ten who did found it time-consuming, precisely because they did not trust the system to have called it right the first time.

82%

satisfied with the product overall

6 / 10

trusted the event classification

8 / 10

avoided reviewing minor events

Survey results showing 82% satisfaction alongside a verbatim complaint about video classification accuracy
The headline number, and the comment underneath it: satisfied overall, unsatisfied with what the system called an event.
Trust study results showing 6 out of 10 participants trust the video system to accurately trigger and classify videos
Six out of ten trusted the classification. That was the number the redesign had to move.
Usertesting trustworthiness result showing 4.41 out of 5 average across 56 tests
A later trustworthiness study across 56 usertesting tests averaged 4.41 out of 5.
05

The fix

We rebuilt the alert language and severity scale from scratch. The original set, collision, dangerous, hard driving, low risk, had been arrived at by committee, and it showed. We tested three different ways of describing what happened in a video with 30 fleet managers on usertesting.com plus 7 internal sales and marketing reviewers: a paragraph description, and two different bulleted formats.

Reveal analysis panel explaining a collision classification with hard braking trigger, average and max speed and maximum G force
What shipped: plain language, plus the specific reasons the system called it a collision.

The result was decisive. The clear bulleted version reached 89% preference on accuracy and 92% on readability, against single digits for the paragraph version. We shipped the simple, bulleted language with explicit context on why an event was classified the way it was, and added a speed graph pulled from our own telematics data so a customer could see the full context of an event rather than take the system's word for it. Trust improved, and customers spent less time checking minor videos.

Analysis description redesign test comparing a paragraph description against two bulleted formats, with accuracy and readability scores
Three descriptions of the same event, tested with 30 fleet managers. The bulleted version took 89% on accuracy and 92% on readability.

The ease of use, the graph to visually see what's happening... just wonderful. Not to mention all the times the camera has saved our business.

Ernesto, fleet manager
Research outcome showing improved trust and system accuracy: in-product accuracy feedback and a trend graph of positive ratings by classification
Outcome: user feedback trained the video analytics engine, and positive ratings rose across every classification.
06

The leap

In August 2022, that trust became the foundation for a driver-facing AI dashcam with real-time early warning and in-cab coaching, built with our Data Science and ML teams. The alerts had to be instantaneous and understandable, so we designed distinct audio and voice cues for each type of risk. Matt O'Sullivan, Lead UX Designer, led this work: defining when a tone, a spoken word, or a combination of both was the right call, and how loud, how long, and how urgent each cue should feel to a driver already focused on the road.

Audio UX research slides comparing verbal and non-verbal warnings and design principles for reaction time
Audio UX research for driver-facing alerts: verbal vs non-verbal warnings and the design variables that govern reaction time. Lead UX Designer: Matt O'Sullivan.

This introduced audio UX and its associated user testing to the design team. A warning a driver cannot understand immediately is worse than no warning.

In its first week, the product achieved the outcome behind the trust work. A customer contacted us after the system detected her drowsiness, slow blinks and dropping head. It alerted her before an incident occurred.

07

The North Star

From 2023, while shipping the driver-facing dashcam, I worked with Product and Engineering leadership to define Reveal AI, a provocative North Star vision built to stretch thinking and guide debate, not a committed roadmap. It used a recurring cast, a safety manager, a dispatcher, a fleet manager, living through one continuous day, rather than a feature list, and it shaped how our research team thought about immediate versus long-range questions: Cheryl Abellanoza, PhD, our UX Research Manager at the time, wrote her own account of what that meant for a research practice, and credits the discipline on our team to this period of leadership.

Trailer sideswipe scenario with a side collision warning and multi-camera footage of the incident
Accident reconstruction view with a map, a side collision report and speed analysis on mobile
Dispatcher view suggesting reschedule options for a delayed driver's upcoming jobs
5G smart city live footage view of a highway crash with vehicle and cargo telemetry
Reveal AI, a 2023 North Star vision built with Product and Engineering to stretch thinking, not a committed roadmap.
08

Where it stands today

The company I joined as a telematics tracking business has moved well beyond that description. This product line contributed to that change. Verizon Connect's current AI dashcam line now runs dual-facing cameras, real-time driver monitoring for phone use, smoking and fatigue, tailgating and pedestrian-proximity alerts, and up to four peripheral cameras for full 360 degree coverage. This is a significant advance from the video browser and map replay in the 2020 MVP.

60%

fewer unfastened-seatbelt incidents

60%

less mobile phone use while driving

50%

fewer tailgating and fatigue incidents

The results are now published. B.A.M. Trucking reports saving $200,000 on insurance premiums. Other customers, Nextier Infrastructure Solutions, Lincoln Hill Retirement Community and Cristo Rey Jesuit High School, describe the same outcome Ernesto described years earlier: the video was available when it mattered. It helped defend against false liability claims and supported direct conversations with drivers about incidents. The product has since received industry recognition, including Gold Globee and Stevie awards.

I was there through the driver-facing AI dashcam launch and the start of the peripheral camera work that would become the 360 degree coverage. After that I moved on to Contentful and then Canto, before the full peripheral system and the awards that followed shipped. The central point remains: the system had to earn trust before it could develop further. The work in 2020 and 2021 gave the video-intelligence product the foundation it needed to become a second pillar of the business rather than an addition to GPS tracking.

09

Launch video

10

Co-Credits Design & Research

Matthew O'Sullivan
Design Manager. Carried the AI Dashcam design work day to day.
Lorenzo Moschi
Lead Designer on the dashcam experience across its redesign and driver-facing release.
Rachel Ryan
Lead Researcher. Ran the trust study and the alert-language testing the redesign was built on.
Alessandro Lori
Head of AI at the time, now CTO of Verizon Connect. Collaborator on the original concept.

Individual squad designers joined the work as needed throughout the product's life. There were too many to name individually, and their contribution was essential.