> Documentation index: https://usertold.ai/llms.txt

# Usability Test Script and Task Examples

A usability test script has four parts: an introduction, one task, a quiet period while the person works, and questions afterwards. This page has a script you can read aloud, task examples for common product areas, and the same test as a UserTold Study that runs on your own site without a moderator.

## Usability test script to copy

Read it as written the first few times. It takes about ten minutes with one task.

```text
INTRODUCTION (1 minute)

Thanks for doing this. I am testing the product, not you. Nothing you do here is wrong.

I will give you one task. Please do it the way you would if I were not here.
While you work, say what you are looking for and what you expect to happen.
I will stay quiet, even if you get stuck. That is on purpose.

I would like to record the screen and your voice for [company]'s product research.
Before this call we sent you who processes the recording and our privacy information.
Taking part is voluntary, and you can stop at any time. Do you agree to the recording?

[Do not start recording until the participant says yes.]

Do you have any questions before we start?

TASK (up to 5 minutes)

[Read the task once, then give it to them in writing.]

Tell me when you think you are finished, or when you would give up.

WHILE THEY WORK

[Stay quiet. Do not answer "is this right?". Say: "What would you do if I were not here?"]
[Note the time of every pause, wrong turn, error message and return to an earlier page.]

AFTERWARDS (3 to 5 minutes)

1. How did that go, in your own words?
2. At [moment you noted], what were you looking for?
3. What did you expect to happen when you clicked [the thing they clicked]?
4. Was there a point where you were not sure what to do next? What was on the screen?
5. Is the result what you expected to end up with?

CLOSE

That is everything. Thank you. Is there anything you want to add?
```

Send the participant your company name, who processes the recording and your privacy information before the session, and start recording only after they agree. [Participant consent](/guides/participant-consent) lists what to disclose.

## How to write the task

The task decides what the test can show. Three rules cover most mistakes:

- **Name the outcome, not the control.** “Send yourself an invoice for $200” tests the product. “Click New invoice in the top menu” tests whether the person can follow instructions.
- **Give a stopping point.** “Stop when you think it is ready to send” tells the person when they are done and tells you what they consider done.
- **Say what they must not do.** If the task could charge a card, invite a real teammate or delete data, say so in the task.

Use one task per test. Two tasks in a row make the second one easier, because the person has already learned the layout.

## Usability testing task examples

Replace the bracketed parts with your own product's words. Avoid the labels that appear on your buttons.

| Area | Task |
|-|-|
| Sign-up and onboarding | Create an account and set up a project for your next piece of work. Stop when you think it is ready to use. |
| First use of a feature | You want to [outcome the feature gives]. Do that for one real item of yours. |
| Pricing page | Your team has five people and needs [capability]. Choose the plan you would buy. Stop before entering payment details. |
| Checkout | Buy [item] with the test card on this page. Stop when you see a confirmation. |
| Search and navigation | Find out whether you can [specific thing]. Tell me the answer when you have it. |
| Settings | Change who receives the weekly report to [address]. Stop when you believe it is saved. |
| Import and integration | Bring in the sample file on this page and check that the first three rows look right. |
| Documentation | Using only the docs, find out how to [task]. Stop when you could do it yourself. |
| Cancellation | You no longer need the paid plan. Move to the free plan. Stop before the last confirmation. |

## Run the same test on your own site without a moderator

The script above needs you in the room or on a call. The UserTold widget runs the same four parts on your site: it shows the task you wrote, records the screen and the person's voice while they work, and then the voice model asks about what just happened. You get the full recording, and each moment where the person had trouble is marked with their words, the page and the time.

```json
{
  "version": 2,
  "goals": [
    {
      "id": "invoice",
      "description": "Find what prevents a new user from sending a first invoice."
    }
  ],
  "segments": [
    {
      "id": "instructions",
      "mode": "speak",
      "title": "Instructions",
      "speak_text": "Please send yourself an invoice for two hundred dollars. Use your own email address as the client. Say what you are looking for while you work. I will stay quiet; choose Done when you finish or want to stop."
    },
    {
      "id": "task",
      "mode": "observe",
      "title": "Send an invoice",
      "instruction": "Send yourself an invoice for $200. Use your own email address as the client.",
      "conductor_context": "This product calls a customer a client. Keep any uncertainty about client details, line items, tax and the send step without assuming any of them caused a problem.",
      "max_duration_s": 300
    },
    {
      "id": "debrief",
      "mode": "talk",
      "title": "Ask about the task",
      "talk": {
        "research_mode": "usability_debrief",
        "goals": ["invoice"],
        "system_prompt": "Use the captured task context to ask about specific pauses, errors, or backtracking. Ask what the participant was looking for and what they expected to happen. If a moment is not supported by the context, ask them to describe what happened instead of inventing a click or problem. Ask one question at a time; do not suggest fixes."
      },
      "experimental_capabilities": {
        "realtime_analysis": true
      }
    },
    {
      "id": "thanks",
      "mode": "speak",
      "title": "Thanks",
      "speak_text": "Thanks for trying the task and telling me what happened."
    }
  ]
}
```

## Ask your agent to adapt it

```agent-prompt
Adapt the usability test script at https://usertold.ai/guides/usability-test-script to my product.

Ask me for one outcome a user should reach, the page the test starts on, and what the participant must not change or purchase. Write the task so it names the outcome and avoids the labels on my buttons. Show the complete Study JSON and wait for approval before saving or activating anything.
```

## How many people and what to do with the result

Five people on one task usually show the problems that most users will meet. Run the test, fix what you saw, then run it again with different people.

After each session, write down three things for every moment you noted: what the person was trying to do, what they expected, and what happened instead. A problem that two or more people met in the same place is ready to fix. One person's trouble is a reason to watch the next session closely.

For the questions themselves, see [usability testing questions](/guides/usability-testing-questions). For a test aimed at sign-up and first use, copy the [onboarding usability test script](/guides/find-where-users-get-stuck). Other research scripts are in [user interview templates](/guides/research-script-templates). How a test without a moderator works is in [unmoderated usability testing](/guides/unmoderated-usability-testing).

[Sign in](/login) and choose **New study**, or read the [Quickstart](/docs/quickstart) first.
