Debugging Design [EN]
-
Upload
magdalena-ostoja-chyzynska -
Category
Design
-
view
355 -
download
0
description
Transcript of Debugging Design [EN]
Debugging designMagdalena Ostoja-Chyżyńska
mchyzynska
WARSAW USABILITY FIX #1 JAN 28, 2014
1. Quantitative testing vs qualitative testing.
2. Why do we test?
3. Optimal amount of users per test.
4. Preparing and performing a test.
5. After the test. What’s next?
usability testing
QualitativeQuantitative
quick usability testing
Quantitative testing
proving a theory
Is the new website better than the former version?
measuring the ratio of successful attempts and time of performing tasks
Qualitative testing
gaining knowledge in order to improve a project
changing protocol afoot is okay
interview with a moderator
no formal collection of data present
“The information is in the people, not in your head.”
Edward T. Hall
why does it work?
1. Nothing is perfect.
2. Serious problems are usually easy to find.
3. Observation of users is always valuable.
N (1-(1- L ) n )
N - amount of all user interface usability problemsL - percent of usability problems found while testing a single user (typical value L = 31%)
http://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/Source:
test preparation
Creation of tasks/task scenarios1. write down main site functionalities
2. convert them to tasks
3. rewrite them to task scenarios
Tester/moderator arrangement
Tester should be sitting in front of the computer.
Task scenarios should be printed x 2 (one bundle for the user, second for you).
Optional agreement for test recording.
Observer should not overwhelm the tester.
video recording
test kick-off
set some neutral page e.g. Google
,,We are testing the interface not you.’’
,,Don’t worry about hurting our feelings…’’
not every question requires/needs an answer
user can ask for a break during the test
turn on recording (if the agreement has been signed)
,,The recording will only be used in order to improve the site’s usability.’’
clean up your browser’s history
Thinking aloud protocol
?@#!
TesT: part 11 min. CONVERSATION
quick chat with the user
What websites do you usually visit?
Do you have any favourite websites?
How many hours a day do you spend using the Internet?
What do you do in everyday life?
Test: Part 22 min. VALIDATING THE CONCEPT OF LANDING PAGE
What can you do on the site?
What is this site about?
Is there anything drawing your attention immediately?
What do you think, who is the owner of this site?
User can scroll through the page, but is not allowed to leave/change the page.
“If I asked the people what they wanted, they would have said ‘Faster Horses’.
Henry Ford
Test: part 312 min. TASK SCENARIOS
Before starting the task you should read out loud each task scenario to the tester.
Build a whole story around the task, so that the tester can easily ‘’fill the described person’s shoes’’.
You feel a bit under the weather and would like to consult a doctor, so that he
can evaluate your condition.
If the tester can not find something important you can help him in a very discrete way. (this is discouraged)
Always thank the tester afterwards.
Be neutral!
what’s next?
List out 3 most serious (according to you) problems with the user interface.
Meet up with the project members for lunch and talk through all perceived by each member (during the test) most serious problems.
Find the easiest way to fix each and every of the 3 most serious problems.
Implement the improvements!
“The ability to simplify means to eliminate the unnecessary so that the necessary may speak.”
Hans Hofmann
Thank you!
Magdalena Ostoja-Chyżyńska mchyzynska
Remember! Performing quick usability tests is always better than not doing anything at all.