Subjects and lessons to explore.

Law

UX/UI Design · Foundations

User Research

9 min read 5 practice questions
10 key termsSourcesReport an error
Want it in plain words first? Jump to Eli explains — the same idea, no jargon.
On this page 9 sections
  1. In 30 seconds
  2. Why this matters
  3. The college version
  4. Eli explains
  5. Worked example
  6. Key takeaway
  7. Quick check
  8. Study tools
  9. Sources & references

In 30 seconds

is the systematic gathering of information about the people you design for: their needs, behaviors, and motivations. It comes before design, because building without it means guessing what users want. Common methods include interviews, surveys, , , and . gives deep insight from a few people; finds patterns across many. Research runs throughout the design process, and it reduces risk without ever removing it entirely.

Why this matters

Every design decision is a bet on what people will do. Research replaces part of that guesswork with evidence about who the users are, what they need, and how they behave. Without it, teams argue from opinion, build features nobody asked for, and discover problems only after launch. With it, teams focus effort where it matters, catch problems while changes are still cheap, and defend choices with data instead of taste. Research is the difference between solving a real problem and solving the problem the team imagined. It does not guarantee success, but it is the most reliable way to raise the odds.

The college version

What user research is

User research is the systematic gathering of information about the people you design for. The classic working definition, from the U.S. government's Usability.gov, is that user research focuses on understanding user behaviors, needs, and motivations through observation techniques, task analysis, and other feedback methodologies. The Interaction Design Foundation offers a similar definition: the methodical study of target users, including their needs and pain points, so that designers have the sharpest possible insights. Two details matter here. First, the word systematic: research is planned, recorded, and analyzed, not a casual chat with whoever happens to be nearby. Second, the object: the goal is information about real people, what they need, what they do, and why they do it, rather than the product team's own preferences. That information, gathered before and during design, is what turns product decisions from guesses into educated choices.

Why research comes first

Designing without research is guessing. The guess may be an educated one, but it is still a guess, and the cost of a wrong guess shows up late. Consider a small team building an app that lets moviegoers reserve seats at a neighborhood cinema. The team's founder is convinced that users want a social feed for sharing which films they plan to see, so the team spends two months building one. Only after a soft launch do they learn the truth: Friday-night customers mostly want to know, in one glance, whether seats remain before they drive across town. Interviews with eight regulars, or a short , would have surfaced that need in days. This is why serious design processes put research before building. Nielsen Norman Group notes that nearly all projects benefit from multiple research methods and from combining insights, and that insight belongs in front of the first design decision, not after it.

The main methods, briefly

The main methods form a small toolkit, and each one answers a different kind of question. Interviews are one-on-one conversations that go deep into a few people's experiences and motivations. Surveys send structured questions to many people to collect comparable answers. Observation, sometimes called a field study, means watching people do real tasks in their real environment, where what people do often differs from what they say. Usability testing means watching people try to use a design so the team can see where it is easy or hard to use. Analytics are the usage numbers a live product collects automatically, such as page views, clicks, and completion rates. Each of these methods is a full topic of its own; here, the point is that they are complementary. Teams get the sharpest picture when they combine a few of them rather than leaning on a single favorite.

Qualitative versus quantitative

Research methods split into two broad families. Qualitative research gathers deep, non-numerical insight from a small number of people. Interviews and observation are the classic examples: they answer why questions, such as why users abandon a checkout or why they trust one page and not another, because a researcher can watch, listen, and follow up. Quantitative research gathers measurable data from many people. Surveys and analytics are the classic examples: they answer how many and how often questions, and they can reveal patterns across a whole population, such as which step in a flow loses the most users. Nielsen Norman Group describes qualitative data as findings gathered directly by observing or hearing people, and quantitative data as measurements collected indirectly through instruments such as surveys or analytics tools. The two are partners: qualitative research finds the problems worth caring about, and quantitative research checks how widespread they really are.

Research runs through the whole process

A common beginner assumption is that research happens once, at the start. In practice, the questions change as a project moves, and the practice continues the whole way. Early research is generative: it looks for new directions and opportunities, often before a design exists. Mid-project research is formative: it helps improve a design while changes are still cheap. After launch, research is summative: it measures how the product performs against earlier versions or competitors, using data such as analytics and follow-up testing. Nielsen Norman Group maps methods onto exactly these stages of product development, and the Interaction Design Foundation makes the same point: user research can be applied at any point in the design process. The honest note is that research is a habit, not an event.

Bias, and the honest limits of research

Research is only as good as the care taken to keep it honest. A is one whose wording suggests the answer the researcher wants, such as asking whether a bigger payment button would be easier; people will often agree with it, which makes the answer worthless. is the tendency to notice and favor evidence that supports what you already believe, which is exactly why teams that research after deciding tend to find what they were looking for. Bias can enter through the researcher, through participants, and through the method itself, so the fix is continuous: neutral questions, honest analysis, and a willingness to be surprised. And the honest framing must be stated plainly: research reduces risk; it does not eliminate it. It tells you what people need and how they behave, but it cannot guarantee that a product will succeed. There is no research that removes the need for judgment.

Eli, the EliExplains learning guide

Eli explains

The same idea, in plain words

Explain it like I’m 10

User research is the practice of finding out who your users are and what they truly need before you build, instead of guessing. You gather facts about people's needs, behaviors, and motivations through methods like interviews, surveys, observation, usability testing, and analytics. Talking with a few people gives deep insight; asking many people reveals patterns; and watching what people actually do often tells a different story than what they say. Research is not a single event at the start of a project. It continues as the design takes shape, and it keeps going after launch.

