1 / 7

Website usability testing guide

Website usability testing guide. December 2007. Aims. Find problem areas on the website Find things that work well for customers Test how easy it really is to use our site Get customer feedback on our site Quantify this “usability” in some way % success time to perform task

Télécharger la présentation

Website usability testing guide

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Website usability testing guide December 2007

  2. Aims • Find problem areas on the website • Find things that work well for customers • Test how easy it really is to use our site • Get customer feedback on our site • Quantify this “usability” in some way • % success • time to perform task • survey data

  3. Methods • Task-based testing • Clear START and END (success) point • Defined goal(s) of task • Have a “script” – an outline of the questions you’ll ask and what you expect them to do • Measure success rate and time • Observe behaviour during task • Record comments during task

  4. Selecting users • Potential and existing customers • Doesn’t matter if used site before (record though) • Look for “typical” Abcam website users People to avoid • Website people • Experienced (internal) users • Anyone who may be biased in any way

  5. Reassure user • Don’t call it a “test” – “User feedback session” is less scary! • Make sure they know what you’re going to do, what you’re recording and how we’ll use the data • Things to say at the start: • “We won’t necessarily be able to answer questions or help you with the task. We’re not trying to be rude, just it’s more useful to see what you do on your own. In real life you wouldn’t have us here to help you” • We’re not testing you, it is the website we’re testing. You can do nothing wrong. • If you’re having any problems or are confused by what you see, please tell us. It is useful for us to know!

  6. Encourage user to vocalise • “Think out loud” How to help • Demo how to do this (google example) • Ask questions • What were you expecting to see here? • What are you looking for? • What are you trying to do now? • Try not to ask “WHY?”

  7. Recording and writing up • One person times and records • One person asks questions (and records if poss) What to record • Problems and actions • Comments (positive and negative) • Times to different success points • Browser type, operating system and screen size • Personal details (job, experience of Abcam etc) Write up See User testing write up

More Related