CS124: Investigation 4

Paper Prototyping

Due: 
Wednesday, Feb 17, 2:45pm in class (Prototype)
Wednesday, Feb 24, 2:45pm on Sakai (Report)

This is a pair investigation.  You should work with the same partner that you worked with on Investigation 3.

Goals

The goals of this Investigation are:

Before you Begin

Before you begin you should have completed Investigation 3.  If you have any concerns about your design, come see Prof. Alvarado before you start prototyping!

Assignment

In this investigation your goal is to construct a paper prototype and use that prototype to test your initial interface design from investigation 3.  The end result of this assignment will be observations about what was wrong with your original design and a redesigned interface designed to address these problems. 

Part 1: Paper prototype construction

Based on your design, construct a paper prototype that is broad and deep enough to support the tasks you developed in Investigation 3.  Clearly you will not have time to prototype your entire interface, so focus on the components of the interface that you believe are the riskiest.  For example, there's no need to prototype a standard file open dialog, but you should prototype a novel dialog box style, e.g., one that incorporates speech input.  Some other factors that contribute to the risk of a particular piece of your interface are:
On Monday, Feb 15 there will be an optional prototype construction session from 12-1pm in Beckman B134.  I will have supplies for building prototypes, but if you have anything specific you need, please bring it yourself.  I will be available to answer any questions you may have.  

Part 2: User testing

We will perform initial prototype testing in class on Wednesday, Feb 17.  To prepare for use testing you should:
  1. Prepare a short introduction that you will read to the user at the beginning of the test.  This introduction should briefly describe the purpose of the interface, but should not instruct the user about how to use the interface (see example below).  It should be concise and to the point.
  2. Prepare a set of instructions that you will read to the user (see example below).  These instructions will help the user understand what to do, and help them feel more comfortable in the test.
  3. Write brief descriptions of your three tasks from Investigation 3 on note cards that you will hand to the user (one at a time) during testing.  These tasks should be brief and should provide the user with the context of the task and the task to be performed (but NOT how to perform the task, of course).  (See example below).
  4. Decide which role(s) you will play.  The facilitator will have to double up as the observer.
  5. Practice running the tests several times with each other until you can run them smoothly.
In class testing will only be part of the user testing you do with your paper prototype.  At some point after the class prototype testing session you need to test your prototype on at least 3 users not in CS 124/182.  

Example:

To help you with your background statement and your task descriptions, here is an example of what you might write if you were evaluating the Google search interface:

Background (read to user):
"We are designing a desktop computer interface for a search engine program.  This program will allow users to search for information on the Internet as well as perform other tasks such as find driving directions, check their email and search for images.  Your participation in this test will help us understand strengths and weaknesses of the current interface design."

Instructions (read to user):
"You will be asked to perform several tasks using the interface prototype in front of you.  You will use physical actions to represent mouse and keyboard actions.  To click on the screen, simply point to part of the interface and tap it.  To type, simply write on the screen where you would type.  As you interact with the interface, my partner will manipulate the interface to reflect how it would change in response to your actions.  In some cases she will describe what is happening verbally.  

We will be taking notes as you perform your tasks, and it is important that you understand that we are evaluating the interface, not your performance.  Please think out loud as you perform your tasks, articulating what you are thinking, why you choose the actions you take, and what seems unclear or missing.  If something seems difficult or unclear, it is the fault of the interface, not you.  You may ask us questions, but sometimes we will not answer them because we want you to explore the interface without our help.

Do you have any questions before we begin?"

Task (written on a note card that is handed to the user):
"Your good friend just bought a house and is having a housewarming party tonight.   She lives at 555 N. Jackson St. in Claremont, and you will be coming from Harvey Mudd College.  You want to stop by and pick up a drink to bring to the party on the way.  Your task is to 1) find a grocery store on the way from campus to the party (or as close to on the way as possible), and 2) find driving directions from Harvey Mudd to the grocery store and then to your friend's house."

Note: I have created this 2-step task as a single tasks because I believe both parts can be done relatively quickly.

Part 3: Identification of usability problems and redesign suggestions

Based on your observations, propose changes to your interface, and describe how the proposed changes would address the problems you observed.  You should include sketches (or full storyboards) of your new interface when the sketches will help you describe your modifications.  The number of changes you propose will depend on what you observed, so there is no "correct" number to submit here.

What to Bring to Testing Day (2/17)

You will not hand anything in on testing day.

What to Hand in On the Final Due Date (2/24)

Grading

Investigation 4 grading rubric
Back to CS124 Investigations Page