MMehak Maini Mynzo Partner App

Case study · Mobile app

Field data,
made easy to collect

I designed the Mynzo Partner App, the mobile app our field partners use to collect plantation and survey data. Rebuilt around field research, it took two people to 400 data points in two days, up from 25 to 30 a day.

My role
Product designerField research to final screens
Platform
Mobile appUsed on site, in the field
Users
Field data collectorsAnd farmer documentation
Early result
400 data points in 2 daysBy two people, up from 25 to 30 a day
The Partner App home screen: five jobs as tabs, and the projects listThe Biodiversity home: boundaries on a map and a list to choose from
My role

Product designer

I designed the app around the people who use it in the field. I went to their environment to see how data is really collected, worked out the data the business needs and the parameters it is judged on, and turned that research into solutions.

Mehak with the field team inside a forest boundary
In the field with the team, testing Version 1
My approach

Five steps

The sections below follow these steps. Version 1 itself came first, built before any of this research.

  1. Step 1

    Understand the users

    How they work today, and the environment they work in.

    Contextual inquiry · Current journey · Problems

    Jump to section →
  2. Step 2

    Strategize

    The jobs the app has to carry, and what it must get right.

    Jobs to be done · Principles

    Jump to section →
  3. Step 3

    Present Version 1

    Our first version, built in a short span with no real-user context, then tested with the actual users to understand its fallbacks.

    Personas · First screens · Fallbacks

    Jump to section →
  4. Step 4

    Improve it

    Worked on those fallbacks, with a clearer view of the real field scenarios.

    Field scenarios · Trade-offs

    Jump to section →
  5. Step 5

    Create Version 2

    The redesigned app, tested with users in the field and reflected on.

    Version 2 · Testing · Reflection

    Jump to section →
Where it started

We built it first, then went to the users

Version 1 was an MVP, built before our first client, around hypothetical personas we imagined. We then took it to the actual users on the ground, to understand how data collection really works. Meet the personas

On assumptionsOn evidence
  1. 01

    Built Version 1

    A working MVP, built in a short span around hypothetical personas, before our first client, and released to them.

  2. 02

    Understood the users

    In Araku Valley we saw how users collect data today, and how they did it before the app. We came away with a clearer picture of their environment, who they are and what matters most.

  3. 03

    Strategized and redesigned

    We set the jobs to be done and the design principles, to remove the problems we saw users facing.

  4. 04

    Tested Version 1

    We tested it with the actual users in the field, against real working conditions.

  5. 05

    Rolled out Version 2

    The app they use today, with farmer onboarding and biodiversity added as the startup grew. Two people collected 400 data points in two days.

01Understand the users
Contextual inquiry

I went to where the data is collected

I travelled with my team to Araku Valley in Andhra Pradesh, India, to see how users collect data with the current partner app, and how they collected it before the app. We also tested the new partner app with them.

Where
Araku Valley, Andhra Pradesh, India
Method
Contextual inquiry, and testing the new app
With
Field partners, farmers and my team
Studying the trees on site
Studying the trees on site
Understanding how a tree's girth is measured in the field
Understanding how a tree's girth is measured in the field
Understanding how biodiversity data is collected, so the app's features fit the task
My team at an agroforestry site
My team at an agroforestry site
Witnessing the farmer documentation process, to bring it into the app
Witnessing the farmer documentation process, to bring it into the app
The team with farmers and field partners in Araku Valley
With farmers and field partners in Araku Valley
Testing Version 1 of the app with the users: a tree's girth being measured and captured on a phone
Testing Version 1 of the app with the users
Who the actual users are

Two roles, two jobs in the field

Two roles use the app in the field, defined by the job they do. A third person, the manager, depends on the data they collect.

Field data collector

Farmer documentation

Does what

Walks to assigned boundaries and records plantation, growth and biodiversity data, across several boundaries in a day.

Visits farmers and landowners and completes their documentation, so their land can join a project.

Works where

Inside forests and plantations, often with no signal, for a full day on one charge.

On site with the farmer, for the documents, interview, verification photo, contract and land boundary.

Uses in the app

Plantation data · Growth data · Biodiversity data

