USABILITY TESTING OF YOUR PROTOTYPE

PRETEST BRIEFING + INSTRUCTIONS

Listed below are the basic stages of preparing a new user to test prototype. On the left, is a condensed summary of the key point on which to elaborate, and can serve as a quick reference. To the right, is a sample script that you may modify or extend to suit your specific requirements.

GREETING + INTRODUCTION
-Welcome message and introductions
-Briefly describe the project
-Explain the goals of the testing
-Introduce the idea of usability testing / “Thank you for coming. My name is ______and I am developing an official website for the musical act ______. The purpose of this site is to create a marketing vehicle to inform new listeners and fans alike about the latest releases and most recent activities of ______.
The purpose of today’s session is for you to help us figure out how to make this interface more user-friendly before we finish developing it. “
ROLE OF THE USER
-Explain what is expected of the user
-Inform them of the observation and recording process
-Explain that you are testing the interface, not the user
-Reiterate how valuable their input is, and remind them of the compensation offered following the test / “We will give you some tasks that we think are representative of what people might do in real life. Your job is to tell us what makes sense, what’s confusing, whether it works the way you’d expect it to, etc.
I will be observing quietly and taking notes, and the camera will videotape your process for future reference. Keep in mind that we are testing the interface—we’re not testing you—so if you run into any problems it’s not your fault and it means that there is something we need to change. I’ll be sitting next to you, and I can help if you want.
We really appreciate having you come and help us out. After the test, please feel free to take one of the treats as compensation for your time.”
SET EXPECTATIONS
-Acknowledge unfinished nature of the prototype (do not apologize)
-Explain that the design will evolve
-Explain that you will record their suggestions / “The prototype still has some rough edges—we’re still thinking through how it should work and some parts of it are incomplete. Before we cast it in stone, we want to get some feedback about how well this design works. We will be doing subsequent tests, so it’s likely that the final version of the interface will be different than what you see today. If you have suggestions we’ll make note of them, although at this point it is premature to promise what we’ll be able to include in the interface. When we get done with all of the test sessions, we’ll review all of the feedback to help determine our priorities for the next release.”
INSTRUCTIONS
-Reiterate to the user to treat the prototype as they would a real application
-Ask the user to speak their thoughts aloud
-Show special features / “Even though this is a prototype, assume you can do all the things you can do with a final product. While browsing the app, please speak your thoughts aloud so that we can get a better understanding of why you are making particular choices.
If you encounter a screen like this [show user an ‘under construction’ page] it just means that you have reached an area of the site which is not yet complete. Just click the ‘Back’ button to return to the previous page.”
QUESTIONS + CLARIFICATION
-Allow time for questions or clarification
-Have users read task aloud / “Do you have any questions about what we’ll be doing today?
Okay, here’s the first thing we’d like you to do. Take a minute to read this aloud [hand form with sample task to user] and let me know if this makes sense. If so, then whenever you’re ready please show us what you would do first”

DEFINING THE TASK

Before the usability testing occurs, you must first define the tasks you wish the user to perform. Use the template below to articulate your goals for the testing. [Note: the user will only be provided with the input and instructions. All other details are for your own assessment of the user responses.]

TASK #: TASK_NAME
Goal/Outputs
Inputs:
Assumptions:
Steps:
Instructions for users:

Goal/Outputs:

What will users have accomplished when they’re done with the task? How will they know when the task is complete?

Inputs:

List all information or resources—tangible and intangible—that a user would need to complete this task. Examples include, a valid login, business policies, physical objects such as a textbook or a credit card, file names, etc. Real users may have some of this information in their heads—in your usability task you might have to provide this information.

Assumptions:

Assumptions are the conditions and prerequisites that are in place at the start of the task. The assumptions depend on what you want to learn from a task.

Steps:

Write down the steps you expect the user will go through in completing the task. This helps you identify the prototype pieces you’ll need to create. Keep the steps mostly at screen level—no need to list every field.

Instructions for Users:

Provide the user with a clearly-worded description of the tasks he or she is expected to perform.

Sample task scripts:

  • “You heard a song on the radio by ______, and would like to purchase the album. You know the name of the single, but do not know the album name or the year of its release. Navigate the ______website to find out which album you should purchase.”
    Title: Always Searchin’
  • “You are writing an article for a student newspaper, and need some information about the history of the band ______.
    First, you need to locate the year and location where the band first performed. Once this information has been located, find contact information for the band’s management company to set up a telephone interview.”

Adapted from the book Paper Prototyping by Carolyn Snyder, published by Morgan Kaufmann Publishers.

Further resources and templates may be found at: