Content Marketing Glossary

  • What is User Research?

What is User Research?

User Research

User Research is the discipline of systematically studying users - who they are, what they’re trying to do, what’s getting in their way, how they think about the problems the product addresses - to inform product, design, and marketing decisions with evidence rather than assumption. Good user research doesn’t produce answers; it produces useful questions and constraints that sharpen every downstream decision. Teams that skip it don’t avoid research; they just do it implicitly, based on their own assumptions, and those assumptions are reliably wrong in specific costly ways.

The two broad families of user research

Generative research. Aimed at understanding what’s true, what matters, and what problems exist. Open-ended. Produces insights, themes, persona material, and a better problem statement than the team started with. Feeds strategy and early product decisions.

Evaluative research. Aimed at answering specific questions about a specific design, prototype, or existing product. Focused. Produces yes/no decisions, rank-ordered priorities, and concrete usability fixes. Feeds product iteration.

Mature teams run both continuously. Early-stage teams often skip generative in favour of evaluative, then wonder why evaluative findings don’t produce strategic clarity.

Common user research methods

Seven methods that cover most practical needs:

In-depth interviews. One-on-one, 30–60 minutes, semi-structured conversation with a target user. Produces rich narrative understanding. The workhorse of generative research.

Usability testing. Ask a user to complete specific tasks on a product or prototype while observing. Produces concrete evidence of where the product breaks down. The workhorse of evaluative research.

Contextual inquiry and field research. Observing users in their actual environment, doing the work they actually do. Expensive; produces insights about context and workflow that interviews and usability tests miss.

Diary studies. Users log their activity over 1–4 weeks, documenting interactions with the product or the problem space. Useful for behaviours that don’t appear in single-session observation.

Surveys and questionnaires. Reach larger sample sizes than qualitative methods. Weaker on nuance; stronger on pattern confirmation. See questionnaire for the craft of writing them well.

Analytics review and behavioural data. What users actually do, at scale. Complementary to qualitative methods - analytics reveals patterns, qualitative research reveals why.

Card sorting and tree testing. Methods specific to information architecture and navigation design. Users group content or locate items within a proposed structure; the data reveals how to organise content.

How to structure a user research programme

Four practical disciplines:

Research questions, not just methods. A study without a clear question (“what blocks users from completing checkout?”) produces diffuse findings. A study with a clear question produces actionable ones.

Recruitment discipline. The participants’ profile determines what the research reveals. Five carefully-recruited target users are more useful than 50 random respondents. Budget for recruitment, use screeners, compensate participants fairly.

Synthesis, not just reporting. Raw interview transcripts aren’t insights. The team needs a synthesis step - clustering themes, identifying tensions, producing reusable artefacts (personas, journey maps, design principles). Research without synthesis decays; synthesis is where the value compounds.

Distribution and activation. Research that sits in a PDF nobody reads doesn’t change decisions. Findings need to travel - via presentations, wiki articles, design-system integration, and ongoing mention in sprint planning. If engineers, designers, and marketers can’t recall the key insights three months later, the programme isn’t working.

Where user research goes wrong

Five common failure modes:

Treating research as validation. The team has already decided; they’re running research to defend the decision. Leading questions, selective listening, confirmation-biased synthesis. Produces the opposite of what research should.

Researching without a hypothesis. The team doesn’t know what they think; they hope research will tell them. Research is better at testing hypotheses than at generating them from scratch. Starting with “we think X because Y; we’re testing whether that’s true” produces sharper studies.

Under-recruiting target users. Researching with “anyone who’ll participate” rather than actual target users. Findings apply to the participants, not to the real audience. Costly to rerun.

Over-recruiting existing customers. Existing customers already adopted the product; they’ve self-selected for fit. Research exclusively with them misses the prospects who didn’t adopt, which is usually where growth insight lives.

Not closing the loop. Research finds a problem; team doesn’t build the fix; or builds the fix but never re-tests whether it actually resolved the problem. Without the loop, research credibility erodes and teams stop investing in it.

User research and marketing

Three ways research shows up in marketing work:

Buyer persona development. Research-grounded personas beat assumption-based ones by a wide margin. Real interviews with real target customers produce persona detail that marketing actually uses.

Positioning and messaging. The words customers use to describe their problems are rarely the words the product team uses. Research captures customer language, which directly improves positioning and ad copy. See target audience for the related marketing frame.

Content strategy. What questions do prospects actually ask before buying? What objections? What research paths? User research produces content roadmaps grounded in demand, not invention.

Related terms