Prototype sketching Flashcards

1
Q

Ways of sketching and components of these prototypes

A

overlaying windows
tracing/overlaying
state transitions
flow charts

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

why use story boarding

A

show me vs tell me
considers both timeline and space of the user
establishes context
can tie different elements of the user inerface or user experience together
important for games and ui’s

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Why prototype

A

get feedback on design faster
experiment with alternate designs
fix problems before code is written
keep the design user centered

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

High fidelity

A

iterated like 5 times

very sophisticated and works close to how the actual end product will work

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

why not just use hi fi

A

can distort the perceptions of the user
- formal representation indicated finished nature
- people comment on unimportant things such as colour, fonts, alignment etc.
Discourages major changes
- testers dont want to change a finished design
- designers dont want to lose effort put into design

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

how to go about constructing the prototype

A
set a deadline
draw a window on a large paper
put different screen regions on cards
ready response for any user action
use copier to make many version
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

how to prepare for a prototype test

A
select particiapnts
- understand their background
- use a questionnaire
- dont use friends and family
Perep scenarios and tasks
Practice before to avoid bugs
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

How to conduct a WOZ Study

A
three or more testers
-greeter
- facilitator - only one who speaks
- computer/wizard
- observors
Approx 1 hr
prep
test
debrief
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

How to conduct a test, in general

A
Greet 
- get forms filled in, assure confidentiality
Test
- explain how will work
- hands written tasks to user
- keeps getting output from participant
- observors records what happens
--avoid reactions
-designers should not lead participants
- only answer questions if they remain stuck for a long time
Debrief
- post eval questionnaire
- follow up
- impressions
- thanks
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What to do when participants get stick

A

indicative of usability problems

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

critical incidents

A

unusual or interesting events during the study

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

example of indications of critical incidents

A

user gets stick
user suddenly understands something
user says “cool”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

what to do with results

A

update task analysis and rethink the design

  • rate severity and ease of fixing problems
  • fix
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

does debriefing help

A

not always
if you ask a question people will alwasy answer even if it is not a reflection of the truth
avoid leading questions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

10 steps to a better evaluation

A

Introduce yourself
Describe the purpose of the observation
If you are having trouble, it’s our fault, not yours!
Tell the participant it’s okay to quit anytime
Talk about the equipment in the room
Explain how to think aloud
Explain that you cannot provide help
Describe the tasks and introduce the product
Written instructions, don’t demo!
Ask if there are any questions; then begin observation
Conclude the observation
Use the results

How well did you know this?
1
Not at all
2
3
4
5
Perfectly