Prototype sketching Flashcards
Ways of sketching and components of these prototypes
overlaying windows
tracing/overlaying
state transitions
flow charts
why use story boarding
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
Why prototype
get feedback on design faster
experiment with alternate designs
fix problems before code is written
keep the design user centered
High fidelity
iterated like 5 times
very sophisticated and works close to how the actual end product will work
why not just use hi fi
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 to go about constructing the prototype
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 to prepare for a prototype test
select particiapnts - understand their background - use a questionnaire - dont use friends and family Perep scenarios and tasks Practice before to avoid bugs
How to conduct a WOZ Study
three or more testers -greeter - facilitator - only one who speaks - computer/wizard - observors Approx 1 hr prep test debrief
How to conduct a test, in general
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
What to do when participants get stick
indicative of usability problems
critical incidents
unusual or interesting events during the study
example of indications of critical incidents
user gets stick
user suddenly understands something
user says “cool”
what to do with results
update task analysis and rethink the design
- rate severity and ease of fixing problems
- fix
does debriefing help
not always
if you ask a question people will alwasy answer even if it is not a reflection of the truth
avoid leading questions
10 steps to a better evaluation
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