[Reprinted] Eight guidelines for Usability Testing

Translation: eight guidelines for Usability Testing

Introduction:
In the professional web design circle, usability testing meetings have become a basic component of any key project. Availability testing is a valuable opportunity to obtain feedback from target users of the website and should be started as soon as possible.

But how do you get the most from these availability test meetings?
　　
1. Select your subject

Like any market research project, the results are the same as those of people you need to test. Do not use people in your own company, friends, or family as testing groups. You can go to any market research company or temporary agency to communicate with them about the participants of this topic. Identifying a market research firm does not provide the company name or any other details, so that these things do not affect the judgment of the participants.

2. Early availability test
Just like anything in life, the first impression is the most critical, and every participant must be relaxed. Remember, the availability test room is usually an extremely man-made environment, and the most useful and informative result is that we want them to behave like they are at home or in the office.

Provide clear guidance on how to reach the availability testing site and, if necessary, meet these participants locally. Do not use terms such as "availability test" or "Market Research" because these will interfere with participants and make them nervous. Similarly, ensure that participants know how long the availability test takes and what type of task they want to perform.

After greeting and greeting, some legal terms are usually signed. It is very important to write in the most easy-to-understand English and to be as short as possible. The last thing is what any intense usability test project needs, namely a contract for something similar to what they signed. For them, all you want is to ensure that these tests are completely confidential and allow data generation as part of our test results during the test process. So tell them this.

3. Start of availability test
　　
Before entering the key tasks, let users familiarize themselves with the environment and tell them the website name and URL, ask them what type of website they like and what information or needs they want to get from their favorite website to get feedback. Take notes on all the terms and statements they use, which not only means that you are taking their feedback seriously, it also provides useful information for key functional and navigation tags.
　　
Next, let them look at the websites they are testing and measure their initial impressions before they become familiar with the websites.

4. Select a task

Setting tasks is crucial to the success of a new website, for example: (an e-commerce website)

• Purchase
• Pay
• Contact customer

Remember, you are not looking for your own information. There is a reason for the establishment of the website-is your target audience doing what you want them to do?

It is also a good idea to ask users to suggest tasks. Although this will give them another hint of expectation and demand, it may suggest new functionality and priority.

5. How to Write tasks
　　
If you give them certain plots rather than instructions, people tend to behave more naturally. When assigning their tasks, you may use the sentence "event a has occurred. Now you need to call the company phone number-find the phone number ". This is much better than "finding a website to contact us.

6. Submit a task

An event is only assigned to the participants with one task, which will make them faster or change their path to the test.

If a user needs to input user input from outside of the test (for example, an email address allows them to enter the password to enter the website), give these input items in the form of the task they proposed. Users will provide useful feedback to all elements of the entire process, rather than simplifying the website.

7. How to perform the availability test

Remember that the website being tested is very important, not only for you or the subject, but also for any valuable feedback you obtain-to ensure that participants are aware of this. If they can't do anything, convince them that this is not their fault.

You must stay quiet and turn a blind eye throughout the test. You cannot change the test results by providing clues, suggesting directions or responses to what they say or do. All feedback given by the year must be neutral. Don't shake your head or get angry, but you can be tempted!

The only time you can talk is to help the participants give their opinions or give a response when they clarify. If you have doubts, shut up!

It is usually difficult for customers to remain silent during the testing process to involve investors in the project. If your customers want to be present, they will be arranged in another room with audio and video connections.

8. After the availability test
　　
After completing all the tests, you should gather as much information as possible and ask about the overall impression of the website so that you can determine whether your expectations have been met, regardless of whether the participants' views on the customer or website have changed in this process.

Frequent inquiries and suggestions-This not only proves your recognition of the value of their ideas, but also gives you a better insight into how websites can better support users.

Finally, ask the participants about the structure and functions of the website they can remember. Clear memories will confirm the logic of the website structure and help identify any classification tags that you may ignore.

Reference This article is written by Tim fidgeon, the leader of usability at webcredible. He is keen on availability and operates on the availability training of the webcredible website and writes for the online training. Respect for the author's hard work. For reposted, please mark the source. ---------------------- thanks to "xiaoxian" for its support for translation

