24 Usability Testing Questions: Before, During & After

Usability testing measures how well real users can complete real tasks on your product. This guide gives you 24 ready-to-use usability testing questions covering every stage — screener, pre-task setup, in-task probes, and post-test debrief — so you can copy what fits and run a sharper study this week.

The right questions don't replace the tasks — the tasks generate the data. The questions frame what you observe and turn raw behavior into measurable insight.

How Usability Test Questions Fit Together

A typical 45-60 minute moderated usability test has 4 question stages:

Screener (before scheduling) — verify the participant matches your target user
Pre-task (first 5 min) — surface expectations and current workflow
In-task probes (during each task) — non-leading prompts that surface mental models without disrupting the task
Post-task + post-test (after each task + at the end) — measure satisfaction and capture what the tasks couldn't surface

Each section below has 5-7 ready-to-use questions tuned to the stage.

Stage 1: Screener Questions

Screeners verify the participant matches your target user without leaking what you're testing.

How often do you [behavior relevant to your product]? (Daily / Weekly / Monthly / Rarely / Never)
Which of these tools have you used in the last 6 months? (Multi-select with realistic options — include yours, 2-3 competitors, and "None of the above")
What's your role on your team? (Specific titles, not seniority bands)
Are you involved in choosing tools for your team or yourself? (Yes / No)
Have you participated in a user research study in the last 30 days? (Yes / No — exclude professional respondents)

The screening rule: behavioral filtering is reliable; self-rated skill ("Are you good at technology?") is not. Ask what they do, not how they'd rate themselves.

Stage 2: Pre-Task Questions

Pre-task questions establish baseline expectations before the participant touches your product. Done well, they let you measure the gap between "what they thought would happen" and "what actually happened" later.

What do you currently use to [accomplish the task we'll test]? (Surfaces the competitive set in their head)
Walk me through what you did the last time you [task]. (Establishes their actual workflow, not idealized)
When I say [your product category], what comes to mind? (Surfaces brand and mental model associations)
What would have to be true about a tool like this for you to switch from what you use now? (Switching costs)
Before we start, anything you want me to know about how you usually do this? (Catches anything you didn't think to ask)

Stage 3: In-Task Probes

The hardest part of usability testing is asking probing questions without biasing the participant. Use these — they're proven neutral.

What are you thinking right now? (The classic think-aloud prompt — use after 10+ seconds of silence)
What did you expect to happen when you clicked that? (Surfaces the gap between mental model and reality)
What would you do next if I weren't here? (Reveals natural recovery behavior)
Where would you look for [thing they're searching for]? (Map their findability mental model)
Is this what you expected? (Open prompt — let them choose what to compare against)
What's confusing or unclear here? (Direct surfacing of friction points — only use after they pause)
What does "[term on screen]" mean to you? (Vocabulary check — critical for IA decisions)

The waiting rule: after asking a probe, count to 8 silently before saying anything else. The most useful answers come 5-10 seconds after the participant first finishes speaking.

The non-leading rule: never say "easy," "simple," "intuitive," or "obvious." Don't say "what do you like about this?" — say "what's your reaction to this?" Leading words bias responses in both directions (positive and negative).

Stage 4: Post-Task Questions (After Each Task)

Right after each task, while the experience is fresh:

Overall, how difficult or easy was that task? (1 = Very Difficult, 7 = Very Easy — this is the SEQ, Single Ease Question)
What made it that score? (Open follow-up — captures the why behind the SEQ)
What was the most confusing part of that task? (Friction surfacing)

SEQ pro tip: SEQ scores correlate strongly with task completion rates and time-on-task, which makes it the highest-value-per-question metric in usability research. It also lets you compare tasks within a study — a task scoring 5.8 against another scoring 3.2 tells you exactly where to focus design effort.

Stage 5: Post-Test Questions (After the Session)

At the very end, after all tasks:

Overall, how would you describe your experience using this today? (Open — captures the gestalt impression)
What was the single most frustrating moment? (Friction prioritization — they'll name the one that mattered most)
What was the single best moment? (Positive signal — preserves what works)
If you could change one thing about what you used today, what would it be? (Highest-priority change in user language)

Pair with SUS: after these four open-ended questions, administer the System Usability Scale — 10 standardized Likert items that produce a 0-100 score for benchmarking against the 68-point industry average. Takes 2-3 minutes and gives you a comparable metric across studies.

How to Analyze the Responses

Don't try to summarize every question. Focus on three things:

The SEQ heatmap — tasks scoring below 5.0 are your priority fixes. Tasks scoring 6.5+ are your "don't break this" zones.
The expectation gap — for each task, compare the pre-task expectation (Q7-8) against the in-task reality (Q12). The gap is where your mental-model mismatch lives.
Recurring open-ended themes — if 4 of 6 participants name the same friction point in Q22, that's your headline finding, not the things only 1 participant mentioned.

For a 6-participant study, plan 1-2 days of analysis. For 12+ participants, plan a week.

Run a Usability Study in One Workspace

ValidateThat's interview tool supports moderated usability sessions with auto-transcription, theme tagging, and SUS scoring — alongside card sorts, tree tests, first-click tests, and surveys in the same project — so the follow-up tests after a usability finding live in the same study.

Run a usability test free →

Frequently Asked Questions

What questions should I ask in a usability test? Effective usability testing questions cover four stages. (1) Screener — verify the participant matches your target user before they spend time on tasks. (2) Pre-task — surface expectations and current workflow before they touch your product. (3) In-task — non-leading probes like "What are you thinking?" and "What did you expect to happen?" (4) Post-task and post-test — measure overall satisfaction with SEQ and SUS, and ask open-ended questions to surface what your structured questions missed.

What's the difference between SEQ and SUS? SEQ (Single Ease Question) is a 1-7 scale asked immediately after each task — "Overall, how difficult or easy was this task?" It measures task-level perceived ease. SUS (System Usability Scale) is a 10-question 1-5 Likert survey asked at the end of the test session, producing a 0-100 score for overall product usability. Most usability tests use both.

How many usability testing questions should I ask? Plan for 8-15 total questions across the session — not counting in-task probes. More than 15 structured questions adds session time without proportional insight. The data comes from the tasks themselves; the questions just frame them.

What questions should I ask in a screener? Screener questions verify the participant matches your target user definition without leaking what you're testing. Behavioral filtering ("Have you used a card sorting tool in the last 6 months?") is reliable; self-rated skill is not.

What's a good post-task question? The best post-task question is the SEQ (Single Ease Question): "Overall, how difficult or easy was this task?" on a 1-7 scale where 1 is Very Difficult and 7 is Very Easy. It's been validated against task-completion rates and time-on-task.

24 Usability Testing Questions: Before, During & After