Key takeaways
- Exploratory research (also called generative, discovery, or foundational research) is used early in the design process to understand users' real needs, behaviours, and pain points before deciding what to build.
- It's most useful when you don't yet know what the right answer is. Once you've narrowed down to specific solutions, evaluative research (usability testing, A/B testing) takes over.
- Common methods include user interviews, focus groups, diary studies, mobile ethnography, journey mapping, and pre-tasking. Each has trade-offs across context, depth, and time.
- Mobile ethnography stands out because it captures actual behaviour in users' real environments, rather than what they remember or claim they did.
- With Indeemo you can run diary studies and mobile ethnography end to end: recruit from a global panel, capture videos, photos, screen recordings, and texts in 30+ languages, and analyse with AI.
A UX researcher's first job is to act as a user ambassador. To represent users well, you need to understand them well, and the best way to understand someone is to spend time in their world.
Exploratory research is a holistic approach to user research that gives you a clear picture of pain points and unmet needs before the design work starts. Done well, it reduces rework, lessens UX debt, and helps teams build things people actually want.
This guide covers what exploratory research is, when to use it, how it differs from evaluative research, and the qualitative methods that work best for it.
What is exploratory research?
Exploratory research is qualitative research used to understand the broader context of users' experiences, particularly when little or nothing is known about the area. It's also called generative research, discovery research, or foundational research, and it can be applied at any point in the UX design cycle, though it's most common at the start.
The goal can be summarised in five verbs: uncover, discover, understand, explore, learn. The output is a deep understanding of the unmet, often unarticulated needs of your users. That's the kind of insight that helps you build empathy and design products, services, and experiences that genuinely matter to people.
Exploratory research seeks to understand the broader context of users' experiences with the intention of providing them with something they need, even if they don't know they need it yet. Communicating those discovered needs clearly to stakeholders is part of the job.
When should you use exploratory research?
Use exploratory research when you don't yet know what the right answer is.
That sounds obvious, but in practice it covers a lot of ground. You might be entering a new market, designing for a new user group, exploring a new product idea, redesigning a poorly performing experience, or trying to understand why a metric is moving in a way you can't explain. In each case, the question isn't "does X work?" but "what's actually going on, and what do users really need?"
Exploratory research belongs in the discovery phase of the design process. According to NN/g, discovery research is the qualitative work UX teams do to understand user needs and inform what gets designed, as distinct from the evaluative work that comes later.
If you've already narrowed to specific solutions and want to know if they work, you're past exploratory research and into evaluative.
How is exploratory research different from evaluative research?
Exploratory research asks "what do users need?" Evaluative research asks "does this design meet their needs?"
Exploratory work is open-ended and generative. You don't know what you'll find. Evaluative work is hypothesis-driven; you have a design or solution and you're testing it. Both are essential, but they belong at different points in the project. Skipping exploratory research and going straight to evaluation is one of the most common ways teams end up building beautifully usable products that nobody actually wants.
What methods are used in exploratory research?
Several qualitative methods are used in exploratory research, each with strengths and trade-offs.
The default for many teams is the user interview or focus group. Both are synchronous: a researcher and one or more participants in the same conversation at the same time. They're quick to organise and produce useful material fast, but they have a real limitation. Because you're relying on what participants tell you in a single conversation, the insights are based on claimed behaviour rather than actual behaviour. People misremember, post-rationalise, and tell you what they think you want to hear.
Asynchronous methods get closer to what people actually do.
Pre-tasking, where participants complete a short mobile diary task before an interview, is often used to augment the interview rather than as a standalone method. It gives the participant time to reflect on the topic, and gives the moderator real-world videos and context to reference during the conversation.
Why use mobile ethnography for exploratory research?
Mobile ethnography lets you observe users in the closest thing to their natural state, short of physically following them around. They go about their day with their phone, capturing videos, photos, screen recordings, and texts as decisions and behaviours unfold. You watch from a dashboard, ask follow-up questions when needed, and analyse what you see.
The advantage for exploratory work specifically: you can go broad and deep at the same time. Broad, because you can run a study with more participants across more locations than traditional ethnography ever allowed. Deep, because what you capture is real behaviour in real context, with all the unconscious cues that interviews miss.
A few things mobile ethnography is particularly suited to in exploratory work:
- Behaviour over time. A single conversation captures a snapshot. Mobile ethnography captures a routine.
- Outliers that happen predictably. Edge cases and unusual behaviours surface naturally over a multi-day study, when they'd never come up in a one-hour interview.
- Hidden biases and assumptions. You see what users actually do, which is often quite different from what your team has assumed they do.
- Motivations and fears. When participants narrate their own experience in their own environment, you hear the why behind the action, the things they wouldn't think to mention in a structured interview.
Mobile ethnography also fits modern research operations well. AI-powered transcription and translation in 30+ languages mean you can review submissions almost in real time and run studies across markets without waiting weeks for translation.
The three R's of the user ambassador
If you take exploratory research seriously, three things matter:
- Research the actual behaviour and environment of the users you're representing.
- Represent those users effectively to the people making design and product decisions.
- Real needs, not assumed ones, not articulated ones, drive successful products.
The simplest test of exploratory research is whether your team's view of the user changed because of what you found. If nothing changed, you weren't exploring; you were confirming. The point of going broad and deep is to find out what you didn't already know.
Frequently asked questions
What's the difference between exploratory and evaluative research?
Exploratory research asks "what do users need?" Evaluative research asks "does this design meet their needs?" Exploratory work is open-ended and used early in the design process to inform decisions. Evaluative work tests specific solutions, usually later, through usability testing or A/B testing. Both are needed, but for different questions at different points in the project.
How long does an exploratory research project usually take?
It depends on the method and the depth required. A focus group or set of interviews can run in a single week. A diary study or mobile ethnography study typically runs from one to four weeks of fieldwork, with another week or two for analysis. Most exploratory projects sit between two and six weeks end to end.
Can you combine exploratory research methods in one study?
Yes, and it's often the most useful approach. A common combination is a few days of mobile ethnography or diary tasks as pre-tasking, followed by interviews where the researcher uses the participants' own videos and notes as a starting point. The asynchronous task surfaces real behaviour; the synchronous conversation lets you probe the why behind it.
What outputs come out of exploratory research?
Typical deliverables include user personas, journey maps, opportunity areas, problem statements, and highlight reels of user video that bring stakeholders into the user's world. The format matters less than whether the output actually changes what the team decides to build next.
Exploratory research is the work you do to make sure you're solving the right problem before you start solving it. Done well, it's the cheapest insurance policy in product development. Done badly or skipped entirely, it shows up later as rework, churn, or a beautifully built product nobody uses.
If you'd like to talk about how mobile ethnography or a diary study could fit your next discovery project, get in touch.
