Usability Testing Materials

Preview:

Citation preview

Usability Testing

Wednesday, February 29, 12

Usability is mostly common sense.

Wednesday, February 29, 12

not

Wednesday, February 29, 12

Wednesday, February 29, 12

not

Wednesday, February 29, 12

Wednesday, February 29, 12

But you still need a plan.

Wednesday, February 29, 12

Test Materials

Wednesday, February 29, 12

• Guidelines for observers

• Orientation script

• Background questionnaire

• Data collection instruments

• Agreement & consent forms

• Pre-test questionnaire

• Task scenarios

• Post-test questionnaire

• Debriefing guideWednesday, February 29, 12

Guidelines for observers

Wednesday, February 29, 12

what to do not to do

Wednesday, February 29, 12

• Introduce yourself

• Find out what they need? Anxious?

• Let them know what they’re in for.

• protocols

• testing methods

• testing reasons

Wednesday, February 29, 12

Orientation Script

Wednesday, February 29, 12

Guidelines (p. 156-57)

Wednesday, February 29, 12

Guidelines (p. 156-57)

• Tone

• Length

• Verbatim

Wednesday, February 29, 12

Demonstrate neutrality.

Wednesday, February 29, 12

Wednesday, February 29, 12

you are

Wednesday, February 29, 12

Wednesday, February 29, 12

but you do need to care about them.

Wednesday, February 29, 12

Wednesday, February 29, 12

Wednesday, February 29, 12

The act of observing people can’t help but affect the results.

Wednesday, February 29, 12

Background Questionnaire

Wednesday, February 29, 12

classifiers from screening process

Wednesday, February 29, 12

why?

Wednesday, February 29, 12

Wednesday, February 29, 12

data collection

Wednesday, February 29, 12

What data will address the problem statement/

research question?

Wednesday, February 29, 12

How will you collect the data?

Wednesday, February 29, 12

Who is going to do what?

Wednesday, February 29, 12

Performance Data

Wednesday, February 29, 12

“objective measures of behavior, such as error rates, time, and counts of observed behavior elements”

Wednesday, February 29, 12

Preference data

Wednesday, February 29, 12

“more subjective data that measures the participant’s feelings or opinions of the product.”

Wednesday, February 29, 12

Performance Data:

Wednesday, February 29, 12

• number of errors

• % of tasks completed successfully

• # and type of hints/prompts needed

• # of omitted steps or procedures

• Scores on comprehension tests

Wednesday, February 29, 12

• complete a task

• recover from an error

• achieve a criterion level of competence

• spent reading v working

Time to...

Wednesday, February 29, 12

Preference Data

Wednesday, February 29, 12

• Preference between versions

• Suggestions for improvement

• Number of negative references to product

• Rationales for performance

• Ratings or rankings of product

Wednesday, February 29, 12

(see pgs 166 - 167)

Wednesday, February 29, 12

What type of information will you collect?

Wednesday, February 29, 12

Wednesday, February 29, 12

Listen to the client.Pay attention to your site.

Wednesday, February 29, 12

First things first:

Wednesday, February 29, 12

Where are you going to test?

Wednesday, February 29, 12

These documents are used in varying contexts.

Wednesday, February 29, 12

Wednesday, February 29, 12

Wednesday, February 29, 12

Wednesday, February 29, 12

Ideally, testing is done in the context the document will be used in.

Wednesday, February 29, 12

How are you going to record data?

Wednesday, February 29, 12

Wednesday, February 29, 12

Morae

Wednesday, February 29, 12

Manual data collection

Wednesday, February 29, 12

Observe and take notes on every action.

Wednesday, February 29, 12

Develop a code.

Wednesday, February 29, 12

• You might write “T” when the subject stops reading and does not perform any action to signify that they were thinking

• You might write “F” when the subject flips back and forth to locate something

• You might write “W” when the subject wanders around.

Wednesday, February 29, 12

To use this method, start a table with the elapsed time in one column and the action which occurs in the other.

Wednesday, February 29, 12

By carefully noting what the subject does at each stage, you can locate the difficult parts.

Wednesday, February 29, 12

Nondisclosure FormsRecording Permission

Informed Consent Form

Wednesday, February 29, 12

Pre-test QuestionnairesInterviews

Wednesday, February 29, 12

Task Scenarios

Wednesday, February 29, 12

• Results they will strive to achieve

• Motives for performing the work

• Actual data/names rather than generalities

• State of system when task is initiated

• Any other materials they need to complete the task

Wednesday, February 29, 12

be realisticprovide motivation

Wednesday, February 29, 12

sequence tasks

Wednesday, February 29, 12

Wednesday, February 29, 12

Determine levels of interaction

Wednesday, February 29, 12

The difference between strictly observing a person navigating a document or using a product and participating in what they do is significant.

Wednesday, February 29, 12

But it is also a matter of degree– decide in advance just how much you will interact with your test subjects.

Wednesday, February 29, 12

Wednesday, February 29, 12

silent observation

Wednesday, February 29, 12

talk-aloud protocols

Wednesday, February 29, 12

Post-test Questions

Wednesday, February 29, 12

• Major items related to specific research questions

• Items related to trends/patterns among participants

• Items related to things you can’t directly observe

Wednesday, February 29, 12

Question Forms/Formats

Wednesday, February 29, 12

Likert Scale

Wednesday, February 29, 12

Semantic Differentials

Wednesday, February 29, 12

Debriefing Guide

Wednesday, February 29, 12

Recommended