Great interfaces start with understanding people. A little research before design prevents a lot of rework after launch and it doesn’t need a big budget, a lab or months of time.
Why research first
Every product team makes assumptions: who the users are, what they want, how they’ll use the product, what words they understand. Some assumptions are right. Many are partly wrong, and a few are completely wrong. User research is simply the habit of checking those assumptions with real people before you spend months building on them.
Fixing a misunderstanding in a sketch takes minutes. Fixing it in a finished app means redesign, redevelopment and retesting - and often lost customers along the way. Research is one of the cheapest forms of insurance a product can have.
Start with the right questions
Good research starts with clear questions, not methods. Before talking to anyone, write down what you need to learn. For example:
- Who exactly are our users, and what are they trying to get done?
- How do they solve this problem today, and what frustrates them?
- What would make them trust a new product enough to try it?
- Where do people get stuck in our current flow?
Then pick the method that answers those questions most directly.
Simple methods that work
- User interviews - 5 to 8 conversations of around 30 minutes with people who match your target users. Ask about their past behaviour and real experiences, not hypothetical opinions.
- Usability testing give people realistic tasks on a prototype or live product and watch where they hesitate. Even five participants usually reveal the biggest problems.
- Surveys useful for measuring how common something is, once interviews have shown you what to ask.
- Analytics review find where people drop off, which pages they use most and what they search for.
- Competitor review see how others solve the same problem and where users complain about them.
- Support and sales conversations your team hears user problems every day; collect them.
Running a good interview
- Explain the purpose and get consent to take notes or record.
- Start broad: ask about their role, routine and context.
- Ask about specific recent experiences: “Tell me about the last time you…”.
- Follow up with “why?” and “what happened next?” the real insight is usually in the second or third answer.
- Avoid leading questions like “Would you use a feature that…?” people are kind and will say yes.
- Listen more than you talk, and thank them for their time.
Turning findings into design
Research only matters if it changes decisions. After each round, gather notes and look for patterns across participants. Group similar observations, then turn them into clear outputs the whole team can use:
- Personas or user profiles grounded in what you actually heard.
- Journey maps showing each step, what users feel and where the pain points are.
- Problem statements such as “Parents need to see fees and batch timings without calling the academy.”
- A prioritised list of design changes, linked to the evidence behind each one.
Then sketch, prototype and test again. Research and design work best as a loop, not a one-time phase.
Research on a small budget
You don’t need a lab. Five short video calls, a clickable prototype in Figma and a shared notes document will uncover most major issues. Recruit from your existing customers, your social following or your team’s networks, and offer a small thank-you. Test early and often rough prototypes are fine, and people are more honest about something that looks unfinished.
Common mistakes
- Only talking to friends, colleagues or the people who already love the product.
- Asking what features people want instead of understanding their problems.
- Doing research once and never again.
- Collecting insights that never reach the designers and developers.
- Treating one strong opinion as a pattern.
A simple example
Imagine a sports academy planning a new website. The team assumes parents want an eye-catching gallery and a long history page. Five short interviews with parents show something different: what they really want is to check batch timings, fees and coach details on their phone, and to book a trial without calling. Those findings reshape the whole design - the homepage leads with programmes and a booking button, timings move to a clear table, and the gallery becomes a supporting section. A few hours of conversations saved weeks of building the wrong thing.
Making research a habit
The best product teams don’t treat research as a phase; they make it routine. Try a light rhythm: one or two user conversations every couple of weeks, a quick usability test before each major release and a monthly look at analytics and support tickets. Keep a shared document of insights so everyone - designers, developers, marketers and founders can see what users are saying. Over time this builds an instinct for what your users need, and design decisions become faster and calmer because they’re grounded in evidence rather than opinion.
Quick answers
How many people do I need to talk to? For interviews and usability tests, five to eight people per user group usually surfaces the main patterns. Can I research an idea before anything is built? Yes - interviews and simple paper or Figma prototypes are ideal at that stage. What if users ask for conflicting things? Look past the feature requests to the underlying problem; often one design solves several requests. Who should attend sessions? Invite developers and stakeholders to watch at least one; seeing a user struggle is more persuasive than any report.
Helpful, low-cost tools
You can run good research with simple tools: a video-calling app with recording (with consent) for interviews, Figma for clickable prototypes, a form tool for screeners and short surveys, a shared document or whiteboard for organising notes and themes, and your existing analytics for behaviour data. The tool matters far less than the habit of asking good questions, listening carefully and acting on what you learn.
Quick checklist
- Written research questions before choosing a method
- 5–8 interviews with real target users
- Usability test on a prototype before development
- Findings turned into journeys and problem statements
- Design changes linked to evidence
- Test again after changes



