Usability testing questions: 40 examples that work

40 usability testing questions organized by phase, from screener to wrap-up, with a one-line note on what each one is testing for.

Questions asked before a participant touches the product, while they work through a task, and after they finish serve different purposes. These 40 usability testing questions are organized into five phases: pre-test and screening, first impressions, task-based, post-task, and wrap-up. Each includes a note on what it can reveal.

You will not ask all 40 in one sitting. A single session usually pulls two or three questions from each phase, then leaves room for the moderator, human or AI, to follow up on whatever the participant actually says.

Pre-test and screening questions

Ask these before the participant sees anything, to confirm you are testing with the right person and to capture a baseline before the design shapes their answers. For a deeper walkthrough of writing filters that actually screen out the wrong participants, see how to write screener questions that actually screen.

• 1. "What's your role, and how often do you use tools like this day to day?" Confirms the participant is close enough to your target user to give a useful reaction.
• 2. "Have you used a competitor or similar product before, and what did you think?" Surfaces the existing mental model your design has to work with or against.
• 3. "Walk me through the last time you tried to do this without our product." Establishes baseline behavior before exposure to the design affects the account.
• 4. "How comfortable are you trying new apps or tools without instructions, on a scale of 1 to 5?" Segments participants by technical comfort so novice and power-user findings remain distinct.
• 5. "What device are you using today, and is that what you'd normally use for this?" Confirms that test conditions match normal usage, especially for mobile-first products.
• 6. "Before we start, what do you expect this to do?" Captures expectations before exposure for comparison with later first impressions.
• 7. "Is there anything about today that would make this hard to evaluate fairly?" Flags fatigue, distraction, or contextual issues while you can still account for them.
• 8. "Do you have any questions before we begin, or anything about how you usually work that I should know?" Establishes context and may surface a detail that affects the session.

First impressions questions

Ask these in the first seconds after the participant sees the design, before they have had time to explore it or learn its logic.

• 9. "What's the first thing you notice on this screen?" Tests whether the visual hierarchy leads with the intended element.
• 10. "What do you think this page or product is for?" Checks whether the value proposition is clear without explanation.
• 11. "If you had to guess, what would you click first?" Reveals a new user's default path before instructions influence it.
• 12. "What words would you use to describe this so far?" Surfaces the participant's emotional and tonal response alongside the functional one.
• 13. "Does anything here feel confusing or out of place?" Catches structural problems before the participant learns to work around them.
• 14. "Who do you think this is built for?" Tests whether the positioning matches the target audience.
• 15. "What would you expect to happen if you clicked that?" Records the participant's mental model before they learn the actual behavior.

Task-based questions

Ask these while the participant is still working on the task, not after. The goal is to hear their reasoning in the moment, not their memory of it.

• 16. "Go ahead and try to complete the task, and talk me through what you're doing as you go." Introduces the think-aloud protocol that reveals reasoning during a usability test.
• 17. "What are you looking for right now?" Reveals a participant's immediate goal without disclosing where to find it.
• 18. "What did you expect to happen when you clicked that?" Pinpoints where expectation and behavior diverged.
• 19. "What would you do next?" Keeps a stuck participant moving without solving the task for them.
• 20. "Is there anything you'd try before giving up?" Distinguishes a dead end from a participant who is ready for help.
• 21. "How does this compare to how you'd normally do this?" Connects the task to the participant's usual workflow.
• 22. "What made you choose that option over the others?" Surfaces the reasoning behind an observed choice.
• 23. "Was that what you expected to see next?" Checks whether each step confirms or breaks the participant's mental model.
• 24. "How confident are you that you completed that correctly?" Flags false success when the system records completion but the participant remains unsure.
• 25. "What would make this easier to find?" Elicits a concrete suggestion after a findability problem.
• 26. "Is there a faster way you wish you could do this?" Surfaces efficiency concerns that a success-or-failure metric would miss.
• 27. "What are you thinking right now?" Prompts a participant who has gone quiet to resume thinking aloud.

Post-task questions

Ask these right after each task, while it is still fresh, before moving on to the next one.

• 28. "How difficult or easy was that, on a scale of 1 to 7?" Produces a per-task score you can compare across tasks and design iterations.
• 29. "What was the most confusing part of that?" Directs the debrief to a specific moment of friction while it is fresh.
• 30. "Did anything surprise you during that task?" Catches issues the participant noticed only in hindsight.
• 31. "If you could change one thing about that flow, what would it be?" Elicits a specific change tied to the participant's experience.
• 32. "How does that compare to a tool you already use for this?" Benchmarks the flow against the participant's real-world standard.
• 33. "Did you feel in control during that task?" Tests whether the participant completed the task while still feeling lost.
• 34. "Was there a point where you almost gave up?" Identifies near-abandonment that a completion rate would hide.
• 35. "What would you tell a friend who was about to try this same task?" Prompts an unscripted summary in the participant's own words.

Wrap-up questions

Ask these at the very end, once the participant has enough context to reflect on the session as a whole.

• 36. "Of everything we covered today, what stood out most?" Lets the participant prioritize the session's findings.
• 37. "Is there anything we didn't ask about that you think we should know?" Catches issues outside the task list and gaps in the script.
• 38. "How likely are you to recommend this to someone with a similar need, from 0 to 10?" Provides an NPS-style measure that can be tracked across rounds.
• 39. "If you were building this, what would you prioritize first?" Shows which problems the participant considers most important.
• 40. "Overall, how would you rate your experience today, and why?" Captures the overall impression after individual friction points have been discussed.

How to use these questions well

A few of these questions work in almost any phase. Most only work in the one they are written for. Ask a first-impressions question mid-task, or a task-based question at the very start, and you tend to get a generic answer instead of a specific one.

Keep the scope narrow. A test built around a few small, realistic tasks produces more specific answers than an open-ended tour of the product.

Watch your own phrasing for leading language. "Wasn't that easy to find?" invites agreement; "How did you find that?" does not. The post-task and wrap-up questions above are written as open prompts on purpose, so resist the urge to tack a suggested answer onto the end of them.

Some questions work from a fixed script. Others depend on a moderator who can follow up on the participant's response. The distinction between moderated and unmoderated usability testing largely depends on whether that probing occurs.

Where Versive fits in

Versive studies mix these question types directly: an AI Question asks something like the task-based or post-task prompts above, then probes with adaptive follow-ups based on what the participant actually says, in text, voice, or video. See the full question types reference for how each one is configured.

For prototype and website tasks, Versive's AI tests can run a question set against a Figma prototype or live site using AI personas, either before or alongside real participants. Testing a Figma prototype with AI covers the setup. Conversational mode examines the reasons behind a problem, expert-audit mode checks usability heuristics, and an SUS questionnaire provides a score for comparing design iterations. Treat AI test findings as an initial pass, and validate high-stakes findings with real participants.

Start with the questions that match your study's goals and phase, then leave enough session time for follow-ups.