You write "Tap Sign up, enter your email and choose a plan", send it to five testers, and get five recordings of people tapping Sign up, entering their email and choosing a plan. You learned that people can follow instructions. You didn't learn whether they'd have found Sign up on their own.

The task wording decides what a usability test can show you. I wrote a step-by-step guide to a five-person test last week; this is the part of it people get wrong most often, so it gets its own post.

The rule

Describe what the person wants and why. Never describe the interface.

A task that names a button, a menu or a screen has already answered the question you were trying to ask. A task that names a goal makes the tester find the way, and the way they look is the data.

Five ways a task gives the answer away

  1. It uses your UI words. "Open Collections and add a recipe" tells them the section is called Collections. If they'd have looked under "Saved", you'll never know.
  2. It lists the steps in order. "First set your goal, then pick a reminder time" walks them through your flow in the order you designed it.
  3. It names the right option. "Choose the monthly plan" skips the moment you most need to watch: comparing plans.
  4. It praises the thing being tested. "Try our quick checkout" plants the idea that checkout is quick. Testers are polite and will tend to agree.
  5. It asks for an opinion instead of an action. "Is the onboarding clear?" gets you "yes, pretty clear" from someone who just struggled through it. Watch them do it, and ask for opinions at the end.

What a good task has

Three parts:

  • A situation: who they are right now, in one sentence.
  • A goal: what they want to get done, in their words.
  • An end point: how they'll know they're finished, so they stop instead of wandering.

A template that works for most apps:

You [situation]. [What you want]. You're done when [end point].

For example: "You've just moved and want to keep your spending under control. Set yourself a limit for groceries this month. You're done when the app shows you how much of it is left."

12 examples

Made-up apps, but these are the kinds of flows people send to testers every week.

App Leads the user Better
Habit tracker Tap + and create a habit called "Read" You want to read a little every evening. Get the app to help you keep at it.
Budgeting Go to Budgets > New and set a $400 limit for Food You want to spend less than $400 on food this month. Set that up.
Recipes Use search to find a vegetarian recipe Find something you could cook tonight without meat.
Fitness Start the 20-minute beginner workout You have 20 minutes and haven't exercised in months. Find something you could do right now.
Online shop Add the blue jacket in size M to your cart and check out Buy a warm jacket for under $80. Stop before you'd pay.
Booking Select Thursday 3 PM and confirm Book a haircut for some time Thursday afternoon.
SaaS dashboard Click Invite, enter a colleague's email, assign Editor A colleague needs to edit your projects but shouldn't see billing. Give them access.
Notes Create a folder named Work and move two notes into it Your work notes and personal notes are mixed up. Sort them out.
Language learning Complete Lesson 1 of the Spanish course You're going to Spain in a month. Start learning something useful.
Game Tap Play, then finish the tutorial level Play for a few minutes the way you would on a bus.
Chat Open Contacts, find Sam and send a voice message Let a friend know you'll be late, without typing.
Photo editor Use the Crop tool to make the photo square Get this photo ready to use as a profile picture.

Two things to notice. None of the better versions contain a word from the app's interface. And some of them can be finished in more than one way, which is fine: if half your testers crop and half use a "fit to square" button you forgot you had, that's a finding.

When the tester needs something to finish

Some tasks can't be done without a login, a test card or a code. Put whatever they need in the task itself: "Use the coupon WELCOME10 at checkout", or "Log in with the test account below". Otherwise you get recordings of people stuck at a screen you didn't mean to test.

If you're testing payments, use your payment provider's test mode and say so in the task, so nobody hesitates over entering a card.

How many tasks, and in what order

Three to five for a 10 to 15 minute session. Put the flow you care about most first. Testers are sharper at minute two than at minute twelve, and some recordings end early.

Keep one goal per task. In our recordings, the AI marks the moments where a tester pauses, and in 49 of 679 sessions at least one of those pauses was the tester going back to reread the task. A task with three goals in it is easy to lose track of halfway through.

Questions for the end

After the tasks, a few questions that are hard to answer with a polite yes:

  • Was there a moment you weren't sure what to do next? Where?
  • What did you expect to happen when you [did the thing that went wrong]?
  • What would you call [the screen or feature]? (Their word is often a better label than yours.)
  • If you could change one thing, what would it be?

Avoid "Did you like it?" on its own. Most people will say yes to the person who built it.

Try the tasks on one person first

Before you send tasks to five testers, give them to one person and watch. If they ask "what do you mean by...?", rewrite that task. It takes ten minutes and saves a whole round of recordings that answer the wrong question.

Disclosure

I run TestFi, where testers record their screen and talk through tasks like these on their own phones. A recording is $5.99 per tester, and each one comes with a transcript and timestamps for the moments they got stuck. It's here if you want to try your tasks on strangers.

If you have a task you're not sure about, paste it in the comments and I'll suggest a version that doesn't lead.