User Research - Nikki Anderson

User research is a practical, mostly qualitative discipline focused on understanding real people’s pain points, motivations, and behaviors so product teams can make better decisions. In practice, it means going to the target users of a website, app, or service and gathering evidence through methods like interviews and usability testing—then translating what’s learned into actionable guidance for product managers, designers, developers, and business stakeholders.

A key point is that user research isn’t limited to “small-sample” insights or purely qualitative work. While the core work often relies on qualitative methods (especially generative/discovery interviews), it can also incorporate quantitative approaches when the business needs them—such as surveys, A/B testing, and analytics tools like Google analytics and Firebase. The most effective teams increasingly blend both through “mixed methods,” rather than treating qualitative and quantitative as separate camps.

Common methods span the spectrum from discovery to evaluation. Interviews—often grouped under labels like generative research, discovery research, or listening sessions—help uncover what users are trying to achieve and why they behave the way they do. Usability testing evaluates prototypes (early skeletons of interfaces) to see where people struggle. Card sorting helps map how users mentally organize content by having participants sort labeled cards into categories that “make sense” to them; the goal is to align navigation and information architecture with user expectations. Journey mapping and concept testing show up as additional tools, especially when teams need to reason about experiences over time or validate ideas before building.

User research also extends beyond digital products. While the focus here is often on apps and websites, research can apply to physical spaces and services. Service design research examines how people move through environments—such as museums—where signage, information placement, and pathways shape whether the experience feels intuitive. Ethnography and contextual inquiry can capture how people behave in real settings, not just in controlled testing.

The conversation draws a sharp contrast between user research and academic research. Academic-style research can be slow and overly process-heavy for fast-moving product development, where decisions must fit existing company workflows. There’s also a perceived cultural gap: user research often isn’t taught in academia, even though many practitioners come from social science backgrounds like psychology or anthropology. Within industry, some researchers advocate for stricter, academic-like protocols and statistical rigor, while others argue user research should not mimic academia because the goals and constraints differ.

Finally, the path into user research is framed as practice-first. People often enter through adjacent roles such as research assistant, recruiter, or internship positions that build hands-on skills like recruiting participants, note-taking, and synthesizing findings. For career changers, transferable research skills matter, but hiring teams also expect familiarity with product development realities—agile vs. waterfall, design thinking, and the ability to produce work products like a portfolio. One practical strategy described: building portfolio case studies by testing an existing app (even personally) and documenting what was learned, since theory alone can be hard to apply in interviews. The work itself is presented as highly collaborative and iterative—proposal discussions, budgeting, recruiting, and then sharing insights through meetings and workshops—aimed at reducing user stress and improving how products help people get from point A to point B.