User Research

What is User Research?

User research is the systematic study of users and their needs, behaviors, and motivations, using a mix of qualitative and quantitative methods. It is the engine that feeds every other discovery activity with real evidence.

Qualitative vs. Quantitative

• Qualitative (interviews, observation) — answers why and how; small sample, deep insight.
• Quantitative (surveys, analytics) — answers how many/how much; large sample, statistical confidence.

Strong discovery uses both: qualitative research generates hypotheses, quantitative research tests how widespread they are.

Choosing the Right Method

Goal	Best Method
Understand a problem deeply	Interviews, observation
Validate how common a problem is	Surveys, analytics
See real behavior, not self-reported	Observation, usability testing
Test a specific solution	Prototype testing, A/B tests

Research Cadence

Continuous discovery teams aim to talk to customers at least weekly — small, frequent touchpoints beat rare, large research "projects" because they keep evidence fresh and bias-resistant.

Why Interview Users?

Interviews surface the context, motivations, and emotions behind behavior — things surveys and analytics cannot capture.

Writing Good Interview Questions

• Ask about past behavior, not hypothetical future behavior. "Tell me about the last time you..." beats "Would you use a feature that...".
• Avoid leading questions ("Don't you think X is annoying?").
• Avoid solution-focused questions early — focus on problems and current workarounds first.

The Mom Test Principle

Talk about their life, not your idea. If you pitch your solution too early, people will be polite and falsely validate it. Good interviews could be mistaken for a conversation about the user's life, not a pitch.

Running the Interview

1. Build rapport, explain you're there to learn (not sell).
2. Ask open-ended questions, then go silent and let them talk.
3. Follow the energy — dig deeper where they show emotion or hesitation.
4. Ask for specifics: "Walk me through exactly what happened."
5. Don't take the bait when asked "should we build X?" — redirect to their underlying problem.

After the Interview

Write up notes within minutes while memory is fresh, tag insights to share with the team, and look for patterns across multiple interviews rather than acting on a single data point.

When to Use Surveys

Surveys are best for validating the scale of something you've already learned qualitatively — e.g. "we heard 5 users mention X in interviews; what % of our base feels the same?"

Designing Good Surveys

• Keep it short — every extra question lowers completion rates.
• Use closed questions for quantifiable data, with 1-2 open questions for color.
• Avoid double-barreled questions ("Do you find the app fast and reliable?" — two things in one).
• Pilot the survey with a handful of people before wide distribution to catch confusing wording.

Common Pitfalls

• Leading or biased phrasing that nudges a desired answer.
• Sampling bias — only your most engaged users respond, skewing results.
• Over-reliance on surveys alone — they tell you "what" and "how many," rarely "why."

Useful Survey Frameworks

• NPS (Net Promoter Score) — measures loyalty/advocacy with one question.
• CSAT — measures satisfaction with a specific interaction.
• PMF survey (Sean Ellis test) — "How would you feel if you could no longer use this product?" to gauge product-market fit.

What is Observation Research?

Observation (or contextual inquiry) involves watching users perform real tasks in their natural environment, rather than relying on what they say they do. People are often unreliable narrators of their own behavior — observation reveals the gap between stated and actual behavior.

Methods

• Contextual inquiry — observe users at their workplace/home doing real tasks, asking clarifying questions as they go.
• Usability testing — give users a task with a prototype/product and watch them attempt it, without guiding them.
• Diary studies — users log behavior/feelings over time when you can't be present.
• Session replay/analytics — digital "observation" via recorded user sessions or behavioral analytics.

What to Look For

• Workarounds and hacks — strong signals of unmet needs.
• Moments of hesitation, confusion, or frustration.
• The tools and steps people use around your product, not just inside it.

Best Practices

• Observe, don't help — resist the urge to jump in when a user struggles; that struggle is the data.
• Take detailed notes on actions, not just words.
• Combine with a short interview afterward to ask about anything you observed.