Back
UX Survey Questions: 40 Examples, SUS and SEQ

Matthieu Saussaye

UX survey questions ask users about their experience with a website, app or product: whether they could complete what they came to do, how easy it was, what got in the way, and how they feel about using it. The strongest UX surveys combine one validated score, such as the Single Ease Question or the System Usability Scale, with open questions about specific moments.
The short version:
Ask about behavior before attitude. "What were you trying to do?" and "Did you manage it?" come before "How satisfied are you?"
Use a validated scale for benchmarking: the SEQ after a task, SUS after a test session or for an overall product score.
Trigger questions in context. An in-app question right after a task beats an email a week later.
Keep intercepts to one or two questions; longer studies go to opted-in users.
Surveys show what and how many; usability tests show why. Use both, and use open questions with follow-up to close the gap.
UX survey formats compared
Format | When to use | Example question | Output | Length |
|---|---|---|---|---|
Single Ease Question (SEQ) | Right after a task | Overall, how difficult or easy was this task to complete? | Task-level ease score on a 7-point scale | 1 question |
System Usability Scale (SUS) | End of a usability test, or periodic product benchmark | I thought the system was easy to use. | 0-100 usability score | 10 items |
Intercept / on-site survey | During a live visit | What did you come here to do today? | Visit intent and success rate | 1-3 questions |
Onboarding survey | After sign-up or first key action | What almost stopped you from signing up? | Friction points in activation | 2-4 questions |
Feature feedback | After first use of a new feature | How useful is [feature] for your work? | Adoption and usefulness signal | 2-3 questions |
Research recruitment screener | Before interviews or tests | How often do you use [product]? | Qualified participants | 5-8 questions |
Nielsen Norman Group notes that these post-test and post-task questionnaires are rarely meaningful by themselves without performance data such as success rates or task times. Treat them as one signal among several.
40 UX survey questions by purpose
Task success and intent
What did you come to [site/app] to do today? (open, or list plus Other)
Were you able to complete what you came to do? (Yes / Partly / No)
If not, what stopped you? (open)
How long did it take compared with what you expected? (Much longer / Longer / As expected / Shorter)
Overall, how difficult or easy was this task to complete? (7-point, Very difficult to Very easy)
What, if anything, would have made this task easier? (open)
Navigation and findability
How easy was it to find what you were looking for?
Where did you expect to find [item]? (open)
Did you use search to find it? (Yes / No) If yes, did the results help? (Yes / No)
Was any label or menu item unclear? (open)
How confident were you that you were on the right page? (Not at all to Completely)
Onboarding and first use
How easy was it to get started?
What almost stopped you from signing up? (open)
Which step of setup was the most confusing? (list of steps)
Did you feel you understood what the product does after the first session? (Yes / Somewhat / No)
What did you expect to be able to do that you could not? (open)
Usability and interaction
How easy is [product] to use day to day?
How often do you make mistakes or need to undo something? (Never to Very often)
Which part of [product] feels slow? (open)
How consistent does the product feel from one screen to the next?
Have you ever needed help from someone else to use [product]? (Yes / No)
How well does [product] work on your phone? (Very poorly to Very well, plus I do not use it on a phone)
Visual design and content
How would you describe the look of [product] in three words? (open)
How easy is the text to read?
Was any information missing when you made your decision? (open)
How clear were error messages when something went wrong?
How trustworthy does [site] look? (Not at all to Very)
Accessibility
Do you use any assistive technology, such as a screen reader or magnification? (Yes / No / Prefer not to say)
Did you have any difficulty using [product] with your device or settings? (open)
Is there anything about [product] that makes it harder for you to use than it should be? (open)
Feature feedback
How useful is [feature] for your work? (Not at all useful to Extremely useful)
How often do you expect to use [feature]? (Daily / Weekly / Rarely / Never)
What were you hoping [feature] would do? (open)
If you could change one thing about [feature], what would it be? (open)
Overall experience
How satisfied are you with your experience of [product] overall?
How would you feel if you could no longer use [product]? (Very / Somewhat / Not disappointed)
How likely are you to recommend [product] to a friend or colleague? (0-10)
What is the one thing we should improve first? (open)
May we contact you for a 20-minute research session? (Yes / No)
Is there anything else you would like to tell us? (open)
The System Usability Scale: questions and scoring
The System Usability Scale is the most widely used standardized usability questionnaire. MeasuringU describes it as a 10-item questionnaire with five response options, released by John Brooke in 1986. Respondents rate each statement from Strongly disagree to Strongly agree:
I think that I would like to use this system frequently.
I found the system unnecessarily complex.
I thought the system was easy to use.
I think that I would need the support of a technical person to be able to use this system.
I found the various functions in this system were well integrated.
I thought there was too much inconsistency in this system.
I would imagine that most people would learn to use this system very quickly.
I found the system very cumbersome to use.
I felt very confident using the system.
I needed to learn a lot of things before I could get going with this system.
Scoring: for odd items, subtract 1 from the response; for even items, subtract the response from 5. Add the ten converted values and multiply by 2.5 to get a score from 0 to 100. According to MeasuringU's analysis of 500 studies, the average SUS score is 68, so anything above 68 is above average. A SUS score is not a percentage: 68 is roughly the 50th percentile.
Keep the original wording and the alternating positive and negative items if you want to compare with published benchmarks. Replacing "system" with your product name is a common and generally accepted change.
The Single Ease Question
For a single task, ask one question right after it. Nielsen Norman Group describes the SEQ as asking users to rate the difficulty of the task they just completed on a 7-point scale from Very difficult to Very easy, and calls it reliable, valid and sensitive. Ask "Why?" after any score of 4 or below, and you have most of the value of a short usability test at a fraction of the cost.
How to run a UX survey that informs design
Write one research question first
"Why do users abandon setup at step 3?" produces a focused survey. "What do users think of the app?" produces a long one. Every question in the survey should help answer the research question.
Intercept at the moment, not days later
Trigger task questions immediately after the action: after checkout, after export, after a failed search. Memory of an interface fades fast; a question a week later measures general impression, not the task.
Avoid leading and hypothetical questions
"How much do you like the new dashboard?" assumes they like it. Ask "How would you rate the new dashboard?"
"Would you use a feature that does X?" invites polite yes answers. Ask what they did last time they needed X.
Do not ask users to design the solution; ask about the problem and observe the behavior.
Our survey bias guide covers more wording traps, and closed-ended questions explains when fixed answer lists help.
Segment by experience level
New users and power users experience the same interface very differently. Always ask how long and how often someone has used the product, and report results for each group separately.
UX surveys vs usability tests vs interviews
Method | Best at | Weak at | Sample |
|---|---|---|---|
UX survey | How many users hit a problem, and how they rate ease | Why it happens, unless open answers are probed | Dozens to thousands |
Usability test | Observing exactly where people struggle | How common a problem is | 5-10 per round |
User interview | Motivations, context, mental models | Measuring frequency | 5-15 per segment |
Analytics | What users actually do, at scale | Why they do it | All users |
A practical sequence: analytics shows where users drop, a short UX survey at that point asks what happened, and five usability sessions show exactly how. For more on mixing methods, see qualitative vs quantitative research.
Get the why behind every UX score with SmartInterview
SmartInterview runs UX surveys by voice or text. When a user rates a task as difficult and writes "confusing", the AI asks what exactly was confusing, in the user's own language, before moving on. Open answers are coded into themes automatically, so a UX survey with hundreds of responses gives you the reasons behind the scores, not just the scores.
Start free and launch your first UX survey.
Frequently Asked Questions
What are good UX survey questions?
Good UX survey questions ask about a specific task or moment: "What did you come here to do?", "Were you able to complete it?", "How difficult or easy was this task?" and "What would have made it easier?". Combine one rating with one open question for the reason.
What is the System Usability Scale?
The System Usability Scale (SUS) is a 10-item questionnaire with five response options that produces a usability score from 0 to 100. It was released by John Brooke in 1986. According to MeasuringU, the average SUS score across 500 studies is 68.
What is a good SUS score?
A SUS score above 68 is above average, based on MeasuringU's analysis of 500 studies. MeasuringU places a score above 80.3 in the top 10%, roughly an A grade, and scores below 51 in the bottom 15%. Remember that SUS is not a percentage.
How many questions should a UX survey have?
One or two for an in-app or on-site intercept, three to five for onboarding and feature feedback, and ten to fifteen for a survey sent to opted-in users. A post-task question should be a single item such as the SEQ.
What is the difference between a UX survey and a usability test?
A UX survey asks many users to report their experience, which tells you how common a problem is. A usability test observes a few users completing tasks, which shows exactly where and why they struggle. Most teams use surveys to find problems and tests to understand them.
When should you send a UX survey?
Send task questions immediately after the task, in the product, while the experience is fresh. Send broader UX surveys after onboarding, after a major release, or on a regular schedule such as every quarter, so you can compare scores over time.


