Project Context
The client needed a modern IoT platform for municipal and environmental maintenance fleets. Operators required a web portal to manage vehicles, work orders and routes, while drivers needed a focused mobile app for executing tours in the field.
My role
Lead Product Designer
Team
Product Owner, Frontend, Backend, QA
Scope
Web tool + Android app, based on IoT platform
Key Challenge
Create a unified platform for planning, monitoring, and executing fleet operations with synchronized statuses across web and mobile
Problem
Fleet operations involve many vehicles, destinations, routes and task states. The tool had to connect two very different user groups: operators and drivers, while supporting complex business logic, vehicle tracking, and real-time status updates.
Two users, one complex workflow
Keep order and tour statuses consistent across web, mobile, IoT data and backend services.
Operators
Plan work, assign vehicles, build tours and monitor execution across the fleet.
Drivers
Work outdoors and on the move, with limited time and attention for each interaction.
Discovery
Competitive analysis
I reviewed products such as Samsara Fleet, Verizon Connect Reveal, and ServiceMax to identify familiar interaction patterns for vehicles management and field operations.
Outcome
✓ Map-first monitoring and real-time fleet visibility.
✓ Structured planning and dispatch workflows.
✓ Focused mobile experience for field workers.
Stakeholders interview
To validate requirements and answer open questions, I ran several sessions of stakeholder interviews. Senior client representatives gave me understanding of the daily work of operators and drivers. Bases on that interviews I've got some insights that helped me to work on the design.
Operator's tool
How is work assigned to drivers?
Operator submit work requests from different clients that become Orders. Then they assign vehicles and executors and create Tours.
Introduced separate Order and Tour entities to support planning and execution independently.
What are destinations?
An address alone isn't enough. Often it can be a park or street
We need 3 types of destinations: address, street, zone.
How are tours created?
Operators sometimes need full control over planning, while routine work should be generated automatically and often multiple tours at a time.
Manual planning with automatic bulk tour generation
Driver's app
What do drivers need to complete their work?
Drivers only need the information required for the tour: destinations, navigation, task status, and a way to report issues.
Simplify interface for drivers, highlighting only currently important actions
How drivers can report an issue
For some cases it's just a comment, and for some cases it's photo proof.
Add possibility to add a media to a tour
Do drivers need both orders and tours?
Drivers complete work through tours, but each order contains its own required form. To report completed work correctly, they need access to both.
Organized the mobile experience around tours, with access to individual orders when needed.
Both interfaces
What information needs to stay synchronized?
Tours and orders statuses. Both, operators and drivers should see same up to time data
Build statuses logic, considering all edge cases
