Seasoned Harvest Usability Test Plan

by Shannon Rae

Script I read before the tests:

https://docs.google.com/document/d/1sSw5pM6QyotbXjAkyME_yOs9EDbvfJcuewn-TyJLX9g/edit?usp=sharing

Prototype link: https://marvelaapp.com/9gf2j

Test Objectives

What are we testing and what state is it in? The landing page will be tested to ensure users have an understanding that Seasoned Harvest is a grocery delivery service. The landing page will be in color as we will be asking for feedback on the visual design. The flow of Seasoned Harvest website will be tested using wireframes made clickable through software. The wireframes will be in grayscale to access flow vs. look of the design.

Participants and recruiting

I recruited 30 participants who are willing to take the assessment. Since we are not testing for demand of a product and most people shop for groceries in some form, I plan to do several tests starting with 5 people. According to the Nielsen Norman Group, you only need 5 users to get good results. The article states that: “it is better to distribute your budget for user testing across many small tests instead of blowing everything on a single, elaborate study.” So a good approach would be to spend your budget on 3 studies with 5 users each. Some tests will have more than five because their were more users available. http://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/

Procedure

I plan to do some tests in person first. I can ask questions based on what they do. Testing in person could provide additional insight. This will also help me set up remote testing. The usability test will be sent by email to the majority of the participants.

Tasks

There are several tasks we can test. A-C are separate tests.

A. Landing Page Test

The users will be asked questions to see if they can understand what Seasoned Harvest is about by looking at the landing page alone. They will also be asked their opinion on the design of the landing page.

Scenario: From a web search you landed on Seasoned Harvest’s homepage.

Questions to ask the users-

What is the first thing that catches your eye?

What type of service is Seasoned Harvest?

Does Seasoned Harvest have special products?

Is there anything else that we should add or clarify on that would make someone more likely to sign up?

What do you think about testimonials on a website?

What do you like or dislike about the design of this page?

Which product window do you prefer?

B. Usability of Browsing and Searching

We will test for how easy it is to browse and search.

Scenario: From a web search you landed on Season Harvest’s homepage. You wonder if they sell liquid eggs. Describe each step you would take to find the liquid eggs.

Questions to ask the users-

Once you find the product, how do you see more information?

Are their any details you feel are missing on the product description?

How many ways can you get back to the home page from this page?

From 1(easy) to 5(difficult), what was the ease of completing this task? Details?

C. User purchases items / Prompted to Log In or Register

We have provided a fictitious name, address, and credit card to complete this task.

Name- Hungry Person

Address- 123 Anywhere RD. Yummy, OH 45150

email- foodtodoor@email.com

Visa Credit card- 4608471729102543

expires- 12/19

security code - 349

Scenario: You are shopping for groceries on Season Harvest’s homepage and added some items to your cart.

  1. What steps would you take to purchase them?
  2. How do you register for an new account?
  3. From 1(easy) to 5(difficult), what was the ease of completing this task? Details?

Usability goals

The participant’s reaction to the task.  

How long it takes to complete the task.

If the user failed to complete the task.

Any terminology that presented a stumbling block. 

Error-free rate (the percentage of tasks completed without errors or hiccups).

Following Erika Hall's Severity suggestion, we will rate each problem the users encountered during the test on each of the following two scales: severity and frequency. We must look at both to ensure we’re prioritizing real obstacles.

Severity:

High: an issue that prevents the user from completing the task at all.

Moderate: an issue that causes some difficulty, but the user

can ultimately complete the task.

Low: a minor problem that doesn’t affect the user’s ability to

complete the task.

Frequency:

High: 30% or more participants experience the problem.

Moderate: 11–29% of participants experience the problem.

Low: 10% or fewer of participants experience the problem.