Unmoderated Testing

The Tree Test was designed to see where people get lost navigating the menu categories and sub-categories.  This would not prove helpful for our test because we won’t have (or do not plan to) many categories to navigate.  The Optimal Sort Test had tree versions that help organize topics with possible categories.  Again we do no have many categories to worry about.  What was worthy to note about these tests, was the ample result feedback made available, especially the Optimal Sort Test versions.  Way too much for anything we are planning.  The First-Click Test gave results of first impressions of the web design, with limited results, basically pointing to were users went to click, however, perfect for our basic web site.

Our goal is to provide the user with a flight plan calculations, saving the pilot time in his preparations to submit their planned flight with FAA.  Getting their impressions of the site, how fast they can find where to go, and what information is required would be a good indication if our site was working as we intended.  If the user can not locate the intended service, they will not want to use it again, or give positive feed back to new possible users.  If the “flight plan” was too hard to find, say they were over inundated with too much graphics or information; we could simplify the design before testing again.  With each set of tests we could focus in on how easy the process got.  Navigating the site, being clear, concise, and consistent is our desired result.

Moderated Usability Test

Five-Act Interview

  1. A friendly welcome to start the interview
    • Small talk, get them comfortable, relaxed
    • Smile lots and show positive energy (not creepy like)
  2. A series of general, open-ended context questions about the customer
    • Do you own a plane or rent, what kind?  (we want them to have access to planes)
    • How often do you travel privately?  (we want to know how frequently they like to travel)
    • Know many other pilots?  (ultimately we want pilots to share our app, but also want membership to increase)
  3. Introduction to the prototype(s)
    • Show them the mobile app, remind them we are not testing them, but the product (service)
    • Admit you had nothing to do with it, won’t hurt your feelings.
    • Confirm the product may have issues, it’s why we need to test, “talk your way through your thought process”
  4. Detailed tasks to get the customer reacting to the prototype
    • You are hoping to take a flight this weekend with your partner (friend, family member, someone special) and you’re handed this app, where would you begin?
    • How would you input flight information needed for FAA to secure your Flight Plan?
    • Find what the weather will be like where you will be landing?
  5. A quick debrief to capture the customer’s overarching thoughts and impressions
    • Was the information calculated correctly, proving accurate enough for you to confidently submit to FAA?
    • After submitting your flight plan with FAA, how did you find you saved time vs your last method?
    • Would you share this App with fellow pilots, why or why not?