User Research

Core Philosophy

User research replaces assumptions about customers with evidence. It is the systematic study of who users are, what they need, how they behave, and why they make the choices they do. Good research does not just validate ideas — it reveals needs and opportunities that the team would never have identified on its own. The most expensive mistakes in product development come from building the wrong thing, and research is the cheapest way to avoid them.

Key Techniques

• User Interviews: One-on-one conversations that explore user goals, workflows, frustrations, and context. Open-ended questions reveal mental models and unmet needs that surveys cannot capture.
• Usability Testing: Observing users as they attempt tasks with the product to identify friction, confusion, and failure points in the interface.
• Surveys: Structured questionnaires for gathering quantitative data at scale about preferences, satisfaction, and demographics.
• Contextual Inquiry: Observing users in their natural environment to understand how they actually work, not how they say they work.
• Diary Studies: Users self-report their experiences over days or weeks, capturing longitudinal behavior that single-session methods miss.
• Card Sorting: Users organize content or features into categories, revealing their mental models for information architecture.

Best Practices

• Talk to users regularly, not just at project kickoff. Continuous research prevents drift from customer reality.
• Recruit participants who represent actual target users, not internal stakeholders or convenience samples.
• Ask about past behavior, not hypothetical future behavior. People are poor predictors of what they will do.
• Separate research from sales or support conversations. Users behave differently when they think they are being sold to.
• Synthesize findings into actionable insights, not just raw notes. Pattern recognition across interviews is where value emerges.
• Share research widely with the team through video clips, insight repositories, and regular research readouts.

Common Patterns

• Discovery Research: Broad, exploratory research at the beginning of a project to understand the problem space before defining solutions.
• Evaluative Research: Testing specific designs or prototypes to validate assumptions before engineering investment.
• Continuous Discovery: Weekly customer touchpoints integrated into the team's rhythm, maintaining constant contact with user reality.
• Mixed Methods: Combining qualitative interviews (why) with quantitative analytics (what and how much) for a complete picture.

Anti-Patterns

• Asking users what they want rather than understanding what they need. Users request solutions; researchers uncover problems.
• Conducting research but ignoring findings that conflict with existing plans.
• Testing with too few participants for quantitative conclusions or too many for qualitative depth.
• Leading questions that confirm the researcher's hypothesis rather than exploring the user's reality.
• Treating personas as fixed artifacts rather than living models updated with new research.
• Researching only existing users and missing the needs of potential users who churned or never adopted.