Use what already exists before asking for anything. Support tickets, sales call recordings, in-product search logs, session recordings, and analytics answer a surprising number of questions for free. Then get five people in front of a prototype, even if they are internal staff close to the problem, and be explicit about the weaker sample. Finish with a staged rollout so real users become the final check.
Why interviewers ask this
This is the everyday reality of design work, and it separates people who need ideal conditions from people who ship. Interviewers want resourcefulness plus honesty about confidence: using internal participants is fine as long as you say what that limits. They are also listening for whether you know that support tickets and search logs are free research nobody bothers to read.
How to structure your answer
- Mine existing evidence first: tickets, recordings, search logs, analytics.
- Talk to the people who talk to customers: support and sales.
- Run five quick unmoderated sessions on a rough prototype.
- State the confidence level and the risk you are accepting.
- De-risk the launch with a staged rollout and a rollback plan.
Example answer
Two weeks is enough if I stop treating research as something that has to be commissioned. Day one and two I read support tickets for that flow sorted by volume, and I go through search queries inside the product, which is basically users telling you what they cannot find, in their own words. Then I spend an hour each with two support agents and someone from sales, because they hear the same complaint forty times a week and nobody ever asks them. That usually gets me most of the problem definition. Then I build a rough prototype and run five unmoderated sessions on a testing platform, which costs very little and turns around overnight. If I genuinely cannot recruit externally, I will use internal people who are not on the product team, and I say clearly in the readout that they are not representative, so we treat findings as signals rather than proof. Finally I would ship behind a flag to five percent and watch. Real users at low volume are better evidence than a perfect study I did not have time to run.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- What are the risks of testing with internal employees?
- How do you decide what to look at first in support tickets?
- How do you communicate low confidence to stakeholders?
Related ux designer questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions