Skip to content
Open fromusers

Goal-based task

Usability tests

A Goal-based task asks participants to accomplish a specific goal on a connected prototype or website. You define the prompt, timing, prototype binding, and what counts as success.

Use goal-based tasks for core flows: checkout, signup, find a setting, or complete an onboarding step. Use Free exploration when you want open browsing without a success definition. Use First click test when only the first click matters.

  1. Open a usability test → Build → Form.
  2. Add a page (or use the Goal-based task template).
  3. Choose Add content → Goal-based task, or start from the testing template.
  4. Write the Task description, set a Time limit, bind the prototype, and configure completion method.

Interactive tasks are not available in surveys or in-product surveys.

SettingOptionsNotes
Task descriptionRich promptTell participants what to achieve, not how
Time limitSeconds (about 1–3600)Default often 300 seconds
Prototype bindingLinked assetFrom Assets & Media
Start screenOptionalWhere the task begins
Task completion methodOn a specific screen, Through a specific pathDefines success in the prototype
URL success criteriaFor URL prototypesWhen success is based on reaching URLs

“Add a team member and assign them the Editor role.” Prototype: Figma onboarding file · Start: Team settings · Completion: specific path through Invite → Role → Confirm · Time limit: 300 seconds.

Goal-based task analytics include:

  • Task summary
  • Path analysis
  • Click heatmap

Combine with recordings when screen or participant recording is enabled on the study.

  • Write goals in participant language; avoid UI element names they have not seen yet.
  • Keep one primary success definition per task.
  • Preview on allowed devices before you set the study to Live.

Common questions

Which study types support goal-based tasks?

Goal-based tasks are available in usability tests only. Surveys and in-product surveys do not include interactive tasks.

How do I define success?

Bind a prototype, set a start screen when needed, then choose completion on a specific screen or through a specific path. URL prototypes can use URL success criteria.

What results should I review first?

Start with task summary, then path analysis and click heatmaps to see where people succeeded or struggled.