The User Research Handbook

Any product manager who needs to understand users directly rather than through secondhand anecdotes: PMs without dedicated research support, PMs who partner with a research team but still run their own interviews, and founders having their first customer conversations. It assumes no formal research training and no research budget.

The Product Discovery Handbook (at /discovery-guide) covers the discovery process: opportunity mapping, assumption testing, and running dual-track agile. This handbook is about the craft underneath that process: how to actually choose a method, run an interview, design a survey, test usability, and synthesize what you learn into insight. Read the Discovery Handbook for how to structure a discovery practice, and this handbook for how to do the research itself well.

Chapters 1 and 2 (why research gets skipped, and how to choose a method) are worth reading first since later chapters assume that framing. After that, go straight to what you need: recruiting and interview scripts in Chapters 3 and 4, surveys in Chapter 5, usability testing in Chapter 6, Jobs-to-be-Done in Chapter 7, and synthesis in Chapter 8.

It depends on the goal, not a fixed number. For usability testing within one user segment, five participants surface most of the findings in a given flow (see Chapter 6). For open-ended generative interviews about a new problem space, most teams start seeing repeated patterns somewhere between five and twelve conversations, though a genuinely diverse market may need more. The better habit is continuous interviewing on a weekly cadence (Chapter 4) so you're never relying on a single one-off batch.

Qualitative research (interviews, usability tests) tells you why and surfaces problems you didn't know to ask about. Quantitative research (surveys, analytics) tells you how many and how often, across a much larger sample. Neither replaces the other. Chapter 2 covers how to choose based on your decision, and most high-stakes decisions benefit from triangulating both: qualitative to explain, quantitative to size.

No. Every method in this handbook, including recruiting, screeners, interview scripts, survey design, and usability testing, is written for a PM running research without specialist support. Chapter 11 covers how to build the lightweight operations (panels, repositories, consent basics) that make this sustainable without a dedicated research operations team.

Start with customer interviews. They are the lowest-cost, highest-signal method for understanding problems you don't yet know how to frame as a survey question, and Chapters 3 and 4 give you the recruiting and scripting to run them well with no budget beyond your own time.

Yes. Every interview script, screener structure, severity scale, and synthesis template in this handbook is meant to be copied and adapted for your own product and team. No attribution required.

The handbook is entirely free to read online, no account or email required. There is no downloadable PDF version yet. The web version stays current and links directly to the interactive tools and frameworks referenced throughout.