Designing for work beyond the connection
FIELD OPERATIONSDesigning an offline-first field tool for drivers performing critical jobs in environments where connectivity can’t be guaranteed.
Designing for work beyond the connection
FIELD OPERATIONSDesigning an offline-first field tool for drivers performing critical jobs in environments where connectivity can’t be guaranteed.
My role
Product discovery · UX/UI · Prototyping · Validation
Users
Drivers emptying wastewater tanks in the field.
Context
On the road and on site, often with limited connectivity.
Product
Mobile app for iOS and Android.
Time
Discovery → MVP
2025–2026
The challenge
An outdated field tool no longer fit for the job
The existing solution was built around an aging and increasingly unstable PC-based application with a limited remaining lifespan. Because the software was fixed inside the vehicle, drivers had to adapt their work around the system rather than having the tool available where the work actually happened.
This created particular challenges when documenting tank emptying in the field. Photo documentation was cumbersome, registrations could be unreliable, and connectivity could not always be guaranteed.
With the existing solution approaching end-of-life, the challenge was not simply to replace it.
We needed to rethink the core field workflow and define a focused MVP that could make everyday work simpler, documentation more reliable and the product ready for the future.
- An aging, unstable platform
- A tool tied to the vehicle
- Cumbersome documentation
- Unreliable field registration
Key insight
The work happens outside the vehicle
The existing solution assumed that the digital part of the job happened inside the vehicle. But the most important moments — locating the tank, performing the emptying and documenting the work — happen outside, at the point of service.
This shifted our perspective. Instead of rebuilding the existing PC application on a new platform, we focused the MVP around the driver’s actual field workflow.
The tool needed to move with the driver — not make the driver return to the tool.
Documentation should happen in the moment
Photos and job information are most reliable when captured directly where the work is performed.
Connectivity cannot define the workflow
Drivers need to keep working when the network is weak or unavailable.
The MVP should focus on the field
We prioritised the essential tasks drivers need before, during and after an emptying — rather than recreating the entire legacy system.
The solution
A simple, reliable app — built for the field
The solution brings the driver’s essential workflow into one simple mobile experience — from finding and navigating to the next job to completing and documenting the work on site.
Designed with an offline-first approach, critical information remains available when connectivity is limited and synchronises when the connection is restored. The experience focuses on the tasks drivers need in the field — reducing complexity and supporting a faster, more reliable workflow.
Offline-first
Works even when connectivity is limited.
Clear job overview
Makes upcoming work easy to find and understand.
Map-based navigation
Helps drivers locate nearby jobs in the field.
Guided job flow
Keeps the essential steps simple and focused.
Automatic sync
Updates data when the connection is restored.
Impact
~50%
Faster job executionin
(Base on usability testing)
Reduced
Manual steps and potential errors
Positive
User feedback during validation
THE OUTCOME
Designed to keep the work moving
— even when connectivity doesn’t.
Key takeaways
Context before interface
Understanding where the work happens helped us design around the driver — not the existing system.
Prioritise the workflow, not the legacy system
Focusing on essential field tasks helped us create a simpler, more focused MVP.
Design reliability into the experience
Offline access and reliable documentation weren’t technical details — they were core UX requirements.