Usability Test Script Generator
Tell us what you're testing and get a script you can run tomorrow: consent, tasks, probes and a screener.
Edit the text directly. Changing the form rebuilds it until you do. Kept in this browser. Log in to save it to your account.
Template, not legal advice. Check it against your organisation's privacy notice.
Study: Moderated usability test | Format: Remote | Length: 45 minutes | Looking at: the checkout flow
Participant: a frequent online grocery shopper
Text in [square brackets] is for you to fill in. Text in quotes is read aloud. Change anything you like.
Before you recruit: run the script once with a colleague to catch unclear tasks. If the tasks do not depend on each other, change their order between participants so one task does not always get the freshest attention.
"Before I ask you a few questions: we'll use your answers only to decide whether this study is a good fit for you, and we'll delete them within [1] month if it isn't. Our privacy notice is at [privacy notice link]."
Note for you: send the privacy notice with your recruitment message, before collecting screener answers. People should see it when you first collect their details, not at the session.
- In your own words, what do you mainly use the Corner Grocer app, or similar products, for? (Open answer) Moderator note: qualify if the answer relates to [the area you are testing].
- Which of these best describes you? (Choose one) A. A frequent online grocery shopper B. [A different group you are not recruiting] C. [Another group you are not recruiting] D. None of these Moderator note: qualify on A only. Do not tell people which answer you are looking for.
- Which of these have you used in the last three months? (Select all that apply) the Corner Grocer app; [a similar product]; [another similar product]; None of these Moderator note: qualify if [the range you need, e.g. includes the Corner Grocer app]. Decide this before you recruit.
- Do you, or does anyone in your household, work in UX design, market research or advertising, or for the company behind the Corner Grocer app? (Yes / No) Moderator note: screen out Yes.
- Are you 18 or over? (Yes / No) Moderator note: Yes is required. Do not book anyone under 18.
- The session is a video call of about 45 minutes, and you would share your screen. Can you do that on a [laptop / phone] with a stable connection on [dates]? (Yes / No) Moderator note: qualify on Yes. Recording consent is asked at the session, not here.
"Hi [participant name], thanks for joining me. I'm [your name]. I'm not here to test you - we're testing the Corner Grocer app. Honest reactions, good or bad, are the most useful thing you can give us."
"Today I'd like to see how you get on with the Corner Grocer app, in particular the checkout flow. You can't do anything wrong. If something is confusing, that's useful for us to know."
"As you go, please think out loud: say what you're looking at, what you're trying to do and what you expect to happen. I may not answer questions during the tasks, because I want to see what you'd do on your own."
Note for you: This is a template, not legal advice - check it against your organisation's privacy notice.
"Before we start, I'd like to explain how we'll use what you tell me. [Organisation name, e.g. Acme Ltd] is responsible for your data (the 'data controller'). If you ever have questions about your data, you can email [contact email, e.g. research@acme.com]. This session is for people aged 18 and over."
"I'll take notes. I'd also like to record your screen and your voice, but only if you agree. You can say no to the recording and still take part."
"[We use Zoom / Teams / Google Meet] for the call and [no transcription tool / Otter / Teams transcription] to transcribe it."
Note for you, read aloud only if it applies: "[If any tool stores data outside the UK: name it and say how it's protected.]"
"We're doing this research to improve the Corner Grocer app. We won't use what you tell me for marketing or sales."
"We rely on your consent to collect this information."
Note for you: Students: use the lawful basis on your ethics approval. If it says public task or legitimate interests, change the lawful basis in the form.
"Please don't share health, financial account or other sensitive details, or personal information about other people. If something comes up, I'll leave it out of my notes."
"Only [named team or people, e.g. the UX research team] will see the notes and any recording. We won't share them outside [that team]."
"It's stored [where, e.g. a restricted folder on our company drive]. Recordings are deleted within [3] months. Anonymised notes are kept for up to [12] months."
"You have the right to see the information we hold about you, to have it corrected, and to complain to the Information Commissioner's Office (ico.org.uk) if you're unhappy with how we handle it."
"You can stop at any time during the session. Afterwards you can withdraw until [date / two weeks after the session]; after that, your input may already be anonymised and combined in our findings, so we can't separate it out. To withdraw, email [contact email, e.g. research@acme.com]. There are no consequences for stopping or withdrawing."
"You'll get [the incentive, e.g. a 20 pound voucher] whatever you decide about recording or quotes, and even if you stop early."
"Our privacy notice is at [privacy notice link], and I can send it to you."
"Three quick questions. One: are you happy to take part on that basis? Two: are you happy for me to record? Three: are you happy for us to use short quotes from this session in our reports, without your name or anything that identifies you? Each is a separate yes or no. Do you have any questions before we begin?"
Start the recording only after you hear a clear yes to the recording question. If the answer is no or unsure, take notes only.
Log the consent: Take part: [yes / no]. Recording: [yes / no]. Anonymous quotes: [yes / no]. Given at [time], by [verbal - noted by moderator / written / chat message].
- "Tell me a little about yourself and what you do day to day."
- "How often do you use apps or websites like this one? Tell me about the last time."
- "Have you used the Corner Grocer app before? What for?"
Give one scenario at a time, on paper or in the chat. Read it out and let the person start. Stay quiet and take notes. Do not point at things or explain the design.
Scenario: "It is Thursday evening and you are out of most things in the fridge. You want to get your usual weekly shop delivered on Saturday morning. Using the Corner Grocer app, show me how you would go about that, and keep talking me through what you are thinking."
Done when: [what success looks like, e.g. the person reaches the confirmation screen]
Watch for: [where you expect people to hesitate or go wrong]
Probe, only if needed:
- "What are you thinking now?"
- "Talk me through what you're looking for."
- "What would you do next? What makes you say that?"
After the task: "Overall, how easy or difficult was that, from 1 (very difficult) to 7 (very easy)? What made you say that?"
Scenario: "You open your order and see one item is marked as out of stock. You want to swap an item that is out of stock for something else. Using the Corner Grocer app, show me how you would go about that, and keep talking me through what you are thinking."
Done when: [what success looks like, e.g. the person reaches the confirmation screen]
Watch for: [where you expect people to hesitate or go wrong]
Probe, only if needed:
- "What would you do next? What makes you say that?"
- "What did you expect to happen when you did that?"
- "Can you say more about that?"
After the task: "Overall, how easy or difficult was that, from 1 (very difficult) to 7 (very easy)? What made you say that?"
Scenario: "You are thinking of moving to a new flat across town. You want to find out how much delivery would cost to your address. Using the Corner Grocer app, show me how you would go about that, and keep talking me through what you are thinking."
Done when: [what success looks like, e.g. the person reaches the confirmation screen]
Watch for: [where you expect people to hesitate or go wrong]
Probe, only if needed:
- "Can you say more about that?"
- "What did you do next?"
- "What are you thinking now?"
After the task: "Overall, how easy or difficult was that, from 1 (very difficult) to 7 (very easy)? What made you say that?"
If someone is stuck for more than a couple of minutes, ask "What would you do if I weren't here?" before you help, and note that you stepped in.
- "What was the easiest thing about using the Corner Grocer app today?"
- "Which part would you like to tell me more about? How did that part go for you?"
- "If you could change one thing, what would it be?"
- "How would you describe the Corner Grocer app to a friend?"
- "Is there anything I didn't ask that I should have?"
"Thank you, that's really helpful. I'll stop the recording now. Your [incentive] will [be sent how and when]. If you change your mind about any of what you agreed today, email [contact email, e.g. research@acme.com]. Do you have any questions for me?"
Stop the recording, then write up your top three observations while they are fresh.
Four parts, in order.
Screener
Check people fit your profile.
Intro and consent
Read word for word, then ask to record.
Tasks or topics
Scenarios, with probes if needed.
Wrap-up
Overall views, thanks, stop recording.
Want a score to report afterwards? Use the SUS calculator.
Frequently asked questions
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.
Beginner UX (AI) Design starts 12 January 2027.
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.
Working in a team rather than learning on your own? We run in-house UX training built around your own product.