Looking for the Best UX Research Agency in 2025? Start Here
Explore UX research agencies 2025 with ANODA UX Design Agency. Compare services & book a free consultation to improve your product using real user insights.
- For new products and features
- Before design and development begin
- 3–6 weeks
- For an agreed scope
- Sessions with real users
- Patterns reported with counts
- A decision review
- What to build next, and why
In short
Evidence about your users before you decide what to build.
What's included
- A research plan
- Sessions with real users
- Findings with counts
- What they mean for the product
Helps you decide
- Which problem to solve first
- Who you are solving it for
- Which assumptions are safe to build on
Where it stops
Reviews the product you already have.
UX Research
Collects new evidence about people, with or without a product.
Not included
- What to build — that decision stays yours
- How common a behaviour is across the market
Findings your team can use to choose a direction.
A UX audit starts from the product you have and ranks what to fix first. UX research starts from a decision you face and finds out how people work, why, and what they need.
A research plan
The decision it serves, your questions, who takes part and the method.
Sessions with the right people
Interviews, observation in context or tests, chosen to fit the question.
Patterns, with counts
Each pattern, how many participants showed it, and anonymised quotes.
Why, and what people need
How people work, why, and what they need, including outside your interface.
Product implications
Which assumptions held, which did not, and the changes they point to.
A decision review
A working session on the decision, open questions and what to test next.
You receive the agreed evidence, synthesis and recommendations organised around your research questions, and we review what they mean with your team in a working session.
Discuss your productThe decision comes first, then the method.
Every study starts from the choice it must inform. The method follows the question, not the other way round.
Decisions research can support
- Which user problem is worth solving first
- Whether a new product or feature is needed at all
- Which workflow to redesign, and for whom
- What to test before committing to build
Questions, and the method for each
| Question | Method | Why this method |
|---|---|---|
| Why do people stop using a key workflow? | Interviews and workflow observation | The reasons sit in context the analytics cannot show. |
| Can people complete a task with the current design? | Moderated usability testing | Watching the task shows where it breaks, not just that it does. |
| What do users already tell you? | Review of support conversations and earlier research | Existing evidence is cheaper than a new study and sharpens its questions. |
Research with people
- User interviews
- Workflow observation
- Usability testing
What you already have
- Support conversations
- Earlier research
- Product analytics
- Internal knowledge
Recruitment
- Your users where reachable
- Screened participants when scoped
-
Frame the decision
Agree the choice the research must inform and what would change it.
-
Plan and recruit
Choose the method for each question and recruit the right participants.
-
Run the sessions
Interviews, observation or tests, with your team invited to watch.
-
Synthesise with counts
Patterns across sessions, how many people showed each, and what they need.
-
Turn it into a decision
Product implications and a review where the team decides what changes.
Limits and confidence. Qualitative research explains why and how, not how many. Every report says what the study does not establish, and where a finding rests on few sessions.
Bring a decision, an uncertainty and access to the right people.
-
A choice to make
You need to choose between plausible product or design directions.
-
Reachable users
You can help us reach relevant users or agree a recruitment approach.
-
Room to be wrong
Stakeholders are willing to reconsider assumptions when evidence changes.
-
Time before the decision
There is time to use the findings before a key decision becomes fixed.
Tell us what your product needs
Share where the product is and what has to change. We will come back with a useful scope and a realistic next step.
How the engagement works
What we need from your team, who does what, and what happens after the handoff.
What we need to start
- Decision
- The decision the study is meant to inform, and when it has to be made.
- Access
- A way to reach relevant users, or an agreed recruitment approach.
- Context
- Whatever you already know: support conversations, earlier research, product data.
- A point of contact
- Someone on your side who can answer questions between sessions.
Who does what
- ANODA
- writes the plan, runs the sessions, analyses the material and presents what it means.
- Your team
- helps reach participants, shares context and takes the findings into the decision.
After the study Research usually leads into design work or a strategy engagement; neither is part of this one. Usually 3–6 weeks for an agreed scope.
Let’s talk about your project
Tell us what you’re working on and where you need help.
Message received.
Within 15 minutes, we’ll email you initial feedback and follow-up questions.
UX Research Strategy
UX Research Strategy: practical guidance, examples and decision criteria from ANODA. Learn how the topic applies to your product and team.
UX Research: common questions
Which research method will you use?
That depends on the question. Interviews can help explain working context, observation reveals what happens during a task, and usability testing examines an experience directly. We may combine methods, but we do not prescribe a large study before understanding the decision.
Can you work with research we already have?
Yes. We review relevant existing material first. Sometimes it answers the question; sometimes it reveals a narrower gap. The goal is to make good use of what your team already knows and collect new evidence where it matters.
Who recruits participants?
We agree that during scoping. Your team may introduce existing users, or the study may need a separate recruitment approach. Participant suitability, availability, incentives and access affect the plan and are made explicit before work begins.
How many participants do we need?
There is no single number for every study. The method, diversity of roles and decision risk affect the sample. We propose a suitable approach and explain its limitations instead of treating a small qualitative study as a representative market survey.
Can you test a prototype before development?
Yes. We can test selected tasks in a prototype and examine where people misunderstand the flow or struggle to continue. The findings inform the next design iteration; they do not prove how the finished product will perform after launch.
What do we receive at the end?
You receive the agreed evidence, synthesis and recommendations organised around your research questions. We review the implications with your team and identify any remaining uncertainty. Recording, storage and access arrangements are agreed for the study.