Writing tasks

How to write effective tasks for prototype testing


Creating effective tasks for a prototype test is crucial for gathering valuable user insights. Participants will take whatever language clues they can get from your task to make it easier. So we recommend avoiding ‘giving away’ the answer so participants are not just matching phrases rather than actually deciding if the information is correct. If tasks include the same language as your prototype test score highly, you can’t infer a lot from the data.

Tips for writing effective tasks

Focus on real-life scenarios

Mimic real-world use: Write tasks that mimic real-world scenarios your users might encounter. This helps you gather more relevant and actionable feedback.

Be clear and specific

Avoid ambiguity: Ensure your tasks are clear and specific. Users should easily understand what they need to do without any ambiguity.

Use simple language

Avoid jargon and complex terminology. Use simple, everyday language to ensure all users understand the tasks.

Avoid existing labels. Use different language in your tasks than the labels on your prototype test.

Provide context

Provide users with enough context to understand the task. Briefly explain the situation and what they need to accomplish.

Keep tasks actionable

Make tasks actionable and achievable. Users should be able to complete them within the prototype's scope.

Avoid leading questions

Ensure your tasks are neutral and don't lead users toward a particular outcome. This helps gather unbiased feedback.

Prioritize your tasks

List tasks in order of importance. Start with critical tasks that align with your primary objectives.

By following these tips, you can create effective tasks that provide valuable insights into your prototype's usability and user experience.

Examples of effective prototype tasks

Creating tasks that are clear, actionable, and aligned with your objectives is key to effective prototype testing. Here are some examples of well-crafted tasks for different types of prototypes:

E-commerce Website

  1. Product search task
    • Task: "Find a pair of running shoes under $100 and add them to your cart."
    • Objective: Test the search and filtering functionality, and evaluate the ease of adding items to the cart.
  2. Checkout process task
    • Task: "Proceed to checkout and fill in your shipping information."
    • Objective: Assess the usability of the checkout process and form fields.
  3. Return policy task
    • Task: "Locate the return policy for the running shoes."
    • Objective: Evaluate the ease of finding important policy information.

Mobile app

  1. Account creation task
    • Task: "Create a new user account using your email address."
    • Objective: Test the account creation process and identify any potential barriers.
  2. Feature exploration task
    • Task: "Use the app to find the nearest coffee shop and view its opening hours."
    • Objective: Assess the usability of the location and information retrieval features.
  3. Notification settings task
    • Task: "Change your notification settings to receive alerts only for new messages."
    • Objective: Evaluate the ease of navigating and adjusting app settings.

SaaS product

  1. Dashboard customization task
    • Task: "Customize your dashboard to include the sales performance chart and hide the user activity log."
    • Objective: Test the customization features and user control over the dashboard.
  2. Report generation task
    • Task: "Generate a monthly sales report for June 2024 and download it as a PDF."
    • Objective: Assess the ease of generating and exporting reports.
  3. Support request tasks
    • Task: "Submit a support request for an issue with your billing."
    • Objective: Evaluate the usability of the support request process and user interface.

Banking application

  1. Balance check task
    • Task: "Check your current account balance and view recent transactions."
    • Objective: Assess the usability of the account overview and transaction history features.
  2. Money transfer task
    • Task: "Transfer $50 to a friend using their email address."
    • Objective: Test the money transfer functionality and user flow.
  3. Bill payment tasks
    • Task: "Set up and schedule a payment for your utility bill due next week."
    • Objective: Evaluate the ease of bill payment setup and scheduling features.

Building tasks

There are three different ways to build tasks in your prototype tests. You can set a correct destination, where the task will be deemed a success if the participant ends the task once they reach that page of your prototype.

You can set a correct pathway, where the task will be deemed a ‘direct success’ if the participant follows that pathway to the intended destination page. In this circumstance, if a participant does not follow the exact path, but does make it to the destination, the task will be labeled an ‘indirect’ success. You can add as many correct pathways or destinations as you like.  The third option is to create a task without a correct answer. We’ll walk you through each option. 

Adding tasks to your prototype test

  1. Click on the ‘tasks’ tab and enter your task text in the box below.

2. Now it’s time to select a starting screen, this is where your participants will begin their task. Click on the starting screen, then click 'Select'.

3. Next, you need to add a correct answer to your task. Click ‘+ Add a correct answer’.

4. From here, you can decide to set either a correct destination, or a correct pathway.

Setting a correct pathway

Navigate your prototype on the right to create the ‘pathway’. The 'correct pathway' you create will become visible on the left of this modal. To delete a step on the pathway, hover over the page and hit the delete icon.

When you have completed your pathway, click on ‘Save pathway'. You can add as many correct pathways as you would like to test.

Setting a correct destination

This is the same process as selecting a starting screen, simply select the screen that you want your participants to reach and hit, “set as correct destination”. If your participants reach this screen and then end their task, the task will be considered ‘successful’.

Creating a task without a correct answer

If you want to create a task without a specific correct answer, you can! For instance, you might ask participants to explore your prototype and share their thoughts. After adding your task description and the starting screen for the task, simply leave the correct answers section blank. We recommend including a post-task question to gather feedback on your design or any other information you need. 

When you create a task without a correct answer, participants will be marked as 'complete' instead of 'successful' or 'failed.' Those who finish the task are recorded as complete, those who skip the task immediately are marked as direct skips, and those who click around before skipping are marked as indirect skips.

If you decide to add a correct answer after launching your study, you can do so, and all existing results will be re-categorized as successes or failures accordingly. Any edits you make to the task copy or correct answers will be retroactively applied in analysis. 

Can I update a correct answer for a task after the study has launched?

If you forget to add a correct pathway or select the wrong option for your task, you can go back at any time and fix it, even after the study is live. This new correct pathway will be retrospectively applied to your results, so you don’t lose any participant insights.