top of page

How to Run User Research for Product Design

Oct 30
9 min read

Last Updated: October 30, 2026

Quick Summary

User research is the process of learning how people think, behave, and struggle with a product or problem before you commit to a design. Running it early helps you avoid building something nobody wants to use. Start by naming the decision the research must inform, then choose a method that fits your stage and budget.

  • Write the decision you need to make as a question before choosing a method.

  • Match the method to your stage: interviews early, prototype tests in refinement.

  • Recruit people who match your target user, not whoever is easiest to find.

  • Five to eight participants per user group often surface the main patterns.

  • Ask people to show you how they do a task rather than describe it.

Table of Contents

Running user research before you design a physical product keeps you from building something nobody wants to use. Many product teams skip this step because it feels slow. In practice, a few focused conversations with real users can prevent expensive redesigns later. This guide from 2B Studio walks through how to plan, run, and act on user research for product design, with practical steps you can use on your next project.

What User Research Is and Why It Shapes Product Decisions

User research is the process of learning how people think, behave, and struggle with a product or problem before you commit to a design.

Research shapes decisions at every stage. Early on, it helps you choose which problem to solve.

  • Confirms the problem is real and worth solving

  • Reveals how users really handle the product, not how they say they do

  • Shows which features matter most and which ones to cut

Skipping research often means designing for assumptions. For the broader framework behind user-centered decisions, see the design thinking process step by step.

Matching Research Methods to Your Decision, Stage, and Budget

No single research method fits every project. The right choice depends on three things: the decision you need to make, where you are in development, and how much time and effort you can spend.

Start by writing the decision as a question. "Which handle shape should we prototype first?" points to a different method than "Do users understand how to assemble this?" Once the decision is clear, the method usually follows.

A decision-first method matrix

Use this matrix to compare methods by what they answer, the stage they fit, relative effort, and sample needs. Effort and sample figures are typical ranges most practitioners use, not fixed rules.

Method

Best for answering

Product stage

Relative effort

Typical sample

User interviews

Needs, context, goals, pain points

Discovery

Low to medium

5-8 per user group

Contextual observation

How work is really done in the real setting

Discovery

Medium

3-6 sessions

Surveys

How widespread a pattern is across many users

Discovery to validation

Medium

30+ for patterns

Usability testing

Whether users can complete tasks with a prototype

Concept to refinement

Medium

5-8 per round

Formative prototype tests

Grip, balance, fit, and ergonomics

Concept to refinement

Medium to high

5-10 per round

Summative testing

Whether a design meets a measurable target

Validation

High

15+ per group

Diary studies

How use changes over days or weeks

Discovery to validation

High

8-15 participants

Match the method to the stage

Early-stage questions usually call for interviews and observation. You are trying to understand the problem before you commit to a solution. Mid-stage questions, like whether a grip feels comfortable or a latch is intuitive, need hands-on testing with prototypes. Late-stage questions, like whether a design meets a measurable target, call for more structured testing with larger samples.

  • Discovery: Interviews, observation, and diary studies to understand needs and context.

  • Concept: Formative prototype tests and quick usability checks to compare directions.

  • Refinement: Repeated usability and ergonomic tests to fix specific problems.

Budget and timeline tradeoffs

A small team with a tight budget can get far with five to eight interviews and a handful of prototype tests. Match the depth of research to the risk of the decision. A low-risk choice about button placement may need one quick round. A high-risk choice about a load-bearing mechanism or a safety feature deserves more participants and more rounds.

When time is short, narrow the question rather than skip the research. One focused round on the single riskiest assumption beats a broad study that answers nothing in time to matter.

Pro Tip If you cannot name the decision the research will inform, the study probably is not worth running yet. Write the decision first, then pick the method.

Qualitative and quantitative together

Qualitative methods like interviews and observation tell you why and how. Quantitative methods like surveys and summative tests tell you how many and how much. Most physical product teams start qualitative to find the problems, then use quantitative work to confirm which problems matter most before committing to tooling.

Step 1: Write a User Research Plan Template for Your Project

A written plan keeps research focused and gives your team a shared reference. Keep it to one page so people will actually read it.

Use this template:

Project: [Product name] Decision we need to make: [e.g., Which handle shape to prototype first] Research question: [What we need to learn] Method: [Interview, observation, usability test, or survey] Participants: [Who, how many, and how we will recruit them] Timeline: [Start date, end date, and owner] Success signal: [What result would change or confirm our direction] Budget: [Hours, materials, and incentives]

Fill in every field before you contact anyone. If you cannot name the decision the research will inform, the study probably is not worth running yet.

Step 2: Recruit Participants and Set Sample Size

Recruit people who match your target user, not whoever is easiest to find. A product for home cooks needs home cooks, not colleagues who work in the kitchen industry. The quality of your findings depends heavily on who is in the room.

Write screening criteria before you recruit

Define the profile in writing before you contact anyone. Good screening criteria describe behavior and context, not just demographics.

  • What the person currently uses to solve the problem

  • How often they do the task

  • What tools, spaces, or constraints they work within

Ask a few short questions to confirm each person fits the profile. Screen out people who are too close to the product team, work in the industry, or have already seen the concept, because they tend to give polite rather than accurate feedback.

Set sample size by the decision, not a fixed number

For qualitative work, small samples often reveal most of the major problems. Many teams stop after about five participants per user group, then run another round if new issues keep appearing.

  • Narrow, similar user group: five to eight participants often surface the main patterns.

  • Varied users or use cases: plan for more participants or separate rounds per group.

  • High-risk or safety-related decisions: use larger samples and more structured testing.

A common pattern is to run a small round, review whether new issues are still appearing, and add a second round only if they are. This keeps effort matched to the risk.

Recruit inclusively and accessibly

Representation matters for physical products because bodies, abilities, and contexts vary. Include users with a range of hand sizes, strengths, and accessibility needs when the product will be used by a broad audience. Plan sessions so people with disabilities can take part, and ask ahead about any accommodations they need.

  • Offer sessions in accessible spaces or remote options where the method allows.

  • Provide materials in readable formats and allow extra time.

  • Avoid scheduling that excludes people with caregiving or shift-work constraints.

Incentives and logistics

Offer a fair incentive for participants' time, and be clear about what the session involves before they agree. Plan a few extra participants in case someone cancels. Keep a record of who you spoke with and when so you can spot patterns across rounds and avoid repeating the same participant.

Watch Out Get consent before recording any session, and explain how notes, photos, and recordings will be stored and used. Protect participant privacy and remove identifying details from shared findings.

Keep recruitment ethical and organized

Treat participants with respect throughout. Explain the purpose, confirm they can stop at any time, and follow through on any promises about how their data will be handled. A simple recruitment tracker with name, profile fit, session date, and consent status keeps the process organized and auditable.

Step 3: Prepare User Interview Questions for Product Design

Good interview questions ask about past behavior and real situations.

Start broad, then narrow in. Ask people to show you how they do something rather than describe it.

  • "Walk me through the last time you did this task."

  • "What was the hardest part of that process?"

  • "What do you currently use to get it done?"

Avoid leading questions such as "Wouldn't a faster version be better?" Instead ask, "How do you feel about how long this takes?" Take notes or record sessions with consent, and keep the conversation relaxed.

Step 4: Run Usability Testing for Physical Products

Usability testing shows whether people can complete tasks with your prototype. Give participants a realistic task, then watch without helping.

Product designer conducting user research by observing a participant testing a handheld prototype at a workbench.

Set up the test near the environment where the product will be used. Use the prototype you plan to show, even if it is rough.

What to watch for:

  • Where people hesitate or stop

  • Which grips, angles, or motions feel awkward

  • What they ask for help with

Write down what people do, not only what they say. A user who says a handle feels fine but keeps shifting their grip is telling you something.

User Research Examples From Physical Product Projects

Examples help show how research changes a physical design. The examples below are illustrative rather than specific client results.

Consider a team designing a kitchen tool: interviews might reveal that the tool gets used one-handed while the other hand holds a pan, and that finding could shift the grip size and balance.

These examples share one lesson. The biggest design changes often come from small details that only appear when you watch real use.

Turning Findings Into Your Next Design Step With 2B Studio

Research only pays off when findings change the design. After each round, sort what you learned into three groups: problems to fix now, questions to test next, and ideas to park. Then decide the next action for each.

Our team at 2B Studio works with product teams to take research findings into design and prototyping. See how we approach design and manufacturability for physical products. If you have research results and need help deciding what to change, contact 2B Studio to talk through your project and next steps.

Frequently Asked Questions

What is user research in product design?

User research is the practice of learning how people think, behave, and struggle with a product or problem before and during design. In product design, it answers questions such as who the user is, what tasks they need to complete, and where current options fail them. Teams use interviews, observation, surveys, and usability testing to gather this evidence. The findings guide decisions about form, features, materials, and ergonomics so the product fits real use rather than assumptions made in the studio.

What are the main methods of user research?

The main methods fall into generative research, which explores needs early on, and evaluative research, which tests a design. Generative methods include user interviews, contextual inquiry, and field observation. Evaluative methods include usability testing with prototypes and structured surveys. Qualitative methods reveal why people act as they do, while quantitative methods measure how often something happens. Most product teams combine several methods, choosing based on the decision in front of them, the stage of development, and the time and budget available.

How many users should you interview for product research?

For early qualitative interviews, many teams plan for roughly five to eight participants per distinct user group, then keep recruiting until new sessions stop producing new insights. Usability testing of a physical prototype often uses a smaller number of participants per round, with several rounds of changes between sessions. Sample size depends on how varied your users are, how many user groups you serve, and what decision the research needs to support. Recruit participants who match your target users rather than whoever is easiest to reach.

When should user research happen in the product design process?

User research should start before design begins, when the team is still defining the problem and the user's needs. It continues through concept development, when sketches and models are tested, and again during detailed design and prototyping. Research is also valuable before production tooling is committed, because changes are far less expensive at that point. Teams that treat research as a single step at the beginning often discover problems late, when fixing them costs more in time and materials.

 
 
 

Comments


bottom of page