Region Reports & Scouting Notes in FieldView

What is Climate FieldView?

FieldView is a software platform for farmers that brings together all the data from your farm operation and fields.

From choosing seed type, applying fertilizer, and harvesting at precise timeframes, a farmer has very little margin of error. FieldView helps maximize crop output by optimizing every part of the season.

Project Overview

Allow customers to draw region shapes over map layers and write notes regarding possible issues in that region of the field. These regions need to be accessible after harvest so the customers can analyze their crop yield.


I was the user experience/designer on this project. I worked with a product manager, the director of product and several engineers.

The Problem

Throughout the season, Farmers and agronomists use FieldView to monitor the health of their fields. FieldView generates field health images from satellite imagery. Red areas signify potential problem areas such as pests, disease or flooding. Farmers or agronomists may decide to go into the field to scout it out.

FieldView allowed users to take basic notes by dropping pins on the map but problems are not always confined to single points.

Users need the ability to take notes of entire regions and save the shape bounds so they can view yield reports for that region after harvest.

Example of a generated field health image within FieldView


By having interviews with farmers I was able to get a good sense of what their struggles are and the journey they go through.

One thing that really stood out to me was that the farmer and their agronomist regularly reviewed the health of their fields using FieldView, but they would print off maps of their fields. Using the printouts, they circled areas of concern and took notes in their binders. This is time consuming and can be unorganized.

After harvest, the farmer agronomist and seed dealer need to see how those problem areas affected the crop output. Because the shapes were drawn on paper, there was no easy way to analyze yield performance in those regions using FieldView.

The customer’s journey based on my conversations

Sketching & Wireframing

After my interviews with our users, my Product manager and I started brainstorming and whiteboarding ideas to identify use cases, start visualizing the path our users would be taking and identifying the features and functionality needed to accomplish their tasks. Ideas were added and cut through the process as we narrowed down the goals. After getting to a good spot, I began sketching and wireframing initial flows while frequently meeting with my PM to review.

By getting initial thoughts onto paper quickly I could concept with different patterns and layouts. By quickly iterating I was able to narrow the concepts down to something that would work well for our users. Flow diagrams were created to ensure the user wouldn’t end up in dead ends. I was able to receive feedback throughout my concepting phase during our weekly design critiques.

Some initial exploration sketches
Exploring drawing tool variations


After the exploration stage, I began designing the screens and created clickable prototypes with Invision. Clickable prototypes give me perspective and usually surface any flaws that may not have been obvious with static wireframes. After iterating with my PM on the prototype, I presented it to our director of product to get feedback and buy in for the feature experience.

One of my early prototypes


My next step was to get feedback from our customers. We scheduled video calls with some of our farmers, agronomists and seed dealers and gave them tasks to complete within the prototype. Overall users were excited about this feature and expressed how valuable it would be to their workflow.

The Designs

Drawing tools

Users can select a drawing tool on the map and outline the portion of their field they want to analyze, annotate or save for later. The tools include drawing freehand, creating polygons, rectangles and circles for irrigation. A blue bar at the bottom was used to give the user real-time instructions to complete the drawing task.

Examples of regions drawn to outline problem areas, compare yield of seed types, and analyze irrigation

Region Report

After drawing a shape over the map, a user can view detailed harvest information about that specific region of the field. This allows them to see how things like seed type, soil, and density of seed placement affect the crop yield. From here users can create a note attached to the report as well as save the region for later analysis.

Region Report with note attached

Scouting Notes

From the region report, a user can tap into the notes area at the top to document information about their region. They can add multiple photos, enter descriptions, categorize the note and more. Scouting notes help farm managers and agronomists stay in sync about the status of their field and to know what problems need their attention.

Scouting Notes on iPhone
Scouting Notes: Entering Category Data Flow

Saved Regions

After a region has been saved, it gets added to a list where users can run post-harvest reports. This allows them to follow up on problem areas identified earlier in the season.

Viewing your saved regions


During implementation phase I worked closely with the engineers and created specs, flow diagrams, cut assets, reviewed UI builds and helped test.


This project was received well by our users and helped improve their workflow. I plan to continue improving this feature by giving the drawing tools more functionality and precision.