This work was created for Aegro, where, at that time, I was working as a Lead Product Designer. Aegro is a Brazilian SaaS company that focuses on developing digital solutions for farms.
Although I was the only Designer actively working on this project since its beginning, Júlia Rodrigues entered in the middle of the prototyping phase and collaborated to the process with user flows, icons, and user testing.
Challenge & Requirements:
> Aegro just launched a new crop scouting functionality on the mobile app. It aimed to help farmer's employees to perform crop scouting activities with more precision. However, Aegro's clients were experiencing many obstacles, and user satisfaction with this functionality was low.
> This new version needed to increase our user satisfaction (from the manager to the field worker), and, to do that, we needed to identify the main pain points involving this last release and the causes for the low rates.
Role & Responsibilities:
> Lead the discovery phase, perform field research and perform user testing;
> Frame the solution considering user needs and development constraints;
> Create user flows, wireframes, and high-fidelity prototypes.
First things first, what is crop scouting, and why is it important? Crop scouting is about managing the pest infestation in your crop, and, depending on the information gathered in the field, you apply a certain amount of pesticide to your plantation. Crop scouting is a sustainable way of controlling pests as it saves money by avoiding the unnecessary use of pesticides in the field and causes less damage to the environment.
Crop scouting is majorly performed by people. An individual or a group of people should walk in the field and gather information about critical pests that could be affecting the crop. That is precisely where the crop scouting on mobile has to act: helping these people collecting data in the field, even without the internet.
CROP SCOUTING (MOBILE) PROBLEM STATEMENT:
During a trip to Goiás (located in the Center-West region of Brazil), where we visited some farms to showcase the crop scouting initial solution, we could interact with our users in their work environment and ask questions about their daily routine and crop scouting. Besides that, we could perform some usability tests with them.
The usability tests used the interface below: Crop Scouting Mobile v1 created and released before I actively started working on the project. My job was to work on improvements to this interface.
Thanks to the field research and the opportunity to perform user interviews and user testing, we gathered valuable findings.
These findings were gathered, grouped by affinity, and prioritized. Below, I am showing some of the discoveries related to usability issues. Some insights were directly related to the engineering team, so I am not showing them here.
MAIN FINDINGS
In short, the scrollable tabs were confusing to our users, and the interface needed a redesign. Besides that, we needed to have in mind some constraints regarding the activity: the fact that our users only had one hand available.
Regarding the difficulties in identifying pests and diseases, besides adding more images to the list and a description, we thought about creating an image recognition AI (something that some competitors already have). As the AI idea had some significant technical challenges, we deprioritized it.
I started redesigning the crop scouting screens. After a few design iterations, I ended up with an interface that I thought would solve most of the problems. Besides the significant fixes on the navigation, it was added colors to show the pest or disease's severity level: from green (situation under control) to red (severe infestation). With these color schemes, it was possible to see what the data collected meant in real-time.
In Goiás, we only visited big farms, and most of them planted cotton that needs a very systematic way of crop scouting, our user sample was too narrow considering the user base who would use the feature. Thus besides the big cotton farmers, I decided to reach out to other clients with smaller properties, different crop types, and different regions to test the new interface presented above.
NEW FINDINGS
The tests' results were optimistic. The interviewees could easily interact with the interface, identify the new UI elements' meaning quickly, and interact with the expandable cards. However, we concluded that crop scouting is done differently from farm to farm, type of crop, and country's region. Some do it in a very complicated way and others in a much simpler way; it all depends on the size of their property, number of employees, crop type, location, humidity, and so it goes.
We needed to create something flexible and make it even simpler.
We decided to make the interface simpler: we took out all the sample types on the screen, and, for the first use, there is just one generic sample type. If someone needs to add more complexity levels, this person can adjust and create different sample types on the button located on the top right corner.
When you save your findings and go to the next point, it shows what you added for the first time, and you don't need to add again whatever you have added before. The manager can also plan the crop scouting activity on the desktop app: the manager can set what key pests should be evaluated and the sample types for a specific area.
It is hard to measure the impact of a redesign, principally when other improvements were also made: the app's performance, offline use, etc. Our user base that uses crop scouting got bigger (the sales team made a lot of upsells because of this feature), and the average time using the app for clients who have this feature is more prominent than the clients who don't.
Other Works
HelloSign Onboarding on Mobile AppsUI/UX, Product Design
Anotador 2.0UI/UX, Product Design
PGDay AmsterdamWebsite Design, Visual Design
Crop ScoutingUI/UX, Product Design
PlutocracyUI/UX, Social Design
Weather DataUI/UX, Product Design