ArcGIS Field Maps

Product design

The team's challenge

When setting out to create ArcGIS Field Maps, there were a number of challenges that we wanted to take head-on to solve:

  • Simplifying offline map preparation: Users found it difficult to access scattered settings for offline map preparation. Our goal was to centralize these settings into one user-friendly location.
  • Handling complex data collection: Existing workflows were inadequate for users' intricate data collection needs. We introduced new patterns and capabilities to accommodate diverse data requirements.
  • Consolidating multiple applications: Users struggled with fragmented workflows due to reliance on multiple apps. We aimed to integrate functionalities into a single, cohesive ArcGIS Field Maps app for a smoother transition.
  • Streamlining backend complexity: The complex backend architecture could overwhelm users. Our focus was on creating intuitive interfaces and workflows that shield users from technical intricacies, ensuring a seamless experience.

By addressing these challenges, we aimed to rethink and enhance the user experience of creating and managing maps for field data collection.

My role

As the lead designer, I played a pivotal role in ensuring the success of the ArcGIS Field Maps web application. My responsibilities included:

  • Owning the user experience: I ensured that the overall user experience aligned with requirements and design standards by conducting research and incorporating user feedback.
  • Collaborating with cross-functional teams: Leveraging my GIS application experience, I collaborated with various teams to develop cohesive user experiences across products.
  • Understanding complex data models and customer use cases: I delved into intricate GIS data to design an intuitive user interface, meeting customer needs effectively.
  • Working closely with the Product Manager: I collaborated with the Product Manager to understand users and shape the application's vision.

My diverse skill set demonstrated my expertise as a lead designer, enabling me to navigate complex projects while prioritizing a seamless user experience.

Evolution of the design work

Design sprint

In the early stage, I led the team through a design sprint using the Google Venture methodology—a four-day, in-person event. This process:

  • Defined long-term goals: Establishing a clear goal for the ArcGIS Field Maps web app, guiding subsequent design and development efforts.
  • Identified key user types and workflows: Understanding user needs, setting the foundation for design decisions.
  • Fostered collaboration and shared understanding: Team cohesion, effective communication, and cohesive design thinking.
  • Generated valuable artifacts: Produced insightful artifacts for reference throughout design and development.

The design sprint laid a strong foundation, driving focus, collaboration, and alignment for the project's success.

Concepts and sketches

During the early concept stage, as the lead designer, I collaborated closely with the other product designer to generate a multitude of sketches, addressing various workflows to alleviate user frustrations. We iterated extensively to refine ideas.

We held daily meetings with the product team and weekly meetings with the wider team to ensure alignment and gather feedback. After several weeks of collaboration and iteration, we arrived at a series of sketches that represented a shared understanding among the team, serving as a basis for scoping upcoming work.

User interviews

In 2019, we engaged customer teams at our annual User Conference, seeking their input on our sketches. The feedback was overwhelmingly positive, validating our design direction. However, we discovered that offline map preparation was challenging for users, leading us to prioritize this pain point.

We transitioned to asynchronous user research, collaborating with a customer experience analyst. Surveys and communication channels provided valuable insights into user needs and behaviors, informing a more user-centered design for ArcGIS Field Maps web.

Bumps in the road

During ArcGIS Field Maps web development, we faced two key setbacks in user experience and interface structure. We successfully addressed these challenges through innovative solutions and collaboration.

  1. "Form First" vs. "Template First" Approach: Initially, we prioritized form creation, but the data model followed a "template first" approach. To reconcile, we treated templates as preliminary work, simplifying form building and maintaining a form-centric experience.
  2. Interface Structure and Map Viewer Collaboration: We encountered interface issues due to Map Viewer redesign. Working closely with their team, we integrated their design patterns and built reusable components for a cohesive experience.

By overcoming these challenges, we achieved a seamless and user-focused design for ArcGIS Field Maps web, ensuring compatibility within the ArcGIS ecosystem.

Product tour

ArcGIS Field Maps is an all-in-one app that uses data-driven maps and mobile forms to help workers perform data capture and editing, find assets and information, and report their real-time locations. ArcGIS Field Maps is the go-to field app that streamlines the critical workflows mobile personnel use every day. Because it is built on ArcGIS, everyone—whether in the field or the office—will benefit from using the same data.

Introduction to Smart Forms

Product screens