1st Year Cohort programs at SFU Surrey - IAT 432: Design Evaluation
1st Year Cohort programs at SFU Surrey - IAT 432: Design Evaluation
1st Year Cohort programs at SFU Surrey - IAT 432: Design Evaluation
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>IAT</strong> <strong>432</strong><br />
Week 11<br />
Usability Evalu<strong>at</strong>ion<br />
Can Be Harmful
…there were two<br />
HCI researchers:<br />
Saul Greenberg<br />
and<br />
Bill Buxton.<br />
Once upon a time…
Saul Greenberg<br />
• Full Professor in the<br />
Department of Computer<br />
Science <strong>at</strong> the University of<br />
Calgary<br />
• HCI, CSCW, PUI or “NUI”<br />
• Badass mountaineer<br />
• Bonus Q: S<strong>IAT</strong> connection?
Bill Buxton<br />
• Principal Researcher <strong>at</strong><br />
Microsoft Research<br />
• Multitouch and Music in the<br />
1970’s<br />
• Worked for Alias Wavefront<br />
(before Maya was Maya)<br />
• Also a badass mountineer<br />
• Bonus Q: S<strong>IAT</strong> connection?
The would <strong>at</strong>tend conferences…<br />
• Premier HCI conference<br />
• Attended by academia and industry<br />
• 2600+ <strong>at</strong>tendees, not easy to present<br />
5
… and speak to industry…<br />
• Most large IT companies have internal Usability teams<br />
– Test product under iter<strong>at</strong>ive development<br />
– Produce list of Usability issues to be fixed in the next dev<br />
round<br />
6
… and they noticed something very, very wrong.<br />
• Blind usability<br />
– “gives meaningless and trivial results”<br />
– Misdirects or prem<strong>at</strong>urely kills future design directions<br />
7
So they wrote a paper. The End.<br />
8
Wh<strong>at</strong>’s wrong with Usability<br />
• Usability methods are a way to engage in user-centered<br />
design – T/F?<br />
• Weak science<br />
• Objectivity vs. Subjectivity<br />
• Evalu<strong>at</strong>ing Early <strong>Design</strong>s<br />
• Predicting Cultural Adoption<br />
9
Usability is Weak Science<br />
• Scientific methods != good science<br />
– Little discussion of methods, big focus on Quant over qual<br />
• Quant gets an easy pass compared to Qual<br />
– Researchers typically choose the method, then adjust<br />
usability question to fit the method<br />
10
• Ideal HCI science:<br />
Usability is Weak Science<br />
– “When performing a series of tasks, the use of the new<br />
technique leads to increased human performance when<br />
compared to the old technique.”<br />
• Reality HCI science:<br />
– There is <strong>at</strong> least one case where my design performs<br />
better than the old way.<br />
11
Usability is Weak Science<br />
• Existence Proof vs Risky Hypotheses<br />
– If a hypothesis holds in spite of trying to refute it, it is<br />
stronger science.<br />
• Lack of replic<strong>at</strong>ion<br />
– “It’s been done before” -> bias towards new and shiney<br />
– Non experts in your subdomain are more likely to think<br />
it’s been done before!<br />
12
Most Usability methods try to be objective…<br />
Objectivity vs. Subjectivity<br />
…when objectivity may not help improve design.
• How do:<br />
– Graphic designers<br />
– Industrial designers<br />
– Web designers<br />
– Car designers<br />
– Craftspeople<br />
• …tell if a design is good?<br />
Objectivity vs. Subjectivity<br />
14
• <strong>Design</strong>er-as-assessor<br />
Objectivity vs. Subjectivity<br />
– Snodgrass and Coyne – see paper for full ref<br />
• “[<strong>Design</strong> evalu<strong>at</strong>ion] is not haphazard because the<br />
assessor has acquired a tacit understanding of design<br />
value and how it is assessed, a complex set of tacit<br />
norms, processes, criteria and procedural rules,<br />
forming part of a practical know-how.”<br />
15
Objectivity vs. Subjectivity<br />
• Subjective is just as valid (if not more valid) than<br />
objective, depending on context<br />
• <strong>Design</strong> is not m<strong>at</strong>h, physics, chemistry, biology, etc.<br />
• <strong>Design</strong> is embedded in incredibly complex and highly<br />
contextual processes<br />
16
Usability devalues early-stage design<br />
• Brainstorming<br />
– “Your idea is not very user friendly, therefore it is<br />
dumb!”<br />
• Early design is under-specified in ways th<strong>at</strong> often make<br />
it “un-usable”<br />
• Don’t mistake a sketch for a prototype!<br />
17
Getting the <strong>Design</strong> Right (prototyping)<br />
Vs Getting the Right <strong>Design</strong> (sketching)
Usability devalues early-stage design<br />
• Most Usability methods make sense on prototypes, but<br />
not on sketches.<br />
• Use your judgment as a designer!<br />
20
Usability is a poor predictor for cultural adoption<br />
• Useable or Useful?<br />
• Most customers (and many designers) don’t understand<br />
how radically new tech can be useful<br />
21
Usability is a poor predictor for cultural adoption<br />
• Cre<strong>at</strong>ivity is socially constructed<br />
– People have to recognize and make sense of new stuff…<br />
– …but is has to be different enough for them to see the<br />
value<br />
• Big shifts in tech are more likely to change the world<br />
but are hard to eval w. Usability<br />
22
Usability is a poor predictor for cultural adoption<br />
• Consumers and pop media have a short memory and<br />
even shorter <strong>at</strong>tention span.<br />
– Memex – Vannevar Bush, 1945<br />
• http://www.youtube.com/w<strong>at</strong>ch?v=c539cK58ees<br />
– Sketchpad – Ivan Sutherland, 1962<br />
• http://www.youtube.com/w<strong>at</strong>ch?v=495nCzxM9PI<br />
– NLS (aka “The Mother of All Demos”) – Dougles Engelbart,<br />
1968<br />
• http://www.youtube.com/w<strong>at</strong>ch?v=JfIgzSoTMOs<br />
23
If Usability is so harmful,<br />
why do we need this course?<br />
• Tech is cheap, experience m<strong>at</strong>ters<br />
• Sign of a m<strong>at</strong>uring field<br />
• Useful for building standards with broad acceptance<br />
and agreement<br />
• Still better than nothing (sometimes)<br />
24
Other Approaches to <strong>Design</strong> and Evalu<strong>at</strong>ion<br />
• Better understanding of requirements<br />
• Consider cultural aspects th<strong>at</strong> Usability would miss<br />
• Investig<strong>at</strong>ing new interface possibilities through<br />
technical innov<strong>at</strong>ion<br />
25
Other Approaches to <strong>Design</strong> and Evalu<strong>at</strong>ion<br />
• Develop and show design altern<strong>at</strong>ives<br />
– Good design process is sometimes like grinding in an<br />
RPG<br />
– More point in a design space == gre<strong>at</strong>er chance of<br />
better designs!<br />
• Reflect on Pros and Cons of usability <strong>at</strong> a particular<br />
point in design cycle<br />
• Use Usability when it makes sense!<br />
26
• An<strong>at</strong>omy of an HCI paper<br />
– Abstract<br />
Assignment 5<br />
– Intro -> Here’s the problem<br />
– Argument I -> problem<br />
– Argument II -> problem<br />
– Argument III…etc.<br />
– Wh<strong>at</strong> to do? -> fix problems<br />
– Conclusion<br />
– References<br />
27
• Due Wednesday, April 11 th<br />
Assignment 5<br />
– One week before final exam<br />
• Be persuasive!<br />
• You have some time – use it wisely.<br />
– Proof read your submission <strong>at</strong> least twice<br />
– Discuss Q’s early, let ideas percol<strong>at</strong>e<br />
– Email Andrew or I with questions th<strong>at</strong> can be answered<br />
quickly.<br />
28
• Assignment 4 Q’s?<br />
House Keeping<br />
• Email Assignment 5 partner to Andrew by the end of<br />
the week!<br />
• Exam Q Review – Lecture or Lab?<br />
– The vote is for Lecture - AB<br />
29
Lab<br />
• This week’s lab cancelled due to illness<br />
– (Maybe email Andrew and tell him to toughen up/get<br />
better?)<br />
• Next week:<br />
– Guest lecture by Veronica Zammitto (EA)<br />
– Lab: Usability Can Be Harmful exercises<br />
• RTFA!<br />
• I mean, pretty-please read the Greenberg and<br />
Buxton article.<br />
30