Eleven newer UX research methods worth trying

Newer UX research methods include unmoderated remote testing, in-product micro-surveys, continuous discovery interviews, AI-assisted synthesis, session replay analysis, rapid concept testing, remote diary studies with mobile apps, prototype analytics, community panels, design sprints with user tests and behavioural data experiments. They make research faster and more continuous.

Why research methods are changing

For many years, user research meant scheduling a lab, recruiting participants weeks in advance and producing a long report at the end of a project. That model still has a place, but it is too slow for teams that ship every week or two. Remote tools, in-product feedback and AI-assisted analysis have made it possible to learn from users continuously, in smaller and faster steps, so that research keeps pace with development.

The newer methods described here do not replace classic techniques such as interviews and moderated usability tests. Instead, they fill the gaps between larger studies, giving teams a steady flow of evidence about how people use the product and what they need next.

The eleven methods

Unmoderated remote testing in practice

In an unmoderated test, participants complete tasks on their own device while software records their screen and voice. There is no facilitator in the session, so tests can run in parallel and results often arrive within a day. The method works best for clear, well-defined tasks, such as finding a product or completing a form, where the goal is to see whether people succeed and where they struggle.

• Write tasks that are specific but do not reveal the answer
• Include a short warm-up task so participants get used to thinking aloud
• Ask a follow-up question after each task about ease and confidence
• Review recordings yourself rather than relying only on summary metrics
• Use moderated sessions for complex or exploratory questions

In-product micro-surveys

Micro-surveys are one or two quick questions shown inside the product at a relevant moment, such as after completing a task or when someone hesitates on a page. Because they appear in context, the answers are more specific and reliable than those from a general survey sent days later. Keep them short, easy to dismiss and limited in frequency so they do not annoy users.

Session replay and behavioural data

Session replay tools record anonymised sessions so teams can watch how people move through the product: where they click, how far they scroll and where they hesitate or leave. Watching a handful of replays around a known drop-off point often reveals the cause quickly. Privacy is essential, so mask personal data, follow local data protection rules and tell users how their data is used.

AI-assisted synthesis

AI tools can transcribe sessions, suggest tags and draft summaries of themes across many interviews, which saves hours of manual work. The risk is that summaries can be wrong or invent quotes, so researchers must check outputs against the original recordings. Our post on AI tools in user research covers safe practices in detail.

Continuous discovery in practice

• Weekly touchpoint: At least one conversation with a user every week.
• Small questions: Focus on current decisions.
• Shared notes: Add findings to the repository.
• Act fast: Feed insights straight into the backlog.

Combining newer and classic methods

The most effective research programmes mix methods. Continuous discovery interviews explain why people behave as they do, micro-surveys and replays show what is happening at scale, and unmoderated tests check whether a design works before it ships. Larger, classic studies are still valuable for big decisions, new markets or complex products.

• Weekly: A short interview and a review of recent feedback.
• Every sprint: Unmoderated tests of upcoming designs.
• Continuously: Micro-surveys and replays on key journeys.
• Quarterly: A deeper study on a strategic question.

Storing what you learn

Fast research produces many small findings, which can easily get lost. Store them in a shared repository, tagged by journey, user group and theme, so the whole team can search them later. The atomic approach described in our post on research repositories works well for this kind of continuous learning.

These complement the classic methods in 15 user research methods. Watch for cognitive bias in fast, informal research.

Getting started this month

If your team has not used these methods before, start with one. A weekly thirty-minute interview slot is often the easiest win: book it as a recurring meeting, rotate who on the team attends, and share three findings after each session. Once that habit is established, add a micro-survey on one key journey and an unmoderated test before each major release. Within a few months, research becomes a normal part of how the team works rather than a special project.

• Book a recurring weekly interview slot
• Pick one journey for a micro-survey
• Run one unmoderated test before the next release
• Share findings in a short team update

Frequently asked questions

What is continuous discovery?

A practice where product teams talk to users regularly, often weekly, to inform ongoing decisions rather than in one-off studies.

Is unmoderated testing reliable?

For clear tasks, yes. For complex or exploratory questions, moderated sessions give richer insight.

Do in-product surveys annoy users?

Not if they are short, well-timed and easy to dismiss.

Related articles

• 15 user research methods beyond usability testing
• Understanding and reducing cognitive bias in user research
• Using AI tools in user research: what helps and what to avoid