Pick one screen
Use the landing page, pricing page, onboarding start, or another single moment. A broad tour produces vague feedback.
Usability test script
Ask less. Watch the task.
A useful first usability test is a short conversation around one real situation. The goal is not to persuade someone that the product is good; it is to learn how they make sense of it.
Create a test taskUse this with people you invite yourself. Ask permission before recording or taking notes, and remove identifying details before sharing what you learned.
Before the call
Set one decision you need to make.
Write one scenario
Frame a situation the person might really have. Avoid telling them which button to use or what they should conclude.
Prepare a note sheet
Give yourself columns for task, observed behavior, exact words, and follow-up. This keeps conclusions from outrunning evidence.
A 15-minute script
Invite the person to think aloud.
- “Thanks for helping. I am testing the page, not you. There are no right answers, and you can stop at any time.”
- “Imagine you want to solve this situation: [plain-language scenario]. What would you do here?”
- “Please say what you are looking for and what you expect to happen as you go.” Stay quiet while they work.
- When they pause, ask “What are you thinking now?” rather than explaining the interface.
- Afterward ask: “What do you think this product is for?” and “What, if anything, would you do next?”
After the session
Turn notes into a modest next step.
Compare the expected path with what actually happened. Mark repeated confusion, but keep unusual reactions visible too.
Choose one change that is small enough to ship or prototype, then test that change with another relevant person.
Do not call the result “validated” because one person liked it. Treat it as evidence with limits.