This document is structured based on a defined design approach.
Define > Research > Ideate > Test and Iterate > Implement > Monitor
Granular is a SaaS enterprise software company building farm management software for farmers. The product covers everything from operations, financials and inventory to reporting and analysis.
Operators and Ops managers are the main users of the mobile app. Operators are on the lower spectrum for adopting technology. The mobile application is the operators’ only tool in Granular. Ops managers are more tech-savvy and use both the Granular mobile and web application.
Both the operators and ops manager are out in the field driving the equipment, spraying, planting, harvesting, etc.
The Granular mobile app has two main high-level use cases:
Communication: As an ops manager, I need to tell my operator to go plant Field A.
Data Collection: As the CEO, I want the data collected in the mobile app to automatically sync to the web so that I can check on my financials, do analysis and run reports in real time.
The data recorded by the operator with the mobile app will upload to the web app where the CEO can check his financials, do analysis and create reports.
I created a spreadsheet to determine what to work on for the remainder of 2018. I collaborated with customer success and sales to quantify the impact every project would make. I created this list by sorting through customer requests and discussing with design and product.
Capturing accurate acres covered and hours worked is critical to several valuable insights farmers can use to improve their operations. These data points can uncover inefficiencies in operations that can be improved and help identify when more workers or equipment are needed.
Today, only about 25% of records are believable for both acres and hours. The current data quality is too low to draw conclusions on.
Outline Use Cases
I created a Google document to outline and document all of the use cases. This helped me have a better understanding of the needs for this project and ensure that the lead product manager, lead engineer and I were all on the same page. There are many edge cases to consider within this project and I considered all of them to ensure that what I handed off to engineering was well thought out.
I researched other mobile applications that were solving similar problems using GPS to track distance and time. I wanted to see if competitors had built something similar as well as gather a general understanding of how other apps resolve this problem and gain inspiration.
2 user flows explored when the app is in the foreground.
Hand Holding Within this flow, Granular pushes the Work Order to the operator once the operator enters the field.
You Got It The user is not pushed the Work Order which gives the user the freedom to pan to a Work Order when they see fit. This is considered a more “magical” flow for the user. I was worried that this flow may not be heavy handed enough.
User flow when the app is in the background.
The same notifications would be sent to the user if the app is in the background:
1. Pinging them that they have entered a field and the work order has been started
2. Pinging them once the user left the field to record actuals
If the user ignores the in-app notification for 2 or more Work Orders, the user enters a “Triage” experience once they re-enter the application.
Test and Iterate
I created a research proposal to review the two user flows, “Hand Holding” and “You Got it”, to help determine the correct direction for the project. I also dug into what the interviewee expected when the app is in background and showed some mock ups after hearing their thoughts. I interviewed five customer service representatives which is an internal group that works with our customers daily and have a lot of insights into their business and daily hurdles. I created an InVision prototype as a deliverable and conducted AB testing.
A secondary goal for research was to gather feedback on a revised Work Order detail screen which was not going to be fit in for the MVP of this project but would be in another iteration.
CSMs were concerned that users may miss their work if it is not directly pushed to them in the “You Got This” flow. Because the new flow is a more streamlined experience than the existing one, I felt confident that “Hand Holding” was the correct direction to move forward with. When I asked about the experience when the app is in the background, all interviewees described an experience similar to the triage one I explored. Once shown the mockup, they felt it was a strong direction and delightful experience.