Key takeaways
- Discovery research is the early phase of a UX or product design project. The goal is to understand users, frame the right problem, and decide what to build before committing to a direction.
- It's sometimes called exploratory, generative, or foundational research, and sits at the start of frameworks like the Design Council's Double Diamond Model.
- Traditional methods (in-person diary studies, field studies, ethnographic research) work well, but they tend to be slow and expensive, and the data is hard to get to in real time.
- Mobile ethnography compresses the same activities into a smartphone app. Participants share videos, photos, screen recordings, and texts from their real environment, while researchers review and probe asynchronously.
- The output of discovery research is usually a set of deliverables: personas, journey maps, and service blueprints. Mobile ethnography supports all three.
- With Indeemo, you can recruit from a global panel, run discovery studies in 30+ languages, analyse responses with AI, and create subtitled highlight reels for stakeholders.
What is discovery research?
Discovery research is the early phase of a UX or product design project, where the goal is to understand the people you're designing for, frame the problem accurately, and decide what to build before committing to a direction.
The Nielsen Norman Group defines the discovery phase as "a preliminary phase in the UX-design process that involves researching the problem space, framing the problem(s) to be solved, and gathering enough evidence and initial direction on what to do next."
It's also represented in the first diamond of the UK Design Council's Double Diamond Model, where teams diverge to explore the problem space before converging on a brief.
Discovery research is sometimes called exploratory, generative, or foundational research. It sits at a different point in the project lifecycle than evaluative research, which tests how well an existing design works. Generative research asks "what should we build?" Evaluative research asks "is what we built any good?" Both have their place, but they answer different questions, and discovery is where most product missteps could have been avoided.
What does the discovery research phase achieve?
A well-run discovery phase helps UX and product teams uncover three things: the right user personas, the pain points worth solving for, and the scope of the problem area.
Personas describe who the actual users are, not who the team assumes they are. Pain points are the real problems users face, in their own words. The scope of the problem area defines what's in scope for this project, and what isn't.
When discovery research is done properly, organisations can build products people actually want, avoid scope creep, and stay on schedule. When it's skipped or rushed, teams end up rebuilding later, usually after the first round of user testing reveals the original brief was off. That kind of rework costs far more than spending two extra weeks understanding the problem upfront.
What are the limitations of traditional discovery research methods?
Traditional discovery research draws on a few well-established methods: diary studies, field studies, and ethnographic research. Each has real strengths, but each comes with practical limitations that mobile ethnography can address.
Diary studies. Participants keep a record of their experiences and reactions over a set period. The method captures behaviour over time, but the data tends to come back in batches at the end of the study. That makes it hard for researchers to ask follow-up questions or course-correct while the study is still running. Collating notes from multiple participants after the fact is also slow.
Field studies. Researchers travel to where users are and observe them in context. Rich, but logistically heavy. It's standard practice for researchers to go in pairs (one to ask questions, one to take notes), which doubles the cost. Geographic coverage is limited by travel budget.
Ethnographic research. A deeper version of field study work, with researchers spending extended time embedded in a setting. The output is detailed and contextual, but the timeline can stretch into weeks or months, and the sample size stays small.
How does mobile ethnography support discovery research?
Mobile ethnography keeps the intent of traditional methods (understanding people in their own environment) but removes the physical barriers. Participants use a smartphone app to share videos, photos, screen recordings, and texts from their real lives. Researchers review submissions on a dashboard as they come in, ask follow-up questions, and probe for context, the same way you'd reply to a friend's social-media post.
The term might sound academic, but the tool is mobile-first and designed to feel familiar. The participant app uses social-networking-style UX that people already know how to use, so onboarding is fast and dropout rates stay low. AI handles the heavy lifting on transcription, translation, and analysis. And if you need help, our team is there.
For a discovery research project, that translates into a few practical advantages.
- Real-time access to data. As participants record, the responses appear on the researcher dashboard. You can ask a follow-up question while a memory is fresh, instead of waiting until the end of fieldwork.
- Asynchronous coordination across markets. Run the same study in five countries at the same time. Recruit from a global panel of 3 million+ participants and capture responses in 30+ languages.
- Organised, searchable data. Submissions are automatically transcribed, translated, and tagged. You can filter, search, and pull together themes without spending days on transcription.
- Lower cost, broader reach. No travel. No researcher pairs. More participants, in more places, for less.
Which deliverables does discovery research produce?
Discovery research typically produces three core deliverables: personas, journey maps, and service blueprints. Mobile ethnography supports all three.
Personas
Personas help product teams align on different types of users and how they interact with a product. Building them requires a representative sample of the actual user base, captured in enough detail to differentiate one persona from another.
Mobile ethnography supports persona development by reaching users asynchronously, capturing their behaviours, preferences, and motivations in their natural environment. Because you can recruit a larger sample without travel, the resulting personas are based on more data points than a typical round of in-person interviews would produce. In-context surveys and prompts let you fill in specific gaps as the study runs.
Journey maps
Journey maps visualise how a user moves through an experience, focusing on the usability of the touchpoints they encounter. Building one usually means understanding behaviour at every stage: awareness, consideration, purchase, onboarding, and ongoing use.
Mobile ethnography captures these stages as they actually happen. Screen recording shows how someone navigates a website. In-context video shows how they move through a physical space. Voice-over narration reveals what they're thinking. Emotional state at each touchpoint can be captured and plotted using CSAT or NPS-style ratings. The output is a journey map grounded in real behaviour, not workshop hypotheses.
For more on this, read our guide to customer journey mapping.
Service blueprints
Service blueprints extend journey maps to include the wider customer experience: front-stage and back-stage, online and offline. They typically take many in-person meetings with users and stakeholders to put together.
Mobile ethnography shortens that timeline. Asynchronous interviews with question prompts gather the user-side input in days rather than weeks. Screen recordings show exactly where the digital experience supports or breaks down. Combined with stakeholder workshops, the resulting blueprint is faster to build and grounded in real customer evidence.
How long does a discovery research study take?
A typical discovery research study runs for one to three weeks of fieldwork, depending on scope and the depth of behavioural data needed.
- Quick discovery (3–5 days): Useful for testing assumptions or exploring a specific question. 10–15 participants is often enough.
- Standard discovery (1–2 weeks): The most common length. Enough time to capture routine behaviour and follow up on interesting submissions. 15–30 participants.
- Deeper exploratory studies (2–4 weeks): When you're entering a new market or building personas from scratch. 25–50+ participants, often across multiple markets.
Recruitment can be quick if you're using an existing panel. Indeemo's panel of 3 million+ participants means you can recruit a target sample within a few days, instead of the multi-week timelines that on-the-ground recruitment usually requires. For diary-style discovery work specifically, our guide to diary studies walks through the design considerations in more detail.
How does AI accelerate discovery research analysis?
The hardest part of discovery research used to be making sense of all the data. Hours of video to review. Dozens of participants across multiple markets. Analysis used to be the slowest part of any discovery project.
AI changes the maths. With Indeemo, video, audio, and text submissions are automatically transcribed and translated in 30+ languages as they come in. Generative AI helps you find patterns and themes across submissions, detect sentiment, and pull together summaries, so you can spend less time on transcription and more time understanding what people are really telling you.
In typical discovery projects, this end-to-end workflow can reduce analysis time by 40–90% compared with traditional manual transcription and coding.
Once you've identified the moments that matter, you can stitch them into a subtitled highlight reel. Sharing a five-minute reel of real user voices with a product team is a faster path to alignment than circulating a 40-page report.
Do you need research expertise to run a discovery study?
No. Whether you're an experienced UX researcher or a brand or product team running discovery for the first time, Indeemo can support you.
Use the platform independently if you have the expertise in-house. Or partner with our Catalyst team for study design, recruitment, moderation, analysis, or the full project. If you have research ambitions but not the capacity or expertise to run the study yourself, we can lend a helping hand as and when you need it.
We've supported thousands of discovery research projects across product design, healthcare, FMCG, retail, and financial services. Whatever your topic, we can help you turn questions into evidence.
Frequently asked questions
What's the difference between discovery research and evaluative research?
Discovery research is generative. It asks "what problem should we solve, and for whom?" Evaluative research is testing-focused. It asks "is what we've built working?" Discovery happens at the start of a project. Evaluative happens once you have something to test, like a prototype or a live product.
How is discovery research different from a usability study?
A usability study tests how easy a specific design is to use. Discovery research is broader and earlier. It explores the problem space before any design exists. You'd run discovery research to decide what to build, and a usability study to check that what you've built actually works.
How many participants do you need for a discovery research study?
Most discovery studies work well with 15–30 participants. For broader exploratory work or persona development across multiple markets, 25–50+ is more typical. Mobile ethnography captures rich data from each participant, so you usually need fewer people than you'd expect.
Can you run discovery research across multiple countries?
Yes. Mobile ethnography lets you run studies across multiple markets at the same time. Recruit from a global panel, set up tasks in any language, and use automated transcription and translation in 30+ languages so your team can review submissions immediately.
What deliverables come out of a discovery research project?
The most common are personas, journey maps, and service blueprints. You might also produce a research report, a list of prioritised pain points, opportunity areas for design, or a highlight reel of participant voices for stakeholder buy-in.
