Overview
Fleet management is the operations layer that sits above the delivery agent experience. While agents use the DA App in the field, operations managers need a web dashboard to see what's happening across their entire fleet — which agents are active, which orders are in trouble, where capacity is needed, and which DAs need attention.
I designed this dashboard from scratch, solo — covering everything from the navigation structure and live fleet map to agent attention alerts, heatmaps, order tracking, and fleet configuration.
The Problem
Ops teams were managing fleets without real-time visibility
Before this dashboard, operations teams were piecing together fleet status from multiple sources — spreadsheets, phone calls, and disparate internal tools. There was no single place to see the live state of a fleet, understand which agents needed intervention, or configure zones and assignments.
The result was reactive management: ops teams found out about problems after they'd already escalated, rather than being able to prevent them.
What I designed
A full-stack operations dashboard
🗺
Live fleet map
Real-time view of all active DAs and orders on a map
⚠️
DA attention alerts
Surfacing agents who need intervention — stuck, late, or flagged
🌡
Heatmaps
Demand and coverage heatmaps for zone planning
📋
Order detail views
Deep-dive on any order — status, agent, timeline
📢
DA announcements
Broadcast messages to agents in a specific zone or fleet
⚙️
Fleet configuration
Zone setup, capacity rules, and fleet parameters
📊
Dashboard overview
At-a-glance fleet health — active DAs, orders, and KPIs
🚚
Order tracking
Live order status and delivery timeline for any order
Process & Key Decisions
Designing for ops — speed and signal over aesthetics
Decision 01
Lead with attention — surface problems before ops teams go looking
The primary job of an ops manager is to find and fix problems. Rather than presenting a neutral view of the fleet, the dashboard leads with agents and situations that need attention — surfaced automatically, not buried in filters. The "DA need attention" view was designed as the default starting point, not a secondary tab.
Decision 02
Map and list as complementary views — not competing ones
Ops teams switch between spatial thinking (where is everyone?) and list-based thinking (who specifically needs attention?). The dashboard treats the live map and the agent list as two views of the same data, always in sync — selecting an agent on the map highlights them in the list, and vice versa.
Decision 03
Design announcement tooling for clarity, not just reach
Ops teams need to communicate quickly with specific groups of agents — not blast the whole fleet. The announcement tool was designed around targeting (by zone, status, or fleet) with a clear preview of who will receive the message before it's sent.
The Work
Key screens
📸 Dashboard / Live Fleet View — export from Figma Fleet Management file
Live Fleet Dashboard
Real-time fleet overview — active DAs on map, attention alerts, order status, and at-a-glance KPIs for ops managers.
📸 DA Need Attention — export from Figma Fleet Management file
DA Attention Alerts
Automatically surfaced agents needing intervention — with context on what's wrong and quick actions to resolve.
📸 Heatmap — export from Figma Fleet Management file
Demand & Coverage Heatmap
Zone-level demand visualisation to help ops teams plan DA placement and identify coverage gaps.
Impact & Outcomes
Shipped and in active use by noon Food ops teams
8+
Distinct surfaces designed — from live map to fleet config
✓
Shipped and used by noon Food operations teams across markets
↑
Add ops metric — e.g. response time to fleet issues, or DA attention resolution rate
↑
Add scale metric — e.g. number of ops managers using the dashboard daily