User Research

What is User Research?

User Research is the systematic process of investigating and understanding actual user behavior, needs, challenges, and motivations, then incorporating those insights into product design. It combines diverse quantitative and qualitative research methods—interviews, surveys, behavioral observation, log analysis—to build a comprehensive understanding of users. Design based on user research achieves far greater market fit than design relying on developer assumptions.

In a nutshell: “Investigating through various methods how actual users behave and what needs they have to inform design decisions.”

Key points:

• What it does: Systematically researches user behavior, challenges, and needs
• Why it matters: Bridges the gap between developer assumptions and actual user needs
• Who uses it: UX designers, UX researchers, product managers, marketers

Why it matters

Most product development begins with the team’s assumption: “Users probably need this.” Often, these assumptions are wrong. For instance, when developing a task management app, developers might assume complex features are necessary, but actual users might only want a simple list display.

Conducting user research upfront reveals these gaps before development, allowing limited resources to focus on features users truly need. This improves development efficiency and increases post-launch user satisfaction. Failed products typically lack sufficient user research, proceeding solely on developer assumptions.

How it works

User research comprises two main approaches:

Qualitative Research explores the “why” and “how” behind behaviors. User interviews are the most representative method—through one-on-one dialogue, researchers understand user motivations, challenges, and solutions. Questions like “Why do you use this app daily?” and “Where do you encounter difficulties?” reveal psychological factors that numbers cannot express. Behavioral observation (field research) is another qualitative method, watching users in their natural environment to capture authentic behavior patterns.

Quantitative Research gathers numerically measurable information about “what percentage” and “at what scale.” Surveys collect numerical data from large user groups, revealing overall trends. Access log analysis automatically records user behavior in implemented products, quantifying patterns like “which page gets most views” and “where do abandonment rates spike.”

Combining both approaches creates comprehensive user understanding. Qualitative research answers “why,” while quantitative research confirms “how much.”

Real-world use cases

Online Banking Service Feature Planning When a bank conducted user interviews, they discovered “We have multiple accounts but the current service makes inter-account transfers complicated.” Based on this insight, they designed the new “simplified inter-account transfer” feature, which saw post-launch usage three times higher than expected.

Smartphone Game New User Improvement A game development team discovered through research that “30% of new users abandon the tutorial midway.” Behavioral observation identified the tutorial was too long. After shortening it, new user retention improved by 50%.

Medical SaaS EHR Workflow Improvement A medical records system developer conducted physician behavior observation research. They discovered “physicians spend more time entering patient data than expected.” Redesigning data entry order and implementing default values reduced physician daily work time by an average of 30 minutes.

Benefits and considerations

User research’s greatest benefit is bridging the gap between team assumptions and reality. This allows design errors to be discovered and corrected before full development, preventing costly rework. Additionally, sharing user voice across the organization aligns different departments’ priorities.

However, user research requires time and budget. Rushing conclusions without sufficient research yields unreliable results. Interpreting findings requires skill and experience to avoid statistical errors and personal bias. Finally, understanding that “users shouldn’t implement everything they suggest” is critical. True user needs often lie beneath surface statements and emerge only through integrating multiple information sources.

Related terms

• UX Design — User experience design rooted in user research
• Usability Testing — A form of user research for design validation
• Persona — Representative user archetypes created from research findings
• Customer Journey Map — Visualizing behavior flows discovered through research
• Prototyping — Creating prototypes based on research findings for revalidation

Frequently asked questions

Q: How much user research should be done before full development? A: At minimum, 5-10 user interviews and basic access log analysis (for existing products) are recommended. Even with limited budget, qualitative research alone can be completed quickly. “Limited but conducted research” always outperforms “no research” in post-launch satisfaction.

Q: What if what users say contradicts their actual behavior? A: This happens often. Users don’t fully recognize their own behavior. When interview statements conflict with behavioral observation, trust the observation. Prioritize “what users do” over “what users say.”

Q: Can external research firms conduct user research? A: Yes. However, the product team should lead in interpreting findings and applying them to development. Simply receiving results without active team participation limits organizational understanding. Collaborating with external firms while having team members participate in the “understanding users” process builds organizational capability.