Vehicle Tracking Dashboard
Redesigning fleet intelligence for the people who can't afford to lose track.
Watsoo Express
3 Months
March, 2026
UI UX Designer
Figma, Figjam, Illustrator, Phosphor Icons
problems
More screens. More confusion.
Zero breathing room.
The existing dashboard wasn't broken, it was buried. Here's what the real problems looked like up close.
01
Cluttered, breathless UI
Every piece of data was fighting for attention on a single screen.
No hierarchy, no negative space, no visual rest. Managers opened the dashboard and immediately felt overwhelmed.
02
No dedicated analytics module
All tracking happened on one main screen. There was no way to step back, see patterns, or understand fleet performance at a glance. Numbers existed. Insights didn't.
03
Digital lock was completely missing
There was no module to manage or monitor digital locking systems for vehicles. A critical operational need, entirely absent from the product.
04
Tracking history playback was barely functional
Replaying a vehicle's route history was technically possible but visually painful. Poor UX, confusing controls, no contextual information alongside the playback.
Context
A dashboard built for speed.
Not for the people using it.
A fleet tracking tool used by government and mining teams. They were losing time to their own dashboard. Watsoo had the data, it just couldn't show it clearly to the people who needed it most. I fixed that.
Design Principles
Calm over cluttered
Fleet managers are already operating in high-pressure environments. The dashboard should lower their cognitive load not add to it. White space is not wasted space.
Scannable before deep-dive
The most critical information is vehicle status, alerts, active trips and they should be visible at a glance. Everything else lives one deliberate click away.
Modular by design
Different fleet operators have different needs. The redesign needed to be flexible enough to serve a municipality and a coal mining operation without feeling like a compromise for either.
Confidence through clarity
Users who understand their data make better decisions. Every screen should leave the manager feeling informed, not confused.
research
Understanding the space
I didn't come into this knowing what geofencing felt like from the operations side. So before touching Figma, I did the work of understanding.
What I explored
How does GPS tracking and real-time telemetry works, so I could design for data I understood, not just data I was handed.
What geofencing means
Virtual boundaries that trigger alerts when a vehicle enters or exits a zone. For government fleet managers, this isn't a feature. It's an accountability infrastructure.
Why tracking history matters
Accident investigation, route optimization, driver accountability. Playback isn't just a nice-to-have feature. It's a compliance tool.
What fleet managers actually fear
Not bugs. Not slow load times. The fear is losing sight of a vehicle and not knowing why. Everything I designed had to address that underlying anxiety.
GROWING PAINS
One screen trying to do everything,
succeeding at nothing.
The product wasn't failing because the data was wrong. It was failing because the presentation was exhausting.
drag me..
Report filters were generic and non-configurable, managers
couldn't slice data the way their operations actually worked.
Alert notifications fired globally with no way to
configure by vehicle type, zone, or time.
No visual separation between live tracking and
historical data, everything blurred together.
Module navigation was flat with no clear hierarchy, every
section felt equally important, so nothing was.
Challenges in the
old dashboard
Operators had to scroll through dense tables to find a single vehicle's status. Alert logs were buried.
Reports required separate navigation entirely. And if you wanted to replay a route? Good luck.
THE OLD DASHBOARD — one screen, all data, zero hierarchy
INTRODUCING
The redesigned dashboard: everything
at a glance, understood in a second.
The product wasn't failing because the data was wrong. It was failing because the presentation was exhausting.
redesigned - LIVE TRACKING DASHBOARD
Added generous negative space and a strict visual hierarchy, placing vehicle status indicators at the top, map occupying centre stage, contextual vehicle info cards on the left.
Status is now scannable in under 3 seconds.
Introduced a clear sidebar navigation separating core modules:
1. Live Tracking
2. Analytics
3. Reports
4. Alerts
5. Digital Lock
6. Settings
Analytics Dashboard
NEW — DEDICATED ANALYTICS MODULE
Fleet managers now have a dedicated space to understand performance over time, not just track vehicles in real time.
Designed an Analytics Dashboard from scratch where introduced these necessary sections:
1. Distance covered
2. Fuel efficiency trends
3. Idle time
4. Dedicated Alerts section
5. Over & Under utilized vehicles
6. Driver Dashboard
NEW — TRIP REPORTS · STOP report · DAILY DISTANCE · summary report
Configurable Alerts
redesigned - alERT NOTIFICATION CONFIGURATION
The new playback experience shows the route on a clean map with a scrubber bar at the bottom — play, pause, skip forward, adjust speed.
Contextual data (speed at each point, stop events, geofence crossings) appears alongside the playback in a collapsible modal following the vehicle icon. What used to take minutes to understand now takes seconds to watch.
Reports now feel like business intelligence. Not afterthoughts.
Three new report types, built from scratch:
1. Daily Distance Report — total kilometres per vehicle per day, exportable.
2. Trip Report — start point, end point, duration, distance, and driver tag for every completed trip.
3. Stop Summary — every halt above 5 minutes, with location, time, and duration.
Intensive Reports
REDESIGNED — ROUTE PLAYBACK
Route playback
MEASURING SUCCESS
What changed after launch
We didn't have formal usability testing in place at the time of launch, something I'd do differently next time. But the signals we did get were clear.
40% reduction in support queries
Related to navigation and "where do I find X" in the first 6 weeks post-launch.
Three new enterprise clients onboarded
Within the quarter, the sales team attributed the cleaner demo experience as a key conversion factor.
Digital Lock module adopted immediately
By 80% of existing clients as an add-on, with zero onboarding friction reported.
Report generation usage up 3x
Compared to the previous quarter, managers were finally using the reports because they could finally understand them.
"It feels like a completely different product."
~ Internal feedback from a government fleet manager during a product review session.
LOOKING AHEAD
What's next?
The next release we were already planning.
Before I rolled off the project, the team was already scoping the next big module: Live Dashcam Integration. The idea: every vehicle in the fleet gets a connected dashcam. The admin dashboard receives a live feed, accessible per vehicle.
Why it matters?
1. Accident prevention — admins get instant alerts when the camera detects a sudden impact or harsh braking event.
2. Theft protection — if a vehicle moves outside its geofence after hours, the dashcam feed activates automatically.
3. Driver accountability — trip recordings are stored and attached to the relevant trip report, creating a complete operational log.
This isn't just a feature. It was the product evolving from a tracking tool into a full fleet safety platform.
Project Takeaways
Design for anxiety, not just usability
Fleet managers aren't casual users. They're responsible for assets and people. Every design decision needed to reduce the mental load of their job, not just make screens look cleaner. I learned to ask "what does the manager fear?" before "what does the manager need?"
Research fills the gaps your brief doesn't
Nobody in the brief told me to understand geofencing from an operations perspective. I did it anyway. That context changed how I framed every single module in the redesign. Details you discover yourself always hit different than details you're handed.
No testing, still a choice
Not having formal usability testing at launch meant we were flying on intuition and internal signals. It worked this time, but I walked away knowing that next time, I'd push harder to build even a lightweight test cycle into the timeline, even if it's done with just 5 users
Data without design is just noise
The old dashboard had the same data as the new one. Not a single number changed. What changed was how it was presented, and that alone changed how useful the product felt. That's the most honest argument for good design I've ever experienced firsthand.
Final notes?
This was a product with real users making real operational decisions — government employees, mining supervisors, municipal officers — people who don't have time to figure out an interface.
The redesign wasn't about making things pretty. It was about making people feel like they had control over the dashboard that mattered.
That's the kind of design problem I want to keep solving. 🫶
Thank you for reading!
It’s been a pleasure sharing the journey through my design process and final visuals!
fin!
✦ LET'S WORK TOGETHER ✦ LET'S WORK TOGETHER ✦ LET'S WORK TOGETHER ✦ LET'S WORK TOGETHER ✦ LET'S WORK TOGETHER ✦ LET'S WORK TOGETHER ✦ LET'S WORK TOGETHER
Designed & built by Sanjana Kumari in Framer ✦ 2026
Built with Love 🫶, Spotify on repeat, and four sleepless nights.
okay, your turn
I've shown you the work, the process, and probably overshared a little. Now it's your move.
