8 user testing

feedback and iteration

why test?

empathy

explore different approaches

inspiration

why not get expert/stakeholder opinions?

limited focus

based on prior experience

not target users

what's in it for you?

find problems early

do you offer value?

are users satisfied or delighted?

fidelity

what can be tested?

a path to complete a task

data entry

navigation

whether a task is completed

interface conventions

clickablity

what happens if you don't test?

what cannot be tested

static screens

2 screen tasks

tasks that cannot have error (too specific)

dependence on 3rd party content

tasks that require validation

content-hevay value propositins

veracity tasks

what are we observing?

the way they think it works

what they think it does

understanding features

consistency / learnability

errors

preparation

we are testing the software - not you

scenarios / tasks

prototype to support the task

appropriate device

recording apparatus

what is a task?

open-ended description of a goal

contextual to ideal user

achievable with your design

activity

create a task for your software

5 minutes

the facilitator

prepare participant

get them to think aloud

neutral, patient

observant to non-verbal cues

focused on user (notes)

http://s3.amazonaws.c

om/media.nngroup.co

m/media/editor/2014/0

8/18/thinking-aloud-

demo.mp4

talk aloud technique

when you get stuck

what do you think it should do?

sketch - visualize it

iterate

capturing notes

screen recording

note how they verbalize their experience

have a hypothesis first

follow up questionaire

procedure

let them try and complete the task

clarify the task if necessary

don't correct them or guide them

ask them to say when they have completed it

ask them to fill out questions when done