Farmer onboarding

Needs to

Finish every assigned boundary, and spend less time on the phone, more on the work.

Complete each farmer's documents, and pick up where they left off if a visit is cut short.

Gets in the way

For both roles: instructions lost in calls and chats, details typed by hand with typos, and labels in English, when many partners are more at ease in their own language.

One person or two

Some companies give both jobs to one person; others assign them to different people. The app has to work either way.

Also affected: the manager. They assign boundaries on the dashboard and receive the data, without rebuilding it in Excel first.

Where the growth data goes

To calculate the carbon stock, companies collect growth data for a sample of the trees in a plantation, around 10% in our case. Growth data means the height, leaf and girth of each sampled tree.

Allometric equations then turn this sample into the sequestration for the entire boundary, which is shown on the dashboard.

Current user journey

How users collect field data today

This is the journey users currently follow to collect field data. The manager calls each field collector and sends the boundary location on WhatsApp. The collector navigates there and photographs everything with an app called NoteCam, which keeps every type of data in one pile of photos, saved in the phone gallery. The photos are then sorted by hand and sent on WhatsApp with typed details, and the manager rebuilds it all in Excel.

Can you cover plots4 to 9 tomorrow? Collector 1Collector 2Collector 3ManagerPhone callCalls each field collectorone by oneDetails lost in calls Boundary locations on WhatsAppManagerWhatsAppSends boundary locations Google MapsField collectorGoogle MapsNavigates to the boundary Click! 28.47°N 77.03°E · ±4 m · 10:32Field collectorPhotographs everythingusing the NoteCam appall mixedOne pile of photos ?? PlantationSoilBiodiversity Field collectorGallerySorts the photos by hand, athome Neem · 42 cm · 3.1 m × 200photosField collectorWhatsAppSends photos with typeddetailstyped by handErrors reach the data ManagerExcelRebuilds it all in Excel Auditor / managerManagerSends the report Can you cover plots4 to 9 tomorrow? Collector 1Collector 2Collector 3ManagerPhone callCalls each fieldcollector Boundary locations on WhatsAppManagerWhatsAppSends boundary locations Google MapsField collectorGoogle MapsNavigates to theboundary Click! 28.47°N 77.03°E · ±4 m · 10:32Field collectorPhotographs everythingusing the NoteCam app ?? PlantationSoilBiodiversity Field collectorGallerySorts the photos byhand, at home Neem · 42 cm · 3.1 m × 200photosField collectorWhatsAppSends photos with typeddetails ManagerExcelRebuilds it all in Excel Auditor / managerManagerSends the report
The problems

From the current journey

??

Lost in calls and chats

Work was assigned on calls and locations shared on WhatsApp. Details got lost, and collectors were often unsure what to collect where.

all inone roll

One pile of photos

Every photo, from plantation to soil, landed in the same camera roll, with nothing to say what each one was.

?

Sorting by hand

After a long day in the field, collectors spent their evening sorting photos into categories. Field collection became slow.

Nem · 24 cm typo!

Typed by hand, full of errors

Species, circumference and height were typed manually for every photo. Typos crept in, and the data became inaccurate.

Rebuilt in a spreadsheet

The manager re-entered everything into Excel before a report could go out. Slow for everyone, and one more place for errors.

Problem statement

What had to change

Problem

Field data was collected and passed on by hand, through calls, WhatsApp, a camera app and Excel. As a result, field collection was slow and the data that reached the dashboard was often inaccurate.

Goal

Make field collection fast and the data accurate by default, with one offline-first app where every photo carries its own data and goes straight to the dashboard.

02Strategize
Jobs to be done

One partner, many jobs

In a single day, one partner may onboard a farmer, map a boundary, and record plantation, growth and biodiversity data. The app has to carry all five jobs without getting in the way.

  1. Farmer onboarding

    Collect identity and land documents, interview the farmer, take a verification photo, upload the contract and map the land

  2. Boundary creation

    Create a boundary inside a forest, or a standalone one, by drawing it or walking it

  3. Plantation data

    Record the species and number of saplings planted, with photos of the site

  4. Growth data

    Photograph trees and saplings and mark circumference, height and leaf on the photo

  5. Biodiversity data

    Record fauna, flora, water and soil, with photo, video or voice

