You Don't Need to Be a Researcher

Many new PMs feel intimidated by user research. They think it requires specialized training, formal protocols, and dedicated researchers. While having a research partner is fantastic, PMs need to be able to do lightweight research on their own.

The goal isn't statistical validity. The goal is *reducing uncertainty.* Even a handful of conversations with real users will make your product decisions dramatically better than pure intuition.

The Two Types of Research

Generative Research — Used when you're trying to understand a problem space you don't fully know yet. You're exploring. - Goal: Learn what problems users have, what their mental models are, what their context looks like. - Methods: Semi-structured interviews, diary studies, contextual inquiry. - When to use: Early in discovery, when you're figuring out what to build.

Evaluative Research — Used when you have a hypothesis or prototype and want to know if it works. - Goal: Test a specific design or concept against user needs. - Methods: Usability testing, A/B testing, concept testing, first-click testing. - When to use: Later in discovery and during development, when you want to validate a solution.

The User Interview: Your Most Powerful Tool

A well-run user interview is worth more than a 500-response survey. Why? Because it lets you go three questions deep. You can follow up. You can ask "why."

The 5 rules of a good user interview: - Ask about the past, not the future. "What do you do when X happens?" not "Would you use a feature that did Y?" People are terrible at predicting their own future behavior. - Never lead the witness. "Don't you find it frustrating when…?" is leading. "How do you feel about that experience?" is neutral. - Embrace silence. After an answer, wait. The most interesting things come after the first thing people say. - Follow the emotion. If someone's voice changes, if they laugh or sigh — that's a signal. "You laughed when you said that — what's going on there?" - Don't pitch your solution. You're here to learn, not to sell.

Surveys: When and How to Use Them

Surveys are better for quantifying what you already know qualitatively. Use them after interviews to understand scale and frequency, not before.

• Good uses: Validating which problem from a shortlist is most common, measuring satisfaction (NPS, CSAT) over time, screening participants for future interviews.
• Common mistakes: Leading questions, double-barreled questions ("Is the product fast and easy to use?"), using surveys to test concepts.

Usability Testing: Watching People Use What You Built

Usability testing is evaluative. You put a prototype or live product in front of users and watch them complete tasks. You say almost nothing. You observe.

• Where do people hesitate or get confused?
• Where do they go that you didn't expect?
• What do they misunderstand about your interface?

You don't need a lab or a big budget. A Figma prototype and a Zoom call is enough. Five users will reveal the majority of usability problems in most interfaces.

Analytics: What Users Do vs. What They Say

Qualitative research tells you *why*. Analytics tells you *what*. You need both.

• Funnel conversion rates — where do users drop off in a key flow?
• Feature adoption rates — what percentage of users actually use the features you've built?
• Retention curves — how quickly do new users fall off after signing up?
• Session recordings (Hotjar, FullStory) — watching real sessions is like a passive usability test

The classic mistake is optimizing analytics without ever talking to users. You'll find patterns in the data, but you won't understand *why* they exist. Research fills in the why.

Building a Research Practice as a New PM

You don't need a formal research program. You need a habit.

• Set a goal of 2–3 user conversations per week, even 20 minutes each.
• Create a shared notes document where you capture quotes and observations after every call.
• After 5–6 conversations on a topic, look for patterns — what are the recurring themes?
• Use those themes to challenge the assumptions in your roadmap.

Key Takeaway: User research isn't a department — it's a habit. Interviews reveal the *why*, surveys quantify the *what*, usability tests show *where things break*, and analytics show *what users actually do*. Use all four, and keep talking to customers every week.