Ten books that take you from a first customer conversation to findings a stakeholder will act on.
User research is a set of distinct skills rather than one activity, and most teams are strong at one of them and thin on the rest. This list starts with interviewing, because it is the skill that quietly improves every other method you use, then moves through planning and method choice, evaluative testing, and the analysis that turns a pile of transcripts into something a team can act on. The last few are references you keep on a shelf and open when a specific question arrives.
Portigal on the craft itself, covering rapport, silence, follow up and asking for stories rather than opinions. Everything else on this list depends on getting the conversation right, so start here.
Two hours of reading that fixes the most common research error, which is asking people about your idea instead of about their life. Fitzpatrick also covers how to deflect praise back into evidence and how to end a conversation that has gone nowhere.
Hall on choosing a method that fits the question and running it yourself rather than waiting for a specialist. She is direct about how much evidence is actually enough, which is the judgement most teams lack.
Turns research from an occasional project into a weekly rhythm, with the opportunity solution tree holding the findings together between rounds. Read it when your problem is frequency rather than technique.
Young separates listening from asking, and the listening session she describes surfaces how someone reasons rather than what they think of your product. The skill it teaches is what makes a transcript worth analysing later.
A reference of 125 methods, each on a two page spread, indexed by phase and by whether it is generative or evaluative. Reach for it during planning, when the question is unfamiliar and interviews are the wrong instrument.
The thorough account of running a usability test, from writing tasks that do not lead the participant through to moderating without helping. Useful when you have to defend how you ran a study as well as what it found.
Sharon organises the whole book around the questions product teams ask rather than around methods, so you look up the decision in front of you and find the research that answers it. Written for people working inside a delivery cycle.
Where research meets an analytics team that wants confidence intervals. Sauro and Lewis cover sample sizes, comparing two designs, and the standardised questionnaires including the System Usability Scale.
The most detailed treatment of the analysis step, which is the step most teams skip. Young's diagram of what people are trying to accomplish stays useful long after the interface it informed has been redesigned.