Wikimedia Research/Usability testing

This page describes the basics of how, when, and why to do usability testing.

What usability testing is good for

 * Figuring out whether users can complete important tasks, like finding an article, uploading an image, or adding a citation
 * Comparing whether different versions of the same feature, like Visual Editor or Wikitext editor, work better for a certain type of user.
 * Learning what users expect to happen when they perform a new task for the first time.

What usability testing is not good for

 * Learning users' opinions about why they would use your software.
 * Learning users' opinions about whether they would choose your software vs. your competitors.
 * Learning what users think would make your software better.

Create a protocol
A protocol is a list of tasks that test participants will perform with your software. The protocol should contain basic instructions about the task they are being asked to perform. The goal is to give the user enough information that they understand the nature of the task, and where to start, but not to tell them how to accomplish it. These instructions should be written out, so that all users get the same amount of explanation.

Recruit participants
You should recruit participants for your test who have similar goals, needs, and characteristics as the people who use your software. All software is used by people with diverse backgrounds and levels of experience, and particular tasks or features will be more important to some users than others. Generally you will want to test the usability of your software for a particular type of user.