Skip to content
ResearchUX lexicon

What are surveys in UX?

Surveys in UX are structured sets of questions sent to many users at once to gather opinions, behaviors and satisfaction data you can count and compare.

also calledquestionnaires · user surveys · UX questionnaires

A survey is the cheapest way to hear from a lot of people at once, and the easiest to get wrong. Done well, it tells you how many of your users share a problem. Done badly, it produces confident-looking numbers built on questions nobody understood.

In short
  • Surveys count how many people share an opinion or behavior, but cannot reveal problems you did not think to ask about.
  • Neutral, single-topic questions in plain language matter more than clever design.
  • Keep them short and test the draft on a few people first.
  • Decide what decision the results will inform before you write any questions.
01

What surveys are good for

Surveys shine when you already have an idea of what to ask and need to know how common it is. How many of our customers use the mobile app weekly? Which of these five problems matters most to them? How satisfied were they with checkout?

They are less suited to discovering problems you have not thought of. A closed question can only return the answers you offered. If you do not know what people struggle with, run interviews first and use a survey to check how widespread those struggles are.

Surveys also cannot show you what people actually do. They record what people say they do, which is related but not the same.

02

Types of questions

The format of the question decides what you can learn from it.

  • Multiple choice and rating scales give you numbers that are easy to compare.
  • Ranking questions show relative priority, though they get tiring beyond five or six items.
  • Open text lets people use their own words, which is valuable for discovering things you missed.
  • Standard instruments, such as the System Usability Scale or Net Promoter Score, give you a benchmark you can track over time.

A good survey mixes a few closed questions with one or two open ones, and stays short.

03

Writing questions people can answer

Most survey problems are wording problems. Avoid leading questions such as how much did you enjoy our easy new checkout? Avoid double-barreled ones that ask two things at once, like was the site fast and attractive?

Use plain language, not your team's internal jargon. If people have to wonder what a word means, they either guess or leave.

Ratings need clear labels at each end, and answer options should cover every realistic response, including a way to say not applicable.

Before sending, test the survey on three or four people and watch where they hesitate. This cheap step catches the majority of problems.

04

Getting responses worth trusting

Who answers matters as much as what they answer. People who reply tend to be unusually happy or unusually annoyed, so the quiet middle is underrepresented. Keep this in mind when you read the results.

Keep it short: every extra question costs you completions. A survey that takes three minutes will get more honest answers than one that takes fifteen.

Time it well, too. Asking about checkout right after checkout produces better memories than asking a week later.

When you read results, be cautious about small differences. A satisfaction score moving from 4.1 to 4.2 across a few dozen responses is likely noise.

05

Common mistakes

The usual offenders are surveys that are too long, questions that nudge toward an answer, and asking people to predict their own future behavior. Another is collecting data with no plan to act on it.

Before writing question one, write down the decision the results will inform. If you cannot, you probably do not need the survey yet.

Common questions

Surveys: your questions, answered

What are surveys in UX research?

They are sets of structured questions sent to many users to collect opinions, behaviors and satisfaction ratings in a form you can count. Teams use them to measure how common a need or problem is across their audience.

When should you use a survey in UX?

Use a survey when you already know what to ask and need to quantify it, such as measuring satisfaction, ranking priorities or sizing a problem you found in interviews. They are a poor tool for discovering unknown problems.

How long should a UX survey be?

As short as it can be while answering your research question. Most surveys work best at five to ten questions and under five minutes. Every extra question increases the chance people abandon it or rush their answers.

What is a good sample size for a survey?

It depends on how precise you need to be and how varied your audience is. For rough direction, a few hundred responses may be enough, while detailed comparisons between groups need more. Representativeness matters more than raw numbers.

What are common survey mistakes?

Frequent errors include leading questions, asking two things at once, using jargon, offering incomplete answer options, making the survey too long, and surveying only people who are easy to reach instead of your real audience.

People also ask

More quick answers

Is a survey qualitative or quantitative?

Mostly quantitative, because closed questions produce numbers. Open-ended questions add a qualitative layer.

What is the System Usability Scale?

It is a ten-question standardized questionnaire that produces a single usability score, useful for comparing versions of a product over time.

What is Net Promoter Score?

It asks how likely someone is to recommend a product on a zero to ten scale and groups answers into promoters, passives and detractors. It measures loyalty, not usability.

Which tools can I use to run a survey?

Many online survey platforms and form builders work. Choose one that supports your question types, mobile screens and exporting results.

How do surveys differ from interviews?

Surveys reach many people with fixed questions, while interviews go deep with a few people and let you follow up on surprises.

Keep reading
Free and open source

Found this useful? A GitHub star helps other designers find it.

Star on GitHub