Onfleet - On-Demand Economy's Best Kept $400m Secret

Onfleet - On-Demand Economy's Best Kept $400m Secret

Onfleet launched in 2015 and led the rise of on-demand delivery services from ground zero – SoMa in San Francisco. At the heart of these services lies a significant challenge: managing and optimizing the complexity of last-mile delivery. Onfleet started out as a tiny team of 5 and is currently a leader in this space valued at $400M boasting over a 100 employees worldwide.

Onfleet launched in 2015 and led the rise of on-demand delivery services from ground zero – SoMa in San Francisco. At the heart of these services lies a significant challenge: managing and optimizing the complexity of last-mile delivery. Onfleet started out as a tiny team of 5 and is currently a leader in this space valued at $400M boasting over a 100 employees worldwide.

Impact

May 15, 2024

Valued at $400M

Valued at $400M

Services

May 15, 2024

Product Design

Product Design

Client

May 15, 2024

Onfleet

Onfleet

Year

May 15, 2024

2018

2018

I led design at Onfleet between 2015 and 2018. Although Onfleet started out as a web-based heavy enterprise solution, mobile experiences have been crucial for Onfleet's success over the last decade.

Onfleet has three main personas: Dispatcher, Driver and Recipient. When I joined the team, Driver was probably the most underserved persona of the three. Early user interviews conducted suggested the product was mostly loved by Dispatchers and Recipients, however Drivers, accustomed to pen & paper deliveries, felt they were forced to use the Onfleet, felt they were tracked and spied on.

On top of it, most Drivers used older smartphones, making the experience of using Onfleet mobile app supbar due to high battery consumption, crashes, etc.

The frustration with the mobile app resulted in Onfleet's low rating on Play Store and App Store that hurt our efforts to acquire more customers.

In order to provide drivers with a reason to love using Onfleet app, we've connected it to their primary motivation – earning a living. So was created Onfleet Driver Analytics.

The idea was to empower Onfleet users by giving them a better understanding of where their hours went and how meaningful their work is, in terms of hours spent and dollars earned. As with many analytics features, the big question is what do users need to see. I conducted a series of user interviews among Drivers. The goal was to understand what stats were most important for the persona.

The results suggested "Earnings", "Completed deliveries" and "Distance" were most important. Average performance stats (time per delivery, delay time, service time) were not as important to the drivers, gathering around 5% each, but were mentioned nevertheless.

Interestingly enough average delivery rating or feedback was not important to the drivers, only at 3%, suggesting their businesses' compensation model did not account for customer satisfaction.

61% of drivers I talked to said they tracked their work hours daily, while 19% said they weren't tracking hours at all or weren't paid by the hour, which was an unexpectedly high number, suggesting they were paid by the number of deliveries completed.

Six weeks after release, we conducted a survey asking Drivers about their experience using the Analytics feature.

Most users used analytics to track their hours and, as expected, suggested introducing some way of tracking how much they've earned. Some drivers felt the hours on-duty stat was off, which was the result of them not going "on-duty" at the beggining of the day - one of the incorrect app behaviour we wanted to fix. Seeing their hours as "inaccurate", the drivers began to use the app as intended and clock in and out correctly.