COSC2628 User
Centred Design
Week 5 –Rapid Prototyping & Usability Testing
MIT University acknowledges the people of
Copyright By PowCoder代写 加微信 powcoder
the Woi wurrung and Boon wurrung
language groups of the eastern Kulin Nation on whose unceded lands we conduct the business of the University.
RMIT University respectfully acknowledges their Ancestors and Elders, past and present. RMIT also acknowledges the Traditional Custodians
and their Ancestors of the lands and waters across Australia where we conduct our business.
Ngarara Place
Interface Hall of Fame or Shame?
Submit these to the Canvas Discussion Board “Interface Hall of Fame or Shame” and I’ll pick a couple to be discussed in the lecture
Interface Hall of Shame
• What heuristics are being broken?
• What could be done about it?
Credit Stephen Marcelo
Learning objectives
Understand when and how Understand when and why Be familiar with a range of to use prototypes to conduct user testing types of user testing
Quick Recap
Iterative Design Process
• Ideo’s human centred design process:
http://www.designkit.org
/resources/1
Feedback types?
(Paper) Prototypes
Interviews
Usability tests
Other (see Usability Engineering)
Focus groups Log analysis
Formative vs summative
Summative (evaluative)
Ethnography
Interviews
Cultural Probes
Focus Groups
Diary Studies
Experience Sampling Studies
Studying Similar Products
Interaction Logging of Past Product / Early Prototype Studying Past Product Documentation
Ethnography
Interviews
Focus Groups
Diary Studies
Experience Sampling Studies Interaction Logging
Rapid Prototyping and Mockup
Why prototype?
DEVELOPMENT IS WE WON’T GET IT EXPENSIVE RIGHT THE FIRST TIME
THE EARLIER WE GET WE CAN REFINE OUR FEEDBACK THE EASIER IDEAS
IT IS TO FIX A PROBLEM
Low vs. High Fidelity
• Low fidelity: more like a sketch, missing details. • High fidelity: similar to finished product.
“The low-versus high-fidelity debate lies in the fidelity of prototype required to illustrate a concept, model design alternatives, or test an application. The debate rages to whether prototypes need to be complete, realistic, or reusable to be effective.”
, , , Low vs. High Fidelity Prototyping Debate, Interactions Magazine, 1996
The fidelity of your prototype should match the clarity of your ideas
– , Google Prototyping Video
, , , Low vs. High Fidelity Prototyping Debate, Interactions Magazine, 1996
Prototype features
• Horizontal prototypes: prototype across a breadth of features
• Verticalprototypes:exploringaspecificfeatureindetail
• Look and feel fidelity
• Look—what does the prototype look like?
• Feel—how does the user interact with the prototype?
• Aestheticsdon’tmatter,buttheprototypeshouldreflectinteraction options
Paper prototype: Building
Cut up paper to reflect screen elements
• Windows • Buttons
• Dialogues
Hand draw (or produce like hand drawn) as necessary
Interaction with a paper prototype
• Finger point=click • Writing=typing
Computers interactions simulated by facilitator
Rearranging pieces (e.g. menus) Writing responses
Verbal description of interaction effects
Corrections can be drawn right on the prototype
Benefits and drawbacks
• Cheap to make and quick to edit
• Valuable for learning
• Demonstrates missing functions/problematic task flows
• Users are willing to edit early ideas
Limitations
• Can’t evaluate look and feel
• Response time has to be simulated
• Users can be a bit too polite
Tools for prototypes
Can use digital tools to draw: • Powerpoint
• Balsamiq
Some support scripted interfaces, but remember to make them look “editable”
Invision in use at Uber
https://www.youtube.com/watch?v=x wlCt_eM8BM
Balsamiq and Axure
https://www.figma.com/
Google on the use of prototyping
Go to Quizzes on Canvas The code is
Usability Testing
What testing can tell us
• Behaviour
• Qualitative and quantitative
• All involve use of product
https://www.nngroup.com/articles/which-ux-research- methods/
Quantitative and Qualitative Data in UX research
• Both are useful and complementary
• Qualitative data describes (e.g. give insights to nuance) • Quantitative data counts (measures the significance)
• UX/UCD research does both
• https://www.youtube.com/watch?v=qjsfblXdocg
Usability problems – can you spot it?
Stanstead airport toilet,
Usability problems – can you spot it?
• Where do I press to select the pump I want to use?
How to get quantitative evidence of usability problems in UI?
Eye tracking
Interaction logging
Error rates
Time taken
Steps to completion
Those are tools in user testing
Conducting Usability Studies
What are Usability Studies?
Also known as user testing.
Measured observation of users’ behaviour as they engage with your application.
Uses the scientific methods like metrics, data and measurements to prove assumptions.
What is the goal of a usability study?
To measure ‘effectiveness’ of a feature set
What does effective mean? Depends on development model or clients
Metrics for ‘effective’ must be established pre-test
Usability Testing Example
Usability testing of fruit
Designing a usability test
Tests have several components
• Screener
• Resources (location, equipment, people
• Post test survey
Components of a test plan
• What are you studying?
• How are you measuring it?
• How will you find participants?
• How will the tests be run and by whom?
• When and where will the tests be run?
Template plan
The 1-Page Usability Test Plan by (Image Source: UserFocus) 34
Survey to identify exact users to test—careful to avoid selection bias
Bad screener question
List your favourite Web sites
Write a list of up to 10 Web addresses (URLs) of sites that you go to often
Do you check online news every time you surf the Web?
How often do you check online news? • Several times a day
• Once a day
• Once a week
• Less than once a week • Never
What do you love most about Wired News?
Which features in Wired News are important to you? (check all that apply)
• Number of stories on a given topic
• Number of different topics covered
During a test you need to use a script
• To keep the test structured
• To ensure consistency
The script will include introduction to the test, tester and tasks, and explanations of any equipment used.
Lab-based user testing
Formal usability lab
• Facility design
Low-traffic low-noise area or good sound insulation in walls
Good acoustics and lighting
Electrical, ventilation & ceiling
requirements
Double-pane one-way mirror
• System design
• Digital audio/video/screen-activity monitor/capture
• Event-logging software
• Editing system
The test plan should include all tasks that will be given to testers:
Ideally in the form of a scenario
Complete with all metrics and information that will be collected e.g.
• Time to taslk completion
• Starting/finishing state
• Possible deviations
Observation charts and tables for each table structure recorded observations (good for data analysis)
Post Test Surveys
Questionnaire at the end of the survey to capture additional data
Affirm your observations with data
Open ended questions can be used to gain further insights
Conducting the test: Managing tasks
• Provide each task on a separate piece of paper
• Encourage thinking aloud if you’re running a think aloud protocol
• Do not guide users through tasks—it isn’t a training session
• Consider a short questionnaire after each task
• Time tasks (even if this isn’t your main metric)
Conducting the test: Managing participants
Be very clear the interface is being tested
Encourage users to provide all feedback, including negative
Be polite, friendly and firm
Respond to questions about the interface with your own questions e.g. • Is this the right way to do x? What makes you think it might be?
Compiling findings
Organise comments, findings and measurements
Compare findings to see if there are any common themes
Report any quantitative results
Relate findings to the design you were testing
Usability Testing – examples
Usability testing of Windows 8
Sample eye tracking findings
Banner blindness
F-pattern of web reading
Source: nngroup.com
Discussion
Go to
Brainstorm the range of user testing scenarios for this website.
Discuss what tasks will your user test cover.
Elaborate on which user testing methods you will use and why
15 mins discussion then report back
Special forms of User Testing
Guerrilla user testing
Guerrilla testing: ““the art of pouncing on lone people in cafes and public spaces, and quickly filming them whilst they use a website for a couple of minutes.” ( )
Useful when
• What you are testing (specific tasks, first impressions) require no previous knowledge
• The alternative is no user testing
Check out https://www.youtube.com/watch?v=0YL0xoSmyZI
Remote User Testing
Online services for user testing including
• Crowdsourcing which allows you to set the tasks and do the analysis, and have some control over the participants
• Services such as usertesting.com which run your tests and get results in an hour
You can also run online user testing using services such as Zoom.
Controlled experiments
• Scientific approaches to user testing to ‘prove’ an outcome
• Large numbers of participants (usually 30 or more)
• Can be done in a lab (smaller number of participants, more control) or online (large numbers of participants)
Long history of controlled experiments
• Early example of controlled experiments was a test for vegetarianism, suggested in the Old Testament’s Book of your servants for ten days. Give us nothing but vegetables to eat and water to drink.
Then compare our appearance with that of the young men who eat the royal food, and
treat your servants in accordance with what you see
http://www.exp-platform.com/Pages/KDD2015KeynoteExPKohavi.aspx
Online controlled experiment: A/B testing
• From Ronny Kohavi, Microsoft’s General Manager of the Analysis and Experimentation team & Stanford Professor http://ai.stanford.edu/~ronnyk/
• Concept is trivial
Set your OEC = Overall Evaluation Criterion. Randomly split traffic between two (or more)
A (Control)
B (Treatment)
Collect metrics of interest Analyze
http://www.exp- platform.com/Pages/KDD2015KeynoteExPKohavi.aspx
Case study: The Facebook experiment
Discussion in class
The number of users in usability testing
How many users needed?
• How many?
• Not very helpful answer: Depends.
• A little more helpful: What sort of information are you trying to obtain? How much value would this information bring?
• See earlier lectures
Nielsen suggests
How many users needed? (Nielsen)
Using 5 users to find 84% problems with each of three design iterations
Using 15 users to find 99% of problems with one design iteration
How many users needed?
• The bigger issue is actually approaching the right users.
• Have a good mix.
• Do not test them with fellow developers. You will end up spending hours debating the merits of using some CSS API like bootstrap or semantic UI…
Week 6 Guest lecture
Next week’s guest lecture on Personas
Speaker: , Managing Director ANZ, OneTrust Topic: Mission Statement, Personas, and Use cases
Bio: Rob is the Managing Director of OneTrust for Asia Pacific, Japan. OneTrust is the global leader in privacy, security, and governance software. In 2020 OneTrust was named the Inc 500 fastest growing private USA company at 48,000% over 3 years.
His career spans working and managing teams around the globe; Asia Pacific, North America, West and Central Europe. This includes previous roles at AirWatch(Australia), Telstra(Australia), Gartner(USA), IBM(Asia Pacific, USA, Australia) and .
Rob holds a Bachelor of Mechanical Engineering, Master of Management (Strategic Foresight), CIPP/E & CIPM certifications and is a qualified Fitter & Turner.
This lecture will run in hybrid mode
• Prototyping
• User testing
• Lab based, Guerilla, Remote, Controlled Experiments
• Number of participants
程序代写 CS代考 加微信: powcoder QQ: 1823890830 Email: powcoder@163.com