Vehicle Management
Problem
There was no interface for admin and users to manage their own fleet vehicles, currently it was done through an initial upload by the engineering team. They needed a way to upload vehicles to their fleet, configure their connected devices, and make edits.
The Whelen hardware also collects a variety of data from the vehicles they are connected to, but was the app's interface only surfaces a small amount of that information. The desire was to expose as much of that data as possible, as long as it was relevant or actionable to the user and not overwhelming.
Research & Wire Frames
Because fleet configuration had previously been handled directly by engineering, there was limited visibility into how customers actually expected to manage their vehicles and connected devices. To better understand the problem space, I worked with internal stakeholders across product, engineering, and support teams who regularly interacted with customers.
These conversations helped identify the most common operational tasks customers needed to perform, such as uploading vehicles, configuring connected hardware, and updating fleet information over time. They also highlighted friction caused by the existing workflow, where even small changes required engineering involvement.
In parallel, I explored how other fleet and asset management platforms approached vehicle configuration and telemetry data. This helped inform early wireframe explorations focused on balancing visibility of vehicle data with usability, ensuring the interface surfaced meaningful information without overwhelming users.
Early wireframes were used to validate assumptions with stakeholders and refine which vehicle data points were most relevant and actionable for users managing their fleets.
Solution
Based on insights from stakeholder discussions and early wireframe exploration, we designed a fleet management UI that allowed admins and users to add, configure, and manage vehicles without relying on engineering.
A detailed vehicle view surfaced the most relevant data collected by Whelen hardware, including trip history, location, and device details. Information was organized to make key operational data easy to scan while avoiding overwhelming users with the unnecessary.
The vehicle creation workflow was designed for real-world use, where users may be physically near the vehicle when adding it to the system. To streamline this process, users could scan identifiers such as the VIN, license plate, or connected devices, reducing manual entry and speeding up fleet onboarding.
These changes gave customers direct control over their fleets while making vehicle data more accessible and actionable within the app.