From problem to principle

What we saw, and what we built

1We saw

No signal inside the forest

Partners lost time, and sometimes data, waiting for a network that never came. A long day also drained the phone.

2We asked

How might we let partners collect everything with no network at all?

3So the app is

Offline first

Every entry is saved on the phone the moment it is captured. Partners sync once, back home, and can keep battery saver on all day.

1We saw

Details typed by hand, full of errors

Species, circumference and height were typed for every photo. Typos crept in, and the data became inaccurate.

2We asked

How might we make accurate data the easy way, not the extra effort?

3So the app is

Picture first, accurate by design

The photo carries the data. Measurements are captured as photos, date and GPS fill themselves, and a sample image shows what a good photo looks like.

1We saw

English is a barrier

Most partners are not comfortable reading English, so labels and instructions slowed them down and led to mistakes.

2We asked

How might we make every screen clear without English?

3So the app is

In their own language

The whole app switches to the partner's language in one tap, with eleven Indian languages and an icon on every job.

1We saw

Unsure what to collect where

Work arrived over calls and chats, so collectors often didn't know which boundary to cover next, or what was still pending there.

2We asked

How might we show partners what matters for the spot they are standing on?

3So the app is

Most relevant first

Boundaries open nearest first, every job is one tab away, and each boundary shows its own history.

Updated user journey

How field data reaches the dashboard now

With the Partner App, nothing travels through calls, chats or spreadsheets: the data goes from the boundary straight to the dashboard.

ManagerClimate DashboardAssigns boundaries on thedashboardno callsWork arrives in the app 301 m975 m1.5 km nearfirstField collectorPartner AppSees the assigned boundariesand picks the nearest Google MapsField collectorPartner AppNavigates to the boundary Saved on phoneField collectorPartner AppCaptures data as guided photosofflineSaved on the phone PlantationGrowthBiodiversitysorted as you captureField collectorPartner AppField data is sortedautomatically as it iscapturedno typingAccurate data by default 24 itemsSync now Field collectorPartner AppBack home, syncs in one tap ManagerClimate DashboardSees it live on the dashboardno ExcelReport-ready, no rebuilding ManagerClimate DashboardAssigns boundaries onthe dashboard 301 m975 m1.5 km nearfirstField collectorPartner AppSees the assignedboundaries and picks thenearest Google MapsField collectorPartner AppNavigates to theboundary Saved on phoneField collectorPartner AppCaptures data as guidedphotos PlantationGrowthBiodiversitysorted as you captureField collectorPartner AppField data is sortedautomatically as it iscaptured 24 itemsSync now Field collectorPartner AppBack home, syncs in onetap ManagerClimate DashboardSees it live on thedashboard
03The solution
Version 1

The MVP we built, before the user study

This is the first version, built on our assumptions and taken to our first client. Each screen carries what we assumed above it, and what the users showed us below it.

1Colour for recall

We assumed

Each forest was given a colour for recall, assuming users were not very tech-savvy and might not follow English.

Users showed us

Users read and write well, mostly in their own language and some in English. They went by boundary names, not colours, so Version 2 drops the colour.

Version 1 home: a list of forests, each card in its own colour
Version 1 boundaries screen with the plantation overview

2Plantation first

We assumed

Plantation was the most important metric, so Planned and Planted led. We expected users to collect data against these counts and plan around them.

Users showed us

It is a business metric users do not need upfront. The count shows when a forest or a boundary is selected. Version 2 leaves it to the dashboard.

3Species next

We assumed

Plantation is split by species, so the species list came straight after the boundary.

Users showed us

Users are mostly foresters and experienced field people who know their species. For the rare exceptions, Version 2 adds (Other).

Version 1 boundary selected: totals and a species list
Version 1 boundaries screen with the small Create Boundary button

4Create Boundary

We assumed

Boundaries would be created beforehand on the dashboard, so the app needed only a small button for the exception.

Users showed us