Original article:
Introduction
In professional web design circles, the usability testing session has become an essential component of any major project. similar to focus groups in brand development and product launches, usability Testing offers a rare opportunity to receive feedback from the very people the website is aimed at-before it's too late to do anything about it.

But how can you get the most from these usability testing sessions?

1. choosing your subjects
As with any market research project, the results will only be as good as the people you test. do not test people from your own company, or friends and family. go to a market research firm or temp agency and ask them to source particle to a certain profile. make sure the market research firm does not provide the name of the company or any other details that will cloud the judgement of the participant.

2. Before the usability testing
As with everything in life, first impressions are vital. each participant ipant must be put at least. remember, the usability testing session is often an extremely artificial environment and, for the most beneficial and informative results, we want them to behave as if they were using the site at home or work.

Provide clear instructions on how to get to the usability testing location, and if necessary meet the participant at local stations. do not use terms such as usability testing or market research, as these can confuse and put people on edge. also, ensure that maid know long the usability testing will take, and the type of tasks they will be expected to perform.

After the initial greeting and welcoming drinks, there are always legal forms that must be signed. it is essential that these are written in plain English, and are as short as possible. the last thing any nervous usability testing subject wants is to be given a contract that looks like they're signing their soul away. all you want is for them to be reassured that the tests are completely confidential, and for permission to use the data generated during the test as part of our results. so tell them that.

3. Beginning the usability testing
Before diving into key tasks, get the user familiar with the environment. tell them the website's name and URL, and ask them for initial feedback on what they wowould expect CT from the site or what they wowould like the site to be. make note of any terms or phrases they use-This not only demonstrates you are taking their feedback seriously, but may provide useful tips as to possible labels for key functionality or navigation.

Next, let them look at the website they are testing. gauge their first impressions before allowing them to familiarise themselves with the site.

These few simple tasks will help convince the participant ipant that the usability testing will not be difficult and, perhaps most importantly, that they're not the ones being tested.

4. Choosing tasks
Set tasks that are essential to the new site's success, such:

* Buying products
* Paying bills
* Contacting the client

Remember, you're not looking for an ego massage. The site was built for a reason-Can your target audience do what you need them to do?

It's also a good idea to ask the user to suggest tasks. While this gives another indication of their expectations and requirements, it may suggest new functionality or priorities.

5. How to word tasks
People tend to perform more naturally if you provide them with scenarios rather than instructions. when giving them tasks, you shoshould use phrases like scenario A has occurred, and you need to ring the company urgently-find the telephone number. this is far better than find the Contact Us section of the site.

6. Presenting tasks
Only give particle tasks one task at a time. More than this may intimidate them, or alter their approach to the test.

If the user is required to use inputs from outside the test (e.g. an email giving them a password to the site), give them these inputs in the form they will be presented. this will provide useful feedback on all elements of the process, rather than simply the site.

7. How to behave during the usability testing
It's essential that you remember that it's the website that is being tested, not you or the subject. any feedback you get is valuable-make sure the participant knows this. if they can't do something, make sure they know it's not their fault.

You must stay quiet and out of sight during the test. you must not alter the test results by providing clues, suggesting directions ctions or by reacting to things they say or do. all feedback you give must be neutral. do not start shaking your head or huffing, however tempting it might be!

The only time you shoshould speak is to help the participant give an opinion, or to clarify a response. If in doubt, shut up!

Given the investment made in the project, clients often find it difficult to be quiet during tests. If your client wants to be present, put them in another room with an audio/video link.

8. After the usability testing
After all the tasks have been completed, you should gather as much information as possible. asking for overall impressions of the site will allow you to judge whether expectations have been met, and whether the participates ipant's view of the client or site has changed during the process.

Always ask for suggestions-This not only demonstrates the value you place on their thoughts, but may provide insights into how the site can better support the user.

Finally, ask the participating ipant what they remember about the site Structure and Functions of the site. clear recollection will confirm that the site is structured logically and help identify any labeling issues you may have missed.