Picture it like this

Planning a group hike is a good picture. You would not set out without checking the trail conditions and asking the group how far they can walk. You study the map, talk with a few hikers about their experience, and take a short test stretch. During the hike you keep watching the group: who is slowing down, where the trail becomes confusing. The planning does not guarantee a perfect hike, because a storm can still arrive, but it makes surprises far less likely.

Where the picture stops working

The analogy has limits. A trail is fixed, while a product keeps changing as you design it, so research questions shift along with it. Hikers can usually tell you what they need, while users often cannot fully explain their own behavior, which is why watching people matters. And checking conditions reduces risk but never removes it, just as user research can never prove that a design will succeed.

Worked example

A small team wants to build an app that helps people reserve seats at a neighborhood cinema. Instead of designing from guesses, they first interview eight regular moviegoers about how they choose a showtime. They learn that Friday-night customers mainly want to know, quickly, whether seats are still available before driving over. The team then watches three people try to buy a ticket on the cinema's current website and sees all three give up at the payment step. A survey sent to the cinema's mailing list confirms that checking availability quickly outranks sharing what you plan to see. With that evidence, the team designs the app around a one-screen availability check. The research did not guarantee success, but it stopped the team from building a social feed nobody asked for.

Key takeaway

User research gathers evidence about users' needs, behaviors, and motivations so that design decisions stop being guesses. It runs throughout the process, it reduces risk, and it never removes risk entirely.

Quick check

3 questions here, of 5 in this lesson’s practice set. Answers stay hidden until you check.

Question 1 of 3foundational

What is user research, in its most basic sense?

Choose an answer, then check it.
Question 2 of 3intermediate

A team spends two months building a social feed for a cinema app because the founder assumes users will enjoy sharing what they watch. What is the main problem with this approach?

Choose an answer, then check it.
Question 3 of 3advanced

Which pair correctly matches a research method with the kind of question it answers best?

Choose an answer, then check it.
Practice all 5

Keep learning

Ready to build on this? Continue to the next lesson.

Practice this lesson
Study tools & related lessonsYou’ll learn to · Common mistakes · Easily confused · Key vocabulary · Related

You’ll learn to

  • Define user research as the systematic gathering of information about users' needs, behaviors, and motivations.
  • Explain why research should come before design, using an example of the cost of designing from guesses.
  • Name the main user-research methods and the kind of question each one answers.
  • Distinguish qualitative research, which gives deep insight from a few people, from quantitative research, which finds patterns across many.
  • Recognize that research happens at every stage of a design process, not only at the start.
  • Identify common research biases and describe what research can and cannot guarantee.

Common mistakes

  • Designing the product first and treating research as a confirmation step afterward.

    Run research before committing to a direction, so the evidence shapes the design instead of defending it.

  • Asking leading questions that suggest the expected answer, such as asking whether a bigger button would be easier.

    Ask neutral, open questions that let people describe their own experience without being steered.

  • Treating a few interviews as proof about the whole user population.

    Qualitative findings from a handful of people show depth, not frequency; use quantitative methods to check how widespread a pattern is.

  • Relying on a single favorite method for every question.

    Combine methods, because each one answers a different kind of question and together they reduce blind spots.

  • Believing that research done at the start means research is finished.

    Keep checking with users as the design changes, and use analytics and testing after launch.

Easily confused

Qualitative vs. Quantitative research

Deep insight from a few people vs. measurable patterns from many.

Attitudinal vs. Behavioral research

What people say vs. what people do, which often differ.

Generative research vs. Formative vs. summative research

Generative research finds opportunities before design; formative research improves the design during it; summative research measures performance after it ships.

Research that shapes decisions vs. Research that defends them

Evidence gathered before deciding vs. evidence collected to justify a choice already made.

Key vocabulary

User research
The systematic gathering of information about the needs, behaviors, and motivations of the people a product is designed for.
Qualitative research
Research that gathers deep, non-numerical insight from a small number of people through methods such as interviews and observation.
Quantitative research
Research that gathers measurable, numerical data from many people in order to find patterns and test assumptions.
Interview
A one-on-one conversation in which a researcher asks a user questions to understand their experience and motivations.
Survey
A structured set of questions sent to many people to collect comparable, self-reported answers.
Observation
Watching people perform real tasks in their real environment rather than asking them to describe what they do.
Usability testing
Watching people try to use a design to complete tasks, in order to find where it is easy or hard to use.
Analytics
Usage data collected automatically from a live product, such as page views, clicks, and task-completion rates.
Leading question
A question whose wording suggests or implies the answer the researcher hopes to hear, which makes the reply unreliable.
Confirmation bias
The tendency to notice and favor information that supports what you already believe, while ignoring what contradicts it.

Sources & references

  1. When to Use Which User-Experience Research Methods — Nielsen Norman Group (NN/g)
  2. Quantitative vs. Qualitative Usability Testing — Nielsen Norman Group (NN/g)
  3. Leading Questions in User Research — Nielsen Norman Group (NN/g)
  4. What is User Research? — Interaction Design Foundation (IxDF)
  5. User Research Basics — Usability.gov (U.S. General Services Administration; site archived)

EliExplains lessons are original prose written from the open, credible references above. See Copyright & Licensing.

Researched 2026-08-21

Educational content only. It is not medical, legal or professional advice. Found an error? Tell us.