Not a daily task, but also done on someone’s behalf, and a dashboard KML can differ from the field boundary. Users create and edit in the app, so Version 2 makes it a main job.

5The job came last

We assumed

After choosing a species, users picked Plantation or Update from a pop-up. The tab bar appeared only after a forest and a boundary were selected.

We realised

Too many steps came before the actual data collection. In the sun and weather of the field, users need to record quickly, so Version 2 cuts the steps.

Version 1: pop-up to choose Plantation or Update for a species
Version 1 growth form with manual number entry or camera

6Typed or camera

We assumed

Growth could be typed or captured by camera, as we were not sure which would work better.

We realised

Even after the photo was captured, users often typed a wrong value, as field conditions invite errors. Version 2 removes the typing.

7One history

We assumed

A single cumulative history page would serve both plantation and growth.

We realised

The product would grow, with more tasks added. One history for all would limit it and clutter the view. Version 2 gives each task its own history.

Version 1 history: plantation and growth together

What this means

Version 1 was the right first step.

After the field visit we understood what matters to users and what does not. Version 2 answers each of these seven points.

Version 2: the app

The current app, screen by screen

Built after the user study, this version answers each of the seven points marked on Version 1. It opens with the five jobs a partner does, placed for quick selection because one partner often does several in a day. Every screen keeps typing to a minimum, so collection is quick and the data is accurate.

The Version 2 home screen with the five jobs as tabs at the top
01

Five jobs, one tap apart

The five jobs sit as tabs at the top of the home screen, so a partner can move between them at once.

  • Farmer onboarding. Register a farmer for a project.
  • Boundary creation. Map a plantation boundary.
  • Plantation data. Record the plantation at a boundary.
  • Growth data. Photograph trees and saplings.
  • Biodiversity. Capture fauna and species.

WhyOne partner does several of these jobs in a single day on the ground, so switching between them is the first thing on screen.

02

In the partner's own language

Partners work in the language they are most comfortable in, so nothing depends on reading English.

  • Language is one tap away. The language button sits in the header of the app.
  • Eleven languages. Each one is shown in its own script, so a partner can spot theirs at a glance.
  • The whole app switches. Labels, field names and buttons all change together, not just one screen.

WhyEverything after this screen depends on being able to read it, so language comes first.

03

Start at the right level

Each job opens on the information that matters for it.

  • Projects for farmer onboarding and boundary creation. Both jobs are done for a project, so the project list comes first.
  • Boundaries for plantation, growth and biodiversity. This data is collected at boundary level, so choosing a project and forest first would be wasted taps.
  • Nearest first. The blue dot is the partner. Boundaries sit around it on the map and are listed by distance, so the closest is always on top.

WhyNo tap is spent on a level the job does not need.

04

Growth: photos, not typing

Inside a boundary, each growth measurement is a photo, and tapping one opens a camera that explains it.

  • Tree or sapling. The one selected decides which photos are asked for.
  • Circumference, height, leaf. Three photos instead of three typed numbers. Our in-house model reads the measurement from each one.
  • Instruction on top. Says exactly how to take this shot: tape around the trunk, at chest height.
  • One tap to capture. Date and GPS are saved with the photo.

WhyEach photo has a purpose. Circumference shows how much carbon the tree stores, height is calculated from the photo, and the leaf lets our model identify the species when a partner picks Other.

05

Biodiversity: fauna first

Animals and birds are gone in seconds, so capturing them has to be the quickest thing in the app.

  • Fauna is the first tab. The most time-critical capture opens by default.
  • Photo, video or voice. Whichever is quickest for what the partner sees.
  • Species after the moment. Species are ticked off a list once the sighting is captured.
  • Switch mode in one tap. Audio, Photo and Video sit together at the bottom of the camera, so the partner changes mode without leaving it.

WhyA missed sighting cannot be retaken, so nothing is allowed to slow the first tap.

06

Farmer onboarding: the fifth job

How a farmer is onboarded

When a project starts, the company visits farmers to take their land's carbon rights.

An interviewer first speaks to the farmer about the land: how it is, which species are grown and how it is doing. If everything goes well, the interviewer returns after a couple of days to get the contract signed, and the farmer is onboarded.

