Your SlideShare is downloading. ×
0
Debugging Design [EN]
Debugging Design [EN]
Debugging Design [EN]
Debugging Design [EN]
Debugging Design [EN]
Debugging Design [EN]
Debugging Design [EN]
Debugging Design [EN]
Debugging Design [EN]
Debugging Design [EN]
Debugging Design [EN]
Debugging Design [EN]
Debugging Design [EN]
Debugging Design [EN]
Debugging Design [EN]
Debugging Design [EN]
Debugging Design [EN]
Debugging Design [EN]
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Debugging Design [EN]

370

Published on

Introduction to quick Usability Testing. In English language. Presentation has been prepared for the first Usability Fix in Warsaw.

Introduction to quick Usability Testing. In English language. Presentation has been prepared for the first Usability Fix in Warsaw.

Published in: Design
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
370
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Debugging design Magdalena Ostoja-Chyżyńska mchyzynska WARSAW USABILITY FIX #1 JAN 28, 2014
  • 2. 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?
  • 3. usability testing quick usability testing Quantitative Qualitative
  • 4. Quantitative testing Qualitative testing proving a theory gaining knowledge in order to improve a project Is the new website better than the former version? changing protocol afoot is okay interview with a moderator measuring the ratio of successful attempts and time of performing tasks no formal collection of data present
  • 5. “The information is in the people, not in your head.” Edward T. Hall
  • 6. why does it work? 1. Nothing is perfect. 2. Serious problems are usually easy to find. 3. Observation of users is always valuable.
  • 7. N (1-(1- L ) n ) N - amount of all user interface usability problems L - percent of usability problems found while testing a single user (typical value L = 31%) Source: http://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/
  • 8. test preparation Creation of tasks/task scenarios 1. write down main site functionalities 2. convert them to tasks 3. rewrite them to task scenarios Task scenarios should be printed x 2 (one bundle for the user, second for you). Tester/moderator arrangement Tester should be sitting in front of the computer. Observer should not overwhelm the tester. Optional agreement for test recording.
  • 9. video recording
  • 10. test kick-off clean up your browser’s history 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.’’
  • 11. Thinking aloud protocol @#! ?
  • 12. TesT: part 1 1 min. CONVERSATION quick chat with the user What do you do in everyday life? How many hours a day do you spend using the Internet? What websites do you usually visit? Do you have any favourite websites?
  • 13. Test: Part 2 2 min. VALIDATING THE CONCEPT OF LANDING PAGE User can scroll through the page, but is not allowed to leave/ change the page. What do you think, who is the owner of this site? Is there anything drawing your attention immediately? What can you do on the site? What is this site about?
  • 14. “If I asked the people what they wanted, they would have said ‘Faster Horses’. Henry Ford
  • 15. Test: part 3 12 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’’. If the tester can not find something important you can help him in a very discrete way. (this is discouraged) Be neutral! Always thank the tester afterwards. You feel a bit under the weather and would like to consult a doctor, so that he can evaluate your condition.
  • 16. 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!
  • 17. “The ability to simplify means to eliminate the unnecessary so that the necessary may speak.” Hans Hofmann
  • 18. Thank you! Remember! Performing quick usability tests is always better than not doing anything at all. Magdalena Ostoja-Chyżyńska mchyzynska

×