To summarize, these were:
Not defining the specific motivations for testing at the beginning of a study will prevent you from planning effective tasks.
If your tasks are vague or leading, or don’t get at the root of your research questions, you won’t obtain useful results.
Don’t try to test too much at once. Usability testing is most effective when you zero in on a few key questions per study.
If your test has complicated instructions or a large number of tasks, there is a greater chance users will get off track – which is especially important to avoid in remote unmoderated testing.
Doing a trial run will reveal any problems before you spend the time and money testing with a wider audience.
When a session reveals a problem, you can update your design and test your solution with the next participants. Don’t miss this opportunity!
All too often, teams push usability testing back further and further until they haven’t left any time for analysis. In order to get the most value out of your research, you need to spend time understanding it!
Remain objective while observing sessions. Make sure you thoroughly analyze your data before beginning to synthesize trends and devise solutions.
The most insightful findings are totally useless unless you communicate them in a way that’s meaningful and accessible. There is no one-size-fits-all solution for reporting; you need to find the methods that work best for your team.
Finally, we arrive at the ultimate usability testing mistake. This is...
Although we have just spent three articles describing all the ways your usability testing can go wrong, we still believe that any test is better than no test. Simply seeing someone try to use your product or website gives you a fresh perspective on the design you have spent so much time with.
If you are reluctant to conduct usability testing because you are inexperienced or don’t think you have time to learn how, our advice is to just dive in. The more you do it, the more you will learn, and the more rewarding your results will be!