Assignment 4: Low-Fidelity Prototypes
(due Monday, October 20 at 11:59 PM)

A prototype is one manifestation of a design that allows stakeholders to interact with it and to explore its suitability. It is limited in that a prototype will usually emphasize one set of product characteristics and de-emphasize others.

– Helen Sharp, Yvonne Rogers, and Jennifer Preece, Interaction Design: Beyond Human-Computer Interaction

For this assignment, you will work in your teams to create two low-fidelity prototypes and evaluate your designs with target users.

Low-fidelity Prototypes #

Select at least two requirements from your previous assignment to be the focus of your prototyping. Brainstorm ideas for how to design an interface to address each of these requirements. Derive a set of tasks that a target user would need to perform in order to meet a selected requirement. For example, if a requirement states that a user needs efficient access to their phone contacts, then the task should involve accessing phone contacts. Consider your scenarios when deriving tasks. Design your prototype around these tasks.

Create two low-fidelity prototypes that address different requirements and tasks. These low-fidelity prototypes should take the form of paper-based prototypes or Wizard-of-Oz prototypes. I recommend paper prototyping because it is quick and easy to create and modify.

For paper-based prototypes, sketch out interface elements and content on paper or index cards. You should be able simulate an interactive experiences by adding and removing paper elements or changing cards. Refer to Section 12.3.3 in the Interaction Design textbook and the following resources for details and tips about paper prototyping:

• What is Paper Prototyping?
• The Magic of Paper Prototyping

For Wizard-of-Oz prototypes, use software instead of paper, but do not actually program functional interaction, rather have a team member simulate the software’s response to user actions. Refer to Section 12.3.3 in the Interaction Design textbook and the following resources for details and tips about Wizard-of-Oz prototyping:

• Wizard of Oz Prototyping
• Wizard of Oz

Have 8 target users perform the derived tasks with each prototype (can be the same users for both prototypes). Make sure to setup the context for what the participant is doing and seeing in the interface, but avoid explaining how to perform specific interactions unless participants are confused. Confusion and uncertainty may indicate a flaw in the design. Have them perform multiple tasks to ensure thorough evaluation of the design. Observe their behaviors. Note any problems. The goal here is to get feedback about your designs that will shape the next step, your high-fidelity prototype. You should iterate on your low-fidelity prototypes if you find problems after the first few participants.

Deliverables #

Deliverables for this assignment will take the form of recorded team presentations and self+peer assessment forms.

Low-Fidelity Prototypes Presentation #

Each team will record a video presentation of their two low-fidelity prototypes and evaluation results. The video should be no more than 7 minutes in length and no smaller than 720p in resolution. All members must participate in the presentation, but you are not required to present equal amounts of the material.

Presentations should:

• describe the set of requirements and tasks for which you designed your prototypes;
• present your two low-fidelity prototypes (with visuals);
• describe what data you collected from having target users perform tasks with your prototypes;
• describe what feedback you gained, what elements of your design worked, what elements of your design did not work;
• present your plans for the high-fidelity, functional prototype.

During the following Tuesday and Thursday classes, the instructor will meet with teams to ask questions about your presentations and provide feedback. All team members are required to attend unless with an excused absense. You are encouraged to take notes during the feedback session. You may also record this session.

One member of each team will submit a link to your slides and recorded presentation via Moodle by Monday, October 20 at 11:59 PM. Please make sure that anyone with the link can view your slides and video. If your slides and video are not viewable, your team will receive 0 points for the presentation component.

Self+Peer Assessment Form #

Fill out the following assessment form: Assessment Form. Provide scores for yourself and all of your teammates. Assessments forms will factor into grade calculations. Submit assessment forms via Moodle by Monday, October 20 at 11:59 PM.

Grading Breakdown (100 points) #

• Low-Fidelity Prototypes [50 points]: Prototypes and tasks address different requirements. Prototypes are either paper-based or Wizard of Oz. Prototypes are thoughtfully designed to address requirements. Prototypes make effective use of design principles.
• Evaluation [30 points]: Design insights revealed through evaluation. Use of appropriate methods, data collection, and data analysis. Clear direction for high-fidelity prototypes.
• Presentation [20 points]: Focused, clear, and concise. Stick to time limit. Use of visuals to help illustrate ideas.