Web, Desktop


8 months (2019)

I undertook this project while I was working for KeepTruckin. KeepTruckin builds fleet management products for North American Fleets.


KeepTruckin is building its own integrated speeding product in order to provide customers better driver monitoring and risk reduction capabilities. Most of our competitors offer a Speeding feature that enables the fleet manager to monitor if their vehicles are driving over the posted speed limit.

We aim to offer the same capacity to our customers, in order to solve their needs and fill in a gap in our product offering. The MVP release will  be a native product, inside the KT Dashboard, enabling us to lower costs of providing the feature and providing a better experience

Problem Statement

Fleet Managers don't know when, how long, and how often drivers are driving over the speed limit.

Design Journey

Trips based approach

When I started working on this project, the first approach which came to our mind is to show speeding on trip level. FM will still get the real time alerts but the all the speeding incidents will live within the trip along with other incidents like hard brake, hard acceleration & tailgating.

This approach will help the fleet manager how much does this driver speeds through out the trip. Its simpler to understand the driver context on trip level. Here are some of the explorations I did for trip based approach:

Explorations for trip based approach

Trips based approach - Cancelled

This approach later got cancelled due to following reasons:

1- Hardware Constraints
2- Real-Time Alert cannot be generated because system can only process speeding once the trip is finished.
3- On average a 5hr trip can generate more than 800+ breadcrumbs which is alot for system to process 4- can increase the chances of delays.
5- Can risks the MVP launch.

Incident based approach

After the cancellation of trip based approach we moved towards the incident based approach because we learnt that each incident has almost 7 breadcrumbs which makes it quicker and easier to process and trigger real time alert without any delays. This allows FM to see real-time incident and reach out to driver as soon as possible before the next incident happens.

Final design for beta release

Intensity Metric in Incidents

Now that incident based approach was released, a lot of FM’s wanted to see the intensity of an incident in real time. For example, FM wanted to know if the driver is speeding up or speeding down at any time. I explored several options and we shortlisted the following options for A/B Testing. The results received from that test helped us finalize the intensity metric by using Design B as base.

Design A

Design B

Design C

In the meantime, I was also working on upgrading our platform and we moved to ANT design Framework. To bring consistency we re-think the existing UI and merged all the updates in the next release:

Screenshot of the final MVP design after integrating beta release feedback

UI Explorations for Header & Details Panel

Here are the explorations I did for the header & speeding details panel which I was doing with the Design System team as the impact of these components were across the applications

Explorations for side bar

Integration of new header using ANT Design


1- Successfully delivered Speeding MVP being the most awaited feature of 2020.
2- Solved real world problem (Truck Accidents/Fatalities) which helped all of us, one way or the other.
3- Increased company ARR.
4- 8.5% Decrease in Fatal accidents in first 6 months.