
How Exploratory UX Research Methods Shape Better Design
The exploratory research methods to run before design, and how they shape what gets built.


Table of contents
Free Website Audit
We'll personally review your website across 6 areas. UX, SEO, performance, mobile, conversion, and send you a detailed, actionable report within 48 hours. No cost. No catch.
Exploratory user research is the work you do before design starts. It finds out what users need and which problems are worth solving. It is also called generative or discovery research. The main methods are stakeholder workshops, competitor reviews, user interviews, surveys, field studies and diary studies. Each one uncovers something different, from business goals to how people actually behave. On a tight budget, the minimum I accept is a stakeholder workshop and a competitor review. The findings shape the sitemap, the user flows and which problems the design tackles first.
What Is Exploratory User Research?
Exploratory user research is the investigation you run before any design exists. Its job is to find out what users need, what gets in their way and which problem to solve. It is the first stage of the UX design process, so there is nothing to test yet.
You will also see it called generative, discovery or foundational research. These names describe the same phase. GetWhy, a product research company, describes generative research as exploratory. It discovers problems, needs and opportunities before a solution exists.
The opposite phase is evaluative research, which checks whether a design works once it exists. Exploratory research decides what to build. Evaluative research checks whether you built it well.
Why Does Exploratory Research Come Before the First Wireframe?
Every design rests on assumptions about users, and research is the cheapest point to check them. Before wireframes exist, a wrong assumption costs a conversation. After them, it costs a redesign. Two of my own projects show both sides of this.
What Research Taught Me on BigFundr
When I started designing BigFundr's investment app, I honestly did not know what good investing onboarding looked like. I did my homework first. I signed up for many investing platforms to see how each one handled sign-up. That showed me the patterns, but not which ones mattered to investors.
What changed it was sitting with five people who already invested through other apps. In one-on-one sessions, they showed me how those apps worked and where they nearly gave up. It made my job much easier. Onboarding was clearly where an investing app keeps or loses a customer. That insight shaped how we designed BigFundr's investment app, with onboarding as a priority from the start.
When Research Is Blocked
The opposite happened on a large internal operations project. The client's finance, procurement and operations teams each used separate apps that did not connect. The brief was simple: give them one line of communication, so every department knew the next step.
I was not trying to replace their apps. I only needed to understand how the teams actually communicated across them. But no department wanted to give up its familiar tools. None would walk us through its real workflow. Without that input, the designs could not meet the standard, and the project was cut short.
That project shaped what I tell clients now. Research is not the designer's curiosity. It is the material the design is built from, and the output suffers without it.
Which Exploratory Research Methods Should You Use?
Use the methods that answer what you do not know yet, within your budget and your access to users. Most projects need two or three of them. The table shows what each method tells you and when it earns its place.
These are the same methods behind our UX research services, scaled to what each project needs. Here is how each one works in practice.
1. Stakeholder Workshop
Every project I take on starts with a workshop with the client. It covers what they need, the problems they face today and what they are trying to achieve. For a website, we also walk through their current pages together.
These are the questions I bring to every workshop, whatever the project:
- What do you need this website or app to do for the business?
- What problems are customers or staff running into today?
- What does success look like six months after launch?
- Which pages or features get the most complaints?
- Which competitors do your customers compare you with?
If I can, I bring in the sales team and support staff too. They are on the ground, and they are usually the first people a customer goes to. They hear questions and complaints that never reach a boardroom. That makes them the closest thing to the customer in the room.
2. Competitor Review
The fastest exploratory method is a competitor review: studying how other businesses solve the same problem. It is quick, which is why it runs inside every workshop. Business owners usually know their competitors well, so they can point me straight to the ones that matter.
I add my own review on top, signing up for competitor products and going through them as a customer would. Nielsen Norman Group notes that full competitive usability evaluations can be expensive for teams with small budgets. A lighter review still shows you the patterns users already expect.
3. User Interviews

User interviews are one-on-one conversations with real or potential users about how they behave and why. They are the richest method, and the hardest to arrange. Ask what people did last time, not what they would want. People describe past behaviour far better than they design their own solutions.
Access depends on the project. For a website, reaching the client's customers is difficult. For an app, it is usually possible with an incentive. Most customers will not talk to an agency face to face for nothing. BigFundr offered incentives, which opened a path to their current users.
You do not always need the client's own customers to start. My first five BigFundr interviewees were investors who used other apps. They gave me a starting point before I heard from BigFundr's own users.
Recruit people who match your real users. Friends and colleagues are easy to book but rarely representative. Keep each session to a few focused questions, and let the participant show you rather than tell you. The most useful moments on BigFundr came when interviewees opened the apps they already used and walked me through them.
4. Surveys