Everything needed to register a farmer is done in the app, from the interview to the contract.

  • One list per project. Each farmer shows how many modules are done.
  • Modules in one place. Documents, Interview, Verification photo, Farmer contract and KML boundary.
  • The interview is recorded. The partner taps record and the questions are shown in groups such as Land Details. There is no form to fill and no answers to write down, and the recording is registered with us.
  • The contract stays with the farmer. It is completed in the app and kept with the farmer's record.

WhyAn interview is a conversation, so the partner should be listening to the farmer, not writing.

Try the app

The real app, running on sample data

Tap through it the way a partner would. The notes beside the phone follow you and explain the screen you are on.

Farmer Onboarding

Projects come first

Farmer onboarding is the first step of a project. At this point only the project exists, created from the dashboard, so it is the only level shown. Forests and boundaries come later.

    Try Tap a project to see its farmers

    Trade-offs

    What I chose, and what I left out

    Each decision had an obvious alternative. These six were decided together with the tech team and the product manager. Four of them come straight from what Version 1 taught us, and in each one speed in the field won over the familiar pattern.

    I chose

    Open on boundaries for plantation, growth and biodiversity

    Instead of

    Opening on projects, then forests, then boundaries, the same way as farmer onboarding

    Because

    This data is collected at boundary level, so choosing a project and a forest first would be wasted taps in the field.

    I chose

    A photo for every measurement

    Instead of

    Typed fields for circumference, height and leaf

    Because

    Manual entry caused most of the errors and was very time-consuming. Our in-house model can read the measurement from the photo, so nothing needs to be typed.

    I chose

    Capture the sighting first, name the species after

    Instead of

    Choosing the species before the camera opens

    Because

    A fauna sighting is over in seconds, so the camera has to open in one tap.

    I chose

    Audio, photo and video side by side in the camera

    Instead of

    Separate screens for each kind of capture

    Because

    The partner can switch mode in one tap without leaving the camera and missing the moment.

    I chose

    Plain screens, with no colour for each forest

    Instead of

    A different colour for every forest, carried through all the pages, as in Version 1

    Because

    Users look for a boundary by its name, not by the colour of its forest, so the colour added little.

    I chose

    Leave the plantation totals to the dashboard

    Instead of

    Planned and Planted counts at the top of the app and on every boundary

    Because

    The count is a business metric. Users do not need it upfront in the field, so the space goes to what they do there.

    04Evaluate and reflect
    Testing in the field

    We tested it where it is used

    Before the rollout, our team took the app into the forest and used it ourselves, capturing data tree by tree, to check that every photo step works outdoors. Then we rolled it out to partners.

    Early result

    What the field has shown so far

    Collection sped up once we rolled the app out to partners.

    Before the app

    25 to 30

    data points collected in a day

    With the new app

    400

    data points collected by two people in two days

    That is about 200 data points a day for the pair, roughly 100 each.

    In use today

    Who uses it now

    The Partner App and the dashboard are live with clients across India and Southeast Asia.

    Success measures

    How I would know it worked

    The early result is a first sign. These five measures would give the full picture of whether the app does what it set out to do. The targets are proposed, and the measures themselves are yet to be tracked.

    MeasureBefore the appProposed target

    Hours spent sorting photos

    Collectors sorted photos into categories by hand, at home, after a long day.

    None. Photos arrive already sorted, because each one is captured for a job.

    Entries that need correcting

    Details were typed for every photo, and typos reached the data.

    2 to 4% of entries need a correction, because our in-house model reads the measurement from the photo and nothing is typed.

    Capture to report-ready data

    Photos went through WhatsApp and were rebuilt in Excel before any report.

    Same day as the partner syncs, with no rebuilding.

    Boundaries completed in a day

    Work was assigned on calls, and collectors often did not know what to cover next.

    30% more boundaries completed per collector per day than under the old process, which sets the baseline.

    Partners working in their own language

    Labels and instructions in English slowed partners down and led to mistakes.

    At least 8 in 10 partners finish a task unaided in their own language.

    Reflection

    What I learned

    Next: test the app with more partners in the field, track the five measures above, and compare them against the targets.