article Part 2 of 6

Why Research? (Start Here, Not With Design)

Here's the thing about UX design: it begins with user research, not with sketching interfaces or picking colors. User research is the practice of learning about your target users' needs, behaviors, and pain points so that you can design the right solution.

Without research, design decisions would be based on assumptions or personal opinions rather than evidence, and you risk solving the wrong problems. By involving users early, you ensure you're considering the end user at every stage of the process. In short, good UX is user-informed—bringing real customers into the decision-making process is key to success.

Companies that invest in user-centered research and design tend to outperform those that don't, since they build products people actually find useful and enjoyable. It's not just good for users—it's good for business.

Common UX Research Methods

There are many research techniques available—both qualitative (exploring why or how people behave a certain way) and quantitative (measuring how much or how often something happens). Here are some of the most widely used methods:

User Interviews

One-on-one interviews with target users to gather in-depth insights. This method allows you to hear users describe their goals, frustrations, and experiences in their own words. Interviews are flexible and can be done at various stages of design. They're great for exploring why users behave a certain way or what they need.

Best practices:

  • Prepare a question script, but stay flexible
  • Avoid leading questions (don't guide them to the answer you want)
  • Listen more than you talk—let them tell their story
  • Ask "why?" to dig deeper into their responses

Example: An interview might reveal that users of an e-commerce site find the return process confusing, prompting you to redesign that workflow.

Starter interview template — adapt to your context, but this structure works for most product research:

Opening (builds rapport, sets expectations — ~5 min):

  1. "Thanks for joining me today. I want to be clear: we're testing the design, not you — there are no wrong answers."
  2. "Can you tell me a bit about yourself and what you do day-to-day?"
  3. "How often do you [relevant activity — e.g., shop online / manage projects / use apps like this]?"
  4. "What device do you most often use for that?"
  5. "Before we look at anything, can you describe the last time you tried to [core task your product handles]?"

Core questions (dig into behaviour and pain points — ~20 min):

  1. "Walk me through what that process looked like from start to finish."
  2. "What was the most frustrating part of that experience?"
  3. "Is there anything you wish you could do that the current [tool/site/process] doesn't let you do easily?"
  4. "What do you do when you get stuck or confused?"
  5. "If you could change one thing about how you currently handle [task], what would it be?"

Surveys & Questionnaires

Structured sets of questions (often multiple-choice or rating scales) distributed to a larger sample of users. Surveys are efficient for collecting quantitative data (e.g., "90% of users find navigation very easy or easy to use") and some qualitative comments.

Best practices:

  • Keep surveys concise and focused on your key goals
  • Use clear, unbiased questions
  • Include some open-ended questions for rich feedback
  • Keep it short to encourage completion (survey fatigue is real)

Surveys should be designed carefully—you want data you can actually act on, not just nice-to-know information.

Focus Groups

A moderated discussion with a small group of users (typically 5–8 people) to collect a range of opinions and reactions. Focus groups can quickly surface common attitudes or ideas, especially in the ideation phase or to get feedback on early concepts.

A facilitator leads the conversation with prepared questions while ensuring everyone's voice is heard.

Best practices:

  • Prevent one or two people from dominating the discussion
  • Encourage diverse perspectives
  • Sometimes quieter participants need to be prompted to share
  • Record sessions (with permission) so you can review later

Focus groups are great for breadth of opinions, but be careful—group dynamics can sometimes influence individual responses.

Field Studies (Contextual Inquiry)

Observing and/or interviewing users in their natural environment—for instance, watching how people actually use a website or app in real life, or how they perform the task your product aims to facilitate.

This helps you understand the context of use: physical environment, device, time constraints, distractions, and other real-world challenges that might not arise in a lab setting.

Example: If you're designing a navigation app, a field study might involve riding along with users as they try to use your app while driving. You might discover pain points like voice instructions that are hard to hear over road noise, or that the UI is difficult to interact with while stopped at red lights.

Analytics & Existing Data

Using data from existing website analytics, search queries, support tickets, or other sources to understand user behavior at scale. For instance, web analytics might show where users commonly drop off in the conversion funnel, indicating a potential UX issue on certain pages.

While this is more of an evaluation than a generative research method, it's invaluable for identifying problem areas to investigate further. Think of analytics as your "what's happening" data, which you can then explore with qualitative methods to understand "why it's happening."

Synthesizing Research: Personas and Journey Maps

Often, researchers will synthesize findings from these methods into concrete artifacts that help the design team keep users in mind throughout the process:

User Personas: Fictional profiles representing key user types based on research. A well-crafted persona document typically includes:

  • Name and photo (fictional, but makes them feel real to the team)
  • Background: age, occupation, relevant life context
  • Goals: what they're trying to accomplish when they use your product
  • Frustrations: their recurring pain points related to the problem you're solving
  • Tech comfort level: novice / intermediate / expert — affects how much guidance they need
  • A representative quote: a sentence in their voice that captures their mindset ("I just want to find what I need and get out — I don't have time to learn a new system.")

Example persona: Priya, 34, freelance graphic designer. Goals: quickly find and invoice clients, track project time without friction. Frustrations: accounting tools feel overly complex; she's not confident with tax terminology. Tech comfort: high for design tools, medium for business software. Quote: "I just want the admin side to take 30 minutes a week, not 3 hours."

Journey Maps: Visualizations of a user's steps and feelings in accomplishing a task. Columns typically show each step of the journey; rows show what the user is doing, thinking, and feeling at each step, plus opportunities for improvement. The "feeling" row (often shown as a curve — up for positive moments, down for pain points) makes it immediately obvious where the experience breaks down and where design energy should go.

These tools aren't just academic exercises—they're practical references that keep your team aligned on who you're designing for.

User Research in Practice

The insights from research inform all later stages of design. Here's how it might play out:

  • If interviews reveal that new visitors don't understand what your product does, you know to make your homepage messaging clearer.
  • If a survey shows most users primarily access your site on mobile, you'd prioritize a mobile-friendly design.
  • If analytics show users are frequently using the search bar to find content that's buried in navigation, you might restructure your information architecture.

By respecting what you learn about your users (instead of relying on guesswork), you "stop relying on assumptions and design products that solve real problems." Research-driven design is not just good for users—it leads to higher user satisfaction and loyalty, which benefits the business too.

Getting Started with Research

If you're new to user research, here's a simple approach to get started:

  1. Start small: You don't need a massive research budget. Even talking to 3–5 users can reveal major insights.
  2. Define your questions: What do you need to learn? Focus on the biggest unknowns or riskiest assumptions.
  3. Pick the right method: Need depth? Do interviews. Need breadth? Try a survey. Want to see real behavior? Do field observation.
  4. Recruit representative users: Find people who actually match your target audience (or as close as you can get).
  5. Document and share: Take notes, record sessions (with permission), and share findings with your team.

The key is to actually do research, even if it's informal. Talking to real users beats guessing every single time.

Key Takeaways

  • User research is the foundation of good UX design—always start by understanding your users.
  • Different research methods serve different purposes: interviews for depth, surveys for scale, field studies for context, analytics for patterns.
  • Good research involves real users and generates actionable insights, not just interesting information.
  • Synthesize findings into personas and journey maps to keep users front-and-center throughout design.
  • Even small-scale research is better than no research—start with what you can and build from there.

Now that you understand your users, the next step is organizing your content in a way that makes sense to them. That's where Information Architecture comes in.