Usability Test Script Generator

Tell us what you are testing and get a script you can run tomorrow: consent, tasks, probes and a screener.

Start from an example

Format
Tasks (1 to 5)

Write what the person wants to achieve, not where to click.

1
2
3

Edit the text directly. Changing the form rebuilds it until you do. Saved in this browser only.

This is a template, not legal advice - check it against your organisation's privacy notice.

What you get

Four parts, in order.

Before

Screener

Check people fit your profile.

Open

Intro and consent

Read word for word, then ask to record.

Middle

Tasks or topics

Scenarios, with probes if needed.

Close

Wrap-up

Overall views, thanks, stop recording.

Want a score to report afterwards? Use the SUS calculator.

Questions

FAQ

What goes in a usability test script?

An introduction that explains the session and asks for consent to record, a few warm-up questions, the tasks written as scenarios, follow-up questions to use only when needed, and a wrap-up. Read the introduction out word for word so every participant hears the same thing, and treat the rest as a guide rather than a script you must read. This tool writes all of it for you to edit.

How do I write a good task scenario?

Describe what the person wants to achieve and why, in their words, and leave out the names of buttons, menus and pages. "Find out how much delivery to your address would cost" is a scenario. "Click Delivery and enter your postcode" gives the answer away and tells you nothing. The tool warns you when a task reads like an instruction.

How long should a usability test session be?

Forty-five minutes suits most moderated tests: about 15 minutes of set-up and wrap-up and the rest for three or four tasks. Use 30 minutes for one or two tasks, and 60 minutes or more only when the tasks are long or the product is complex. Participants get tired after about an hour, so a long session produces worse data.

What is the difference between a usability test and a user interview?

In a usability test you watch people try to do something with a product, and you learn where it fails. In an interview you ask people about their past behaviour and needs, and you learn why they do what they do. Test to check a design works. Interview when you are still working out what to build. Both start with the same consent wording.

How many participants do I need?

Five people will show you most of the biggest problems in a single round, and it is better to run several small rounds with fixes in between than one big one. For interviews, keep going until you stop hearing new things, which is often between five and eight. Recruit with the screener questions so the people you talk to match your real users.

Learning UX yourself

Beginner UX (AI) Design starts 14 October 2026.

Tools help you do the work. They don't teach you the judgement behind it. Beginner UX (AI) Design is taught live online by working UX professionals, built for career-changers with no design background.

Book a callSee the course

Working in a team rather than learning on your own? We run in-house UX training built around your own product, and we can talk it through on the same call.