03. User Research

User research validates your assumptions before you invest significant time building the wrong thing. This chapter covers lightweight research techniques suitable for a solo project or small team. You do not need a research budget or formal methodology—you need genuine curiosity about the people you intend to serve.

Identifying Interview Candidates

Your target users are not "everyone" or "developers." Be specific. A good user persona describes a person with a name, a job, daily frustrations, and goals. If you cannot visualize a specific person using your product, you are not ready to research.

Find interview candidates through communities where your target users gather: Reddit threads, Discord servers, Slack channels, GitHub issue discussions, or local meetups. Offer value in exchange for their time—a summary of findings, early access, or simply genuine interest in their problems.

Conducting Effective Interviews

Good interviews feel like conversations, not interrogations. Start with open questions: "Tell me about the last time you [experienced the problem]." Listen more than you speak. Ask clarifying questions but avoid leading questions that suggest the answer you want.

Record interviews with permission, take notes, and transcribe key quotes. Patterns emerge after 3-5 interviews. One person mentioning something is an anecdote. Five people mentioning the same thing is a pattern worth addressing.

Survey Techniques

Surveys supplement interviews but cannot replace them. Interviews reveal the why behind behavior; surveys reveal the what and how much. Use surveys to quantify patterns you found in interviews and to reach people you cannot interview directly.

Keep surveys short (5-10 questions, 2-3 minutes to complete). Ask mostly closed questions with optional open-ended follow-ups. Analyze results by looking for surprising patterns, not just averages.

Synthesizing Findings

After research, synthesize your findings into insights that inform decisions. Organize findings by theme, highlight surprising discoveries, and identify contradictions. Your goal is to answer: What do users actually need versus what do they say they want?

A common pitfall is treating all feedback equally. A power user with complex needs might request features that alienate casual users. A single vocal critic might not represent your target audience. Prioritize patterns over individual opinions.

Research Deliverables

Document your research in a research summary that includes participant descriptions, key findings, notable quotes, and implications for your product. This document becomes a reference when making decisions later—it keeps you anchored to actual user needs rather than assumed ones.