At a Glance

Completing tasks and answering questions are the activities contributors perform during the test so that you can get answers to your research questions.




While completing these tasks, contributors will speak their thoughts out loud so you understand their thought process and the reasoning behind their actions. An example of a task is "Imagine you are thinking about buying a Bluetooth headset, use Google to do the research you normally would" or "After using this webpage, what are three words that describe how you feel about this company?". 

Can’t wait to get started?

We offer a variety of templates with editable tasks so that you can get started quickly. These are great shortcuts to help you write your first test. From the Create test drop-down menu in the Dashboard, select Customize a template.


Below is a quick overview of the different types of tasks available on the Build Test Plan page, reviewing the article Setting Up Tasks can offer more support. If you would like more in-depth information on the various task types, please see our Tasks Overview article. Our Writing Great Tasks article will help strengthen your task-writing skills.


  • Assets: This feature allows you to include a URL, Image, and Video or audio that contributors see or hear during the test. Display an asset and follow it up with additional tasks and questions regarding that asset. 
  • Task Groups: Grouped tasks and results help streamline the test creation process and organize contributor answers for at-a-glance discoveries. Select the task templates relevant to your desired outcome (e.g. findability, content, design evaluation) and the results will be auto-generated in your Metrics tab. 
  • Task: Sometimes referred to as a "blank task," this is an open field where you direct contributors to complete tasks. It is best to frame tasks as a goal you want the person to accomplish, such as "Spend 1 minute finding the ATM closest to Pike Place Market." 
  • Verbal Response: These questions prompt the contributors to provide a spoken answer that correlates with where a contributor is at in the test. This task type is great for asking interview questions, such as "Tell us about the last time you were looking for an airline ticket." This can then be followed with a URL asset pointing to your prototype and a task asking "With your previous answer in mind, how would you find that same ticket using this site."
  • Multiple Choice: This question allows you to ask a question and have the contributor select from a set of answers you provide. You decide if you want to allow the contributor to select only one answer or if they can select multiple answers.
  • Rating Scale: This question allows you to ask a question and provide a scale with defined endpoints, such as "very difficult" to "very easy." You define the endpoints and can select from a number of different sizes for the scale. Be sure to use consistent sizes for your scales throughout the test (e.g., all 7-point scales). This question and multiple choice questions are great for collecting discrete numbers across your contributors (e.g., "8 of 10 contributors rated the task as very easy")
  • Written Response: This question prompts contributors to type their answers into a text box, making it easier to analyze their responses. Note that their verbal responses are recorded at the same time, so a contributor may speak of additional detail beyond what they type into the box.
  • Classic Card Sort: Also known as an "open" card sort, this question has contributors group items into categories and then name those categories (as opposed to a "closed" card sort, in which they group items into predefined categories). Use this task when you want to get a sense of how contributors understand and categorize information.
  • Tree Test: Run a tree test when you want to evaluate the structure and labeling of your site or app, to learn whether contributors would be able to find specific items based on how well (or not) you organized and labeled your content, menus, and call-to-action buttons (e.g., "Add to Cart").

Notes about tasks:

  • If you need some inspiration, select the link under Popular tasks to review and use a task bank of common and popular questions.
  • There is no limit to the number of tasks in a test; however, studies should take 15–20 minutes to complete. Think about how long you expect contributors to spend on each task and limit the number of tasks accordingly.
  • Tasks should not require a contributor to provide any sensitive Personally Identifiable Information (PII). If you are a covered health entity and have signed a Business Associate Agreement (BAA) with UserTesting, you may collect Protected Health Information (PHI); read our article about collecting insights under HIPAA to learn more.
  • Separate follow-up questions from the tasks themselves. Primarily, this ensures that contributors see and answer each of your questions. Secondarily, because each task and question is tagged in the recording, you can skip directly to the specific question and answer in the video. This makes it easier to review the results and create clips to share.

Next Quick Start section: "Launch a Study"

Learn More

Need more information? Read this related article:

Want to learn more about this topic? Check out our University courses.

Please provide any feedback you have on this article. Your feedback will be used to improve the article, and when you submit your survey you'll be entered into a drawing for a $50 Amazon gift card. This survey should take 5 minutes to complete. Article evaluations will remain completely confidential.

Was this article helpful?
30 out of 39 found this helpful