Surveys collect answers from many users at once, trading depth for reach. They work best when a product already has users you can ask. For BigFundr's existing customers, we ran a survey asking what they disliked about the current app and web app.
Write the survey last, once the workshop and interviews have shown you what to ask. A survey drafted without those conversations tends to measure the team's assumptions instead of the users' problems. Keep it short, and leave room for one or two open answers in the users' own words.
5. Field Studies and Contextual Inquiry

A field study means watching people do their real work in their own environment, asking questions as they go. It shows what people actually do, including the workarounds they no longer notice. Use it when a workflow crosses several teams or tools.
This is exactly what the internal operations project needed. I wanted to see how a request moved from procurement to finance to operations across separate apps. A few observed sessions would have answered that. Without that access, there was no way to design the single line of communication the client asked for.
6. Diary Studies
In a diary study, participants record their experiences over days or weeks, as they happen. GitLab's UX research handbook recommends them when you need to understand people beyond a single interaction. They suit long journeys and repeated tasks, such as an investor's first weeks on a platform. Because they take weeks, they fit larger projects with time to spare.
What About Focus Groups?

Focus groups are a weak fit for exploratory research. They capture what people say in a group, not what they do. The research field guide from User Interviews is blunt about this. For an accurate read on behaviour, it says focus groups are probably the wrong method. One confident voice can also steer the whole room. Separate interviews usually tell you more for the same effort.
How Much Exploratory User Research Is Enough on a Tight Budget?
On a tight budget, the minimum is a stakeholder workshop with a competitor review. A tight budget does constrain a lot of my work. Still, this pairing is quick and gives the design a real starting point.
If something has to give, I would rather cut scope than design blind.
On app projects with limited budgets, I phase the work instead. Research stays focused on the main pain points and how competitors handle them. The first phase then covers fewer use cases, but each one solves a real problem for the client's customers.
If you can add interviews, there is no fixed number to aim for. In a widely cited study, Guest, Bunce and Johnson (2006) found their themes stopped changing after 12 interviews. Their participants were a fairly similar group of people. Smaller rounds still help. My five BigFundr interviews gave me a clear direction. Plan more if your users fall into very different groups.
Turning Research Findings Into Design Decisions
Findings turn into design through one main deliverable: a proper sitemap, with recommendations for improving the current structure. The sitemap decides which pages or screens exist and how people move between them. This is where research becomes structure, and good structure is what makes intuitive navigation possible later.
Everything else from the workshop lives in Figma or FigJam: the goals, the competitor notes and the problems we listed. The client can review it at their own pace. Then we agree on what is happening now and what happens next, before any visual design starts.
Research also changes priorities. On BigFundr, the interviews moved onboarding to the top of the list. On a website, the workshop and the sales team's input usually show which pages need attention first. That order then guides the design brief.
Where Exploratory Research Ends
Exploratory research ends when there is something to test. Once BigFundr's wireframes were ready, I gathered stakeholders and users in one room to try the working prototype. That session was evaluative research, because it checked the design instead of shaping it. The two phases work in sequence, and skipping the first makes the second far more painful.
Frequently Asked Questions
Is exploratory research the same as generative research?
In practice, yes. Exploratory, generative, discovery and foundational research all describe the phase before design, where you learn about users and their problems. Some researchers draw finer distinctions between them, but the timing and methods overlap almost completely. What matters is that it happens before you commit to a solution.
How many users should I interview for exploratory research?
Interview until you stop hearing new themes, a point researchers call saturation. How soon that comes depends on how varied your users are. A small round of five can give you a clear direction for a focused question. If you have several distinct user groups, plan a few interviews per group rather than one large batch.
Can you do exploratory research without talking to customers?
Yes, though you will learn less. A stakeholder workshop, input from sales and support staff and a competitor review need no customer access at all. Signing up for competitor products and using them as a customer would also helps. Treat customer interviews as the upgrade when budget and access allow.
Do websites need exploratory research, or only apps?
Both need it, but the methods differ. Apps often justify interviews and surveys, because users can be reached with an incentive. Websites lean more on the workshop, the competitor review and the client's own knowledge of its customers. If you are hiring help, ask what research is included. It is one of the first things to check when choosing a UX designer in Singapore.
Conclusion
Before your next design project starts, book a short workshop with the people who know your customers best. Invite your sales and support staff as well as management.
Then list the three competitors your customers compare you with, and go through their sign-up or enquiry flow yourself. Decide whether you can reach real users, and what incentive it would take to hear from them. Once a design exists, the next step is checking that it works. That is where a website usability audit comes in.
{{build-better-experience="/directory"}}
Categories
Resources
Related Articles
Deep dive into our latest news and insights.
.webp)



