winter 2022 - 2023
There had previously been a map-based tool in SI called Geospatial Analysis, which had been deprecated prior to me joining the team. However, clients clearly craved and made requests to our customer success team for a more visual way to explore their data. And, as time went on, the quantity and types of data Regrow had available continued to grow. With Regrow’s clients being some of the largest food and agriculture businesses in the world (ex. Cargill, General Mills), users were interested in analyzing and making management decisions for potentially millions of acres of crops at a time.
A new mapping tool would need to be able to show insights for 12 possible key performance indications (KPI’s) that each fell into one of two categories: agricultural practices and outcomes. Clients needed to be able to draw insights from combinations of these KPI’s in order to understand the effects of transitioning to more sustainable land management.
Also crucial to this process would be designing a visualization that could expand and accommodate new data sets as Regrow expanded outside of the world of carbon into other realms of sustainability, such as water and yield.
A map is an immensely complex tool; entire companies exist for the exclusive purpose of mapping! For the sake of keeping a neat scope for this project, I worked closely with product to create boundaries and aim to achieving the following goals:
For the design of the map portion, I referenced other mapping tools created by government agencies or that used publicly-available climate and agriculture data sets for inspiration. Initially, I explored using a combination of choropleth coloring and symbols to represent different KPI’sI. For example: cover crop adoption could be represented by coloring on gradient scale, and water risk rates could be overlaid on top of those counties as proportionally-sized circles in those respective colors. However, upon a second round of internal user feedback, it seemed this was still quite visually intense.
To simplify this, I adopted a bivariate choropleth color scheme. In this model, agricultural practice KPI's are represented by one color gradient (yellow), and outcome KPI's are represented by another (blue). The two are combined the create a third color (green) where there is overlap. With this scale, I needed to prioritize accessibility. The color scale would need to have enough visually-distinct colors that someone could pick apart different regions easily, with enough contrast, and with clear boundaries. The coloring also could not conflict with any additional layers. Through a series of explorations, I landed on the final designs shown here:
Another key change for this final iteration of the visual design was to simplify the side panel. I reduced some of the color blocking in favor of more subtle uses of color, and pared down the statistics being shown to the most crucial pieces of information. In order to add context on whether results were "good" or "bad," I added small tags to each summary statistic, indicating whether each value was relatively low or high.
With the more aggregate-level view simplified to only the most crucial pieces of information, users still needed a way to view individual areas (in this example, counties) in greater detail. If the user clicks on an area in the side panel or on the map, or, if they manually zoom in on the map, they are able to see a more detailed view.
In this view, the user can see landscape features, such as city name and waterways, at a more granular level. In the side panel, they are able to see the specific number of farms, total land area, and crop types for that geography. They are also able to their selected KPI metrics broken down by those additional dimensions, as well as volume for each crop on that piece of land.
With these designs, I conducted a second round of internal interviews to validate the designs further. Overall, the qualitative results were resoundingly positive, with customer success managers eager to share the designs with their clients. Having entered into the project with a very specific scope in mind, we as a product team began to brainstorm the next features to explore, including:
• Allowing users to add custom points, shapes, and boundaries
• Adding the ability to take and share snapshots of the map
• Adding more public data sets for things like livestock and yield resilience
However, at this point in time I left Regrow as the first version of the map was at just the beginning of its development and unfortunately did not get to oversee the final implementation. Over the course of this project I was certainly challenged; I was new to designing for map-making, which is both an art and a science. In particular, I enjoyed the technicality of this design and the finesse of having to create simple and reusable patterns out of the chaos of data and geoscience!