Designing an Offline-First Map Experience to Help Field Workers Capture Critical Findings

Overview

Info

Company: Eskuad field data platform

Platform: Mobile and web

Team: Product manager, 4 developers, product designer

Result: MVP launched March 2025 with new features staged for quick improvements

Result: MVP launched March 2025 with new features staged for quick improvements

Result: MVP launched March 2025 with new features staged for quick improvements

My role

  • Executed the end-to-end UX and product design

  • Research and discovery with customers

  • Low-fidelity prototyping & testing with customers

  • Collaborated with the Development team on interaction design

  • Prioritization and definition of the feature’s MVP


Nolan Stewart

Nolan Stewart

Project Summary

In industries like forestry, environmental services, and remote operations, understanding the where behind data is just as critical as the data itself.


To meet this need, we launched Eskuad Maps: a web and mobile feature that allows teams to collect, review, and report geolocated field data—even when working completely offline.


This project opened new opportunities for Eskuad’s business growth and taught me valuable lessons about scope management, user collaboration, and designing for harsh, unpredictable environments.


Design Process summary

  1. Discovery research, conversations with customers

  2. Competitive analysis

  3. Flow diagrams, Lo-Fi design testing and validation

  4. Iteration, feature refinement

  5. MVP definition

  6. Hi fidelity design

  7. Launch and collaboration on releases

The Challenge

Our users— diverse users field admins/supervisors and technicians—needed a way to:

  • Capture exact locations of key findings such as protected areas, harvest sites, culvert positions, and vernal pools.

  • Report geolocated data to internal teams, external partners, and regulatory agencies.



But they worked in challenging environments:

Remote areas with little or no internet access

Harsh weather conditions and rugged terrain

The need for quick, easy-to-use tools while on the move

We needed a solution that felt effortless for the user, was resilient offline, and could grow with our product ecosystem.

Our users— diverse users field admins/supervisors and technicians—needed a way to:


  • Capture exact locations of key findings such as protected areas, harvest sites, culvert positions, and vernal pools.


  • Report geolocated data to internal teams, external partners, and regulatory agencies.



But they worked in challenging environments:


  • Remote areas with little or no internet access

  • Harsh weather conditions and rugged terrain

  • The need for quick, easy-to-use tools while on the move

We needed a solution that felt effortless for the user, was resilient offline, and could grow with our product ecosystem.

The Process

Discovery and early assumptions

Assumptions

When we began planning Eskuad V2 early in 2022 , we knew a map feature would be important.

  • Users want to be able to use a familiar map UI such as navigation apps like Google maps

  • Users want to mark datapoints using a map pin then entering data

  • Users want flexible data entry rather than a fixed form

Informal research

I Invited myself to sales meetings, client meetings with customer success, attended industry events, and conducted user interviews.


Key points from these sessions:

  • Users want to use fixed forms to collect data rather than flexible forms for consistent data entry

  • Many users are tech averse

  • Users are familiar with limited GIS tools

  • Users must concentrate on their tasks rather than focusing on a screen

  • Users are familiar with GIS tools

  • Users don’t want complicated tools, they want complicated reports - Simple data in & complex data out.

Our users needed a tool that captured location data effortlessly—without requiring them to stop, tap around, or break their flow. They worked outdoors, in tough conditions, and didn’t want complex tools—just reliable data capture that fit into their day.

I gathered and organized the information we had, and spent a few hours to make a quick and dirty prototype to gather some feedback from users and see if we were on the right track before continuing with design.




I gathered and organized the information we had, and spent a few hours to make a quick and dirty prototype to gather some feedback from users and see if we were on the right track before continuing with design.

Feedback from users

  • Easy to understand

  • Users don’t need multiple regions for maps uploaded

  • Users want a base map along with the

  • Tabbed map/ form view was easily used and understood


While early feedback confirmed we were on the right track, it also sparked a wave of new feature requests and deeper discussions

Scope creep and MVP definition

Scope creep

As we iterated with customers, the wish list grew:

Flexible pin placement, mini-forms, boundary/ polygon drawing tools, and more.


However, given our startup constraints, we had to reset and focus.

Working closely with engineering, customer success, and sales teams, I helped define a clear MVP centered on critical workflows, not “nice-to-haves.”


MVP definiton

We looked at all the parts of the feature that were most important and fastest to develop.

Included at launch

Set an offline area for the base map

Map view and form view for mobile

Map pin location for each field completed in a form

Completed form map view for web

What will need to wait


Flexible pin placement

Polygon drawing tools

Path tracking/ line drawing on a map

PDF map uploads

Multi form data reports with overlapping visual layers

Key UX decisions

Offline map setup

Early testing showed that we needed to mitigate map setup confusion. Users found the step by step setup process easiest to understand.

Simple data collection - no pin dropping

Because people need to keep their eyes on their work, we assigned every field a designated location, prioritizing safety and simplicity.

Fail-safe offline capability

Bu preloading only the defined map area and allowing base functionality without internet we reduced risks in the remote fieldwork environment.

Outcome

Launch March 2025

Early indicators

  • Improved field task accuracy (users now capture exact GPS data automatically)

  • Streamlined internal QA and auditing processes

  • Strong initial customer feedback validating offline usability

While formal adoption metrics are still being collected, the feature has positioned Eskuad for stronger supply chain integrations and sustainability reporting initiatives.


Reflection

Designing Eskuad Maps deepened my skills in balancing user needs, technical constraints, and business needs.


Takeaways

  • Scoping under startup pressure is challenging, weigh all requests from customers and spot trends for what is most important

  • Designing for offline capability means close collaboration with Development, and communication with users in onboarding and setup

  • Working on complex features in an agile environment means constant communication and early scope establishment.