Your SlideShare is downloading. ×
Usability Testing
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

Usability Testing

441

Published on

Guest lesson usability testing UGent - Belgium

Guest lesson usability testing UGent - Belgium

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
441
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
16
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
  • \n
  • Engineers are more comfortable with the scientific issues associated with systems\n\nNot rewarded for interpersonal “people” skills but for their ability to solve technical problems\n
  • Engineers and programmers traditionally placed the emphasis on the Action part\nMuch less on the human and environment parts\nRelationship between these parts have also been neglected\n
  • Methods and techniques are needed to help designers change the way they view and design products => User-Centered Design (UCD)\n
  • ‘User-Centered Design (UCD) is a user interface design process that focuses on usability goals, user characteristics, environments, tasks and workflow in the design of an interface. The UCD process is an iterative process, where design and evaluation steps are built in from the first stage of projects, through implementation .’ - Shawn Lawton Henry - Accessibility in UCD process\n\n
  • Product can be: sketch, low / high-fidelity prototype, mockup, actual application\n
  • \n
  • Effectiveness/accurate: How many mistakes did people make? (And were they fatal or recoverable with the right information?)\n\nEfficiency: How much time, and how many steps, are required for people to complete basic tasks?\n\nSatisfaction: How does the person feel about the tasks completed? Is the person confident, stressed? Would the user recommend this system to a friend?\n
  • \n
  • \n
  • \n
  • \n
  • Source: Jakob Nielsen & Tom Landauer\nTesting 5 users will tend to uncover 85% of usability problems\nSerious case of diminishing returns for testing additional users\n
  • RITE = Rapid Iterative Testing and Evaluation\n
  • ‘User-Centered Design (UCD) is a user interface design process that focuses on usability goals, user characteristics, environments, tasks and workflow in the design of an interface. The UCD process is an iterative process, where design and evaluation steps are built in from the first stage of projects, through implementation .’ - Shawn Lawton Henry - Accessibility in UCD process\n\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • No need for an experienced data logger\nWho knows when a task starts and when a task is completed or not\nMeasures task completion\nData logger is a distraction to the participant\n
  • The researcher later analyzes the data collected by the tool and reports the results.\n
  • \n
  • \n
  • Transcript

    • 1. Usability Testing Jan Moons @moonsjan
    • 2. The Problem of Unusable Products• Focus on machine and underlying system• Not on the person who will use the system
    • 3. Improve Human Performance Bailey’s Human Performance Model
    • 4. Devigner <> User
    • 5. User-Centered Design
    • 6. Usability Testing• Technique used in User-Centered Design to evaluate the usability of the “product” by testing it on potential users
    • 7. Aim of Usability Testing• Measuring the usability of the “product”
    • 8. Measuring Usability• Effectiveness• Efficiency• Satisfaction
    • 9. Not Usability Testing• Focus Groups: • Small group of people • React to designs and ideas • Sampling of user’s opinions and feelings • Users’ want and needs analysis• Don’t tell whether people can use the product!
    • 10. Usability Test• Watch users• Performing tasks• With sketches, prototypes or application• Note down their problems• Make recommendations• Again!
    • 11. Usual Suspects• Facilitator• Participant, i.e. potential users• Observers / Note takers
    • 12. Example Usability Test
    • 13. How many users?
    • 14. R.I.T.E.• More rounds of small scale (3-4 users) usability tests: • In the first round of tests most of the significant problems are encountered • Fix these problems!!! • In the second round most probably a new set of problems will be uncovered • Etc.
    • 15. When, What and How?
    • 16. Research• Develop usability goals: • Easy-of-use, learnability, rememberability • Benchmarks • Usability tasks• Usability Testing: • Competitive Products • Previous Versions• What to look for? • Like, hate or miss? • Fit in their workflow? • How hard to perform key tasks?
    • 17. Requirements• Usability Testing: • Design concept • Metaphors • Screen flow • Navigation model• What to look for? • Understand the concept? • Is this what they need? • Understand navigation?
    • 18. Design• Usability Testing: • Detailed design • Interaction • Documentation• What to look for? • Understand the concept? • Is this what they need? • Can perform key tasks? • Satisfied?
    • 19. Release• Usability Testing: • Check usability goals• What to look for? • Effectiveness? • Can-do vs. Will-do • Efficiency? • How fast perform tasks? • How many errors? • Satisfaction? • Tell friend about product?
    • 20. www.uxpro.be @uxprobe
    • 21. Real-World Usability• Real users• Real tasks• Real environments• They use the system because they need it!
    • 22. UXprobe SDK
    • 23. Unmoderated Testing• UXprobe automates the usability tests: • Start / stop user sessions • Start / stop task scenarios • Logs screens, features, errors, etc... • Presents post-task questions
    • 24. Dashboard
    • 25. Benefits of UXprobe• Real users, real tasks in real environments• Quantitative data• Statistical confidence• Costs spread over large set of participants
    • 26. Thank you! jan.moons@uxpro.be @uxprobe

    ×