Project Everest

Adopted Experiment

[JAN 19] Functionality and User Experience (Solution) - Fiji FarmEd I

by
Justin Buhagiar
Justin Buhagiar | 7 months ago | in FarmEd - Fiji

Lean Phase: Solution (Prototyping)

Assumption: Farmers find value in the app’s functions

 

Time Box: 4 weeks

 

Key Metrics:

 

Functionality User Experience Rating (FUER)

  • Derived from Functionality User Experience Survey (FUES)

 

          A. Scored 9-10 on FUES

          B. Scored 7-8 on FUES

          C. Scored 4-6 on FUES

          D. Scored 2-3 on FUES

          E. Scored 0-1 on FUES

 

Success point:

At least 75% of the farmers see the app’s functions as a great tool that will assist them, (FUER score of B or above).

 

Green Light:

  • No drastic improvements are needed to the current functions of the app. Can move onto testing next assumption (Farmers are regularly engaging with the application).

 

Orange Light Range:

50% - 75% of farmers have a FUER score of B or above.

Orange Light:

  • Get feedback from farmers about the app regarding functionality and what they would like to see added or modified that will benefit them more than what our competitors are currently offering (Doesn’t include specific content).

Failure Point:

Less than 50% of farmers have a FUER score of B or above.

Red Light:

  • Assumptions made were incorrect about what farmers would like to see in a farming information app.
  • Farmers who were previously interested in the app, are dissatisfied.
  • Get feedback from farmers about the app regarding functionality and what they would like to see added or modified that will benefit them more than what our competitors are currently offering (Doesn’t include specific content).

Experiment build:

 

Pre-departure:

  • Ensure trekkers are familiar with script for demonstration
  • Ensure all necessary documents are prepared prior to step-off
  • Ensure all trekkers have used Hubspot to understand the context behind the village and each individual meeting if required

 

Encounter:

 

  1. Conduct visits to farmers that have been arranged via the phone or through a middleman (eg. District Officer).

  2. Demonstrate the application’s current functions by following the Script and take notes.

 

Post-Encounter:

  • Fill in the FUES, then attain a FUER by inspecting response via the Spreadsheet.
  • Collate all customer information and record it on Hubspot for future reference.
  • Collate all customer feedback to be sent through to the development team.

All links are also attached as PDF’s.

 

edited on 15th January 2019, 03:01 by Jess Riley

James Balzer 7 months ago

This is a really well developed UX testing experiment that is quantifiable and impartial in its data gathering process. That's really good to see.

My only feedback is regarding how the FUES aligns with the assumption that you're trying to test. While there are obviously questions in there that are aligned with understanding how good the user's experience with the app was, other questions are more geared towards how much they would suggest the app or if there are features in the app that they would like.

While these things are really useful to have in a UX test, how do these questions particularly align with testing the above assumption of whether or not "farmers can easily access the app." Perhaps you could re-design your test to assess this more specifically, or maybe re-word your assumption.

Reply 0

Justin Buhagiar 7 months ago

Thanks James!
I actually forgot to change the test assumption and you are correct to say these questions don't align with that assumption. The purpose of this experiment is actually to test whether farmers find value in the apps functions.

Reply 1

Jess Riley 7 months ago

Status label added: Experiment adopted

Reply 0

Share