The UX research process is the sequence a team follows to learn who its users are, what they struggle with, and why, and then turn that learning into product decisions. At WANDR it runs in seven steps: frame the decision, review what you already have, choose methods and recruit, write the interview guide, run the sessions, turn findings into insights, then share, decide, and test again.

We learned how much this matters on a gaming project. The client had designed its product for casual gamers. After the interviews, we realized the people who would actually use it were professional gamers, with completely different behaviors, needs, and expectations. The research shifted the direction of the whole product. No amount of polish on the casual version would have fixed that.

This guide covers the steps, phases, methods, and timelines of UX research, based on how we have run it for 500+ clients in the last 10+ years.

What is UX research?

UX research is the work of understanding the challenges and needs of the people who will use your product: what problems they face, how they solve them today, and where your product helps or gets in the way. It combines qualitative methods, like interviews and usability tests, with quantitative data, like analytics and surveys.

The point is simple. Without research, you design on assumptions. With it, you design around real problems that real people told you about or showed you. Our rule is that we don't ask users what they prefer. We watch what they do, because what people say and what they do often disagree.

That is also why strong teams mix data types. Qualitative research explains why people behave the way they do. Quantitative research tells you how many people do it and how often. Steve Harrison, Product Lead at WANDR, says the two should stay in constant tension, so neither one drives decisions alone.

What are the steps of the UX research process?

The UX research process has seven steps: frame the decision and your hypotheses, review existing data, choose methods and recruit participants, write the interview guide or test script, run the sessions, cluster findings into insights, then share, decide, and test again. The last step feeds the next round, which is why teams call it the UX research cycle.

Here is the UX research process diagram we use, written as a list you can paste into a project plan:

  1. Frame: Agree on the decisions research must inform, and turn the team's assumptions into hypotheses.
  2. Review: Go through the analytics, recordings, support data, and past research you already have.
  3. Choose and recruit: Pick the method that fits the product stage, then screen for the right participants.
  4. Write the guide: Draft the interview guide or usability test script around the research objectives.
  5. Run sessions: Interview and test with real users, with notes and recordings.
  6. Synthesize: Cluster what you heard and saw, then write insights that explain why problems exist.
  7. Share, decide, repeat: Walk the team through the evidence, agree on changes, and test again.

1. Frame the decision and your hypotheses

Start with the decision, not the method. We never go into research blind. Every engagement opens with a Design Thinking Workshop, where empathy maps (what users think, do, feel, and say) turn the team's assumptions into hypotheses we can test. Clients usually arrive with a clear idea of what they want to build, so part of the research process is challenging those assumptions, as Paula Lopez, our Head of Product, puts it.

Personas get the same treatment. Jinny Oh, Founder of WANDR, tells our researchers to push back on the target audience a client hands them: "Is that really your target persona? What's going to bring the greatest revenue for your business?" The persona that sounds right is not always the one spending money on the platform.

2. Review what you already have

A lot of companies tell us they already have research. When we look at it, it often doesn't reveal the core of the problem. It is still the cheapest place to start. Analytics, recordings, support tickets, and churn reasons tell you where to look before you talk to anyone. On our MedTrainer project, Fullstory showed dead clicks on items users expected to be links, which pointed the interviews at the navigation.

3. Choose methods by product stage, then recruit

Which method comes first depends on the stage of the product. If the client only has an idea, we interview people who fit the target user profile to learn their challenges, workarounds, and pain points. If the product already exists, we test it with real users to see what confuses them, what breaks, and whether it meets their expectations.

Recruiting starts with a screener that defines who qualifies: age, profession, industry, and anything else the project needs. Our rules of thumb are 1 to 3 personas, 3 to 5 interviews per persona, and 3 to 5 testers per usability round. That lines up with Nielsen Norman Group's finding that testing with 5 users finds about 85% of usability problems, after which you fix the issues and test again.

Finding those people does not need a big budget. LinkedIn works for specific job titles. Facebook groups work when you need people by interest rather than role. Either way, explain who you are and why their input matters before you ask.

4. Write the interview guide or test script

This step decides the quality of everything after it. As Claudia Mérigo, UX Researcher at WANDR, explains: "Preparing the interview questions is one of the most important parts of the entire research process. If we ask the right questions, we'll receive the right answers." We build the guide with the client so every question maps to a research objective. Keep questions open and ask about what people did last time, not what they might do.

5. Run the sessions

Run moderated sessions live, record them with permission, and have a second person take notes with timestamps so the moderator can focus on the participant. In usability tests, give people real tasks and stay quiet while they work. The moment someone hesitates or clicks the wrong thing is the data you came for.

6. Cluster the findings, then write insights

After the sessions, we sort everything on digital boards into challenges, needs, pain points, and opportunities. We cluster first and hold back conclusions. Then we write insights. An insight summarizes a main problem users experience and explains why it exists. It does not jump to a solution, but it points to the direction a solution should take. Every insight links back to the sessions it came from.

7. Share, decide, and test again

Research only matters if it changes what gets built. We present findings in a live readout with product, design, and engineering, not a 60-page report nobody reads. We show the evidence behind each insight and stay involved as new questions come up during design.

Then test again. Steve Harrison compares shipping without going back to users to a director who only discovers in the cutting room that a scene isn't working. Wireframes do not tell the full story, so each round of testing feeds the next set of questions. Products are never done, and neither is the research.

What are the stages of UX research in product development?

The stages of UX research follow the product lifecycle: discover, explore, test, and listen. Discovery finds the right problem, exploration shapes the solution, testing checks that the design works, and listening tracks real use after launch. Each stage answers a different question, so each one calls for different research methods.

Nielsen Norman Group's UX research cheat sheet organizes methods into these four phases, and its guide on when to use which UX research methods maps them to generative, formative, and summative goals. In our own projects, the same ground is covered by the four phases of the WANDR process: Discovery and Research, Strategy, Execution, and Feedback.

Discover: find the right problem

  • Stakeholder interviews to align on goals, constraints, and what success looks like.
  • User interviews to understand workflows, pain points, and workarounds.
  • UX audit of the current product or site to find known issues fast.

Explore: shape the solution

  • Personas and journey maps to show where users drop off or lose trust.
  • Card sorting to learn how users group information, which shapes navigation.
  • Competitive analysis to see where others solve the problem well or badly.

Test: check that the design works

  • Clickable prototype testing before any code is written.
  • Moderated usability testing to watch users attempt real tasks.
  • Five-second tests to check that people understand what you offer at a glance.

Listen: learn from real use

  • Product analytics and session recordings to find where users stall.
  • Surveys and in-app feedback to spot trends.
  • Support ticket review to surface recurring friction.

How long does the UX research process take?

In our experience, a proper UX research study takes about one month at minimum, and a larger study with more than 20 participants can easily take two months. Recruiting is usually the slowest part. People cancel or miss sessions, and specialized participants like CEOs and CTOs have very full calendars.

Audience changes the math. Claudia points out that gamers are the opposite of executives: they love talking about gaming, and the hard part is ending the conversation. Inside a full redesign, research runs alongside other work. On our WWF-Canada project, the research and audit phase ran across months 1 and 2, before design began.

How do you prioritize UX research with a limited budget?

Prioritize UX research by risk. Study the decisions that are most expensive to get wrong and least supported by evidence, such as a new product direction, onboarding, or a key conversion flow. Reuse the data you already have, run small rounds of 3 to 5 users, and test prototypes before anything gets built.

Some research always beats none. When a client says they only have budget for two weeks, Marlind Tako, Product Designer at WANDR, says: "We would make the most out of it, but it's still much better than not having it at all." Skipping it entirely tends to cost more later. In Claudia's words: "Many companies that skip research eventually come back to conduct user research anyway because the product doesn't perform as expected."

A practical order for small budgets:

  1. Rank your open questions. Score each by how costly a wrong answer would be and how little you know. Research the top two or three.
  2. Run small rounds. A few interviews or tests per round, fix what you find, then test again.
  3. Test before you build. A clickable prototype is far cheaper to change than shipped code. We have seen clients spend millions building apps that didn't work once they reached users.
  4. Start with an audit. An expert UX audit catches known usability issues quickly, so user sessions focus on what only users can tell you.

How is AI changing UX research in 2027?

AI now handles much of the mechanical work in UX research, such as transcription, tagging, and first-pass analysis, while people still own study design, moderation, and interpretation. Most research teams already use AI tools. The open question is quality: AI-generated "synthetic users" can help you prepare for research but cannot replace real participants.

Our take: use AI to speed up transcripts, tagging, and first drafts of screeners and guides. Keep people in charge of recruiting, moderating, and deciding what a finding means. The casual-versus-professional gamer split would not have come from a synthetic user. It came from listening to real ones.

How does WANDR approach UX research?

At WANDR, research comes before design decisions, not after. We frame every study around the decisions a team needs to make, combine existing data with interviews and moderated testing, and validate designs across two rounds of user testing. The same team then turns the insights into structure, flows, and designs.

Our research service runs in five steps:

  1. Research framing and alignment: business goals, research questions, hypotheses, and success criteria.
  2. Secondary research and data review: analytics, prior research, customer feedback, and market context.
  3. User recruitment and test design: screening, scheduling, incentives, and a structured test script.
  4. Moderated usability testing: live sessions documented with notes, recordings, and timestamps.
  5. Insights, analytics, and reporting: patterns ranked by impact and frequency, with clear recommendations and a stakeholder readout.

Three examples of where that led:

  • Zoe Financial: Research showed prospects dropped out when onboarding asked for financial details before earning their trust. We resequenced the flow so value came before the ask and validated it across two rounds of user testing. Self-scheduling conversion rose 175%, from 8% to 22%. Read the case study.
  • MedTrainer: Two exploratory and three validation interviews, plus a Google Analytics, competitor, and Fullstory review, showed where the old site lost buyers. Card sorting shaped a new information architecture, and the MedTrainer redesign lifted inbound leads 23% in the first month.
  • WWF-Canada: We started with an analytics baseline and a UX audit against nine user groups to find where the donation funnel was leaking. The redesign lifted digital donations 37%.

You can see the full scope on our user research and usability testing services page.

Make your next product decision with evidence

A good UX research process does not need to be big. It needs clear questions, the right participants, and a direct line from insights to decisions. If you are planning a new product, a redesign, or a fix for a flow that is not converting, book a call with our team. We will tell you which research is worth doing first, and we will tell you if it isn't needed at all.