Secondary Research: The Complete Guide to Desk Research for Product and UX Teams

Bottom line: Secondary research (also called desk research) is the practice of gathering insights from existing data sources — industry reports, academic studies, competitor publications, analytics, and internal documents — before conducting primary research. Done well, it saves weeks of redundant effort, focuses your interviews on genuine unknowns, and makes your primary research dramatically more productive.

Every research project should start with secondary research. Not because it replaces talking to users — it does not — but because it tells you what is already known so you can focus your user interviews on what is not.

What Is Secondary Research?

Secondary research is any research that analyzes or synthesizes data originally collected for a different purpose. You are not generating new data — you are extracting insights from existing sources.

It is called "desk research" because historically you could conduct most of it without leaving your desk (as opposed to fieldwork, which requires going out to observe and interview real people in their context).

The fundamental distinction:

Types of Secondary Research Sources

Internal sources — data your organization already has:

• Product analytics and behavioral usage data
• Previous research studies and synthesis reports
• Customer support ticket logs and recurring themes
• Sales call recordings, win/loss notes, and CRM data
• NPS and CSAT survey verbatims
• Onboarding and activation funnel data
• Customer success team knowledge

External sources — data available outside your organization:

• Industry analyst reports (Gartner, Forrester, IDC, Nielsen)
• Academic research papers and peer-reviewed journals
• Government statistics and public datasets
• Competitor blogs, case studies, help documentation, and job postings
• App store reviews, G2, Capterra, and Trustpilot reviews
• Online communities (Reddit, LinkedIn groups, industry Slack communities, forums)
• News coverage, press releases, and earnings call transcripts

Why Secondary Research Comes Before Primary Research

The argument for starting with secondary research is straightforward: do not ask questions you already know the answers to.

When product teams skip secondary research and go straight to interviews, they routinely spend time asking questions that have already been thoroughly answered in existing reports, confirming obvious hypotheses rather than uncovering new ones, and missing important context that would have changed the direction of their research entirely.

According to Nielsen Norman Group: "Secondary research in UX tells the team what is already known, surfaces existing answers, and points the primary work toward the gaps that still matter." This is the compounding effect of good desk research — it does not just save time; it improves the quality of everything that follows.

Consider two researchers preparing to study enterprise software adoption:

Researcher A (skipped secondary research): Spends the first 5 interviews asking about the general buying process, rediscovering well-documented patterns about committee decisions and procurement involvement.

Researcher B (completed secondary research): Knows committee buying is already well-documented. Asks focused questions about the specific friction points in the technical evaluation phase — a gap she identified in the literature — and surfaces insights no existing report contains.

Researcher B produces more original, more actionable findings with the same number of interviews.

The 5-Step Secondary Research Process

Step 1: Define Your Research Question

Secondary research without a clear question produces interesting but unfocused notes. Be specific: "What do we already know about why enterprise software pilots fail to convert to paid?" produces better desk research than "learn about enterprise buying."

Write your research question at the top of your notes document before you begin searching. Return to it repeatedly to keep your review focused.

Step 2: Identify Your Highest-Signal Sources

Not all sources are equal. Prioritize by credibility and relevance:

• For market behavior and quantitative benchmarks: Gartner, Forrester, IDC, Statista, government datasets
• For UX and user behavior patterns: Nielsen Norman Group, Baymard Institute, academic UX journals
• For competitive landscape: Company blogs, G2/Capterra reviews, LinkedIn job postings (which reveal what competitors are building), changelog pages
• For your own users: Internal analytics, support tickets, previous research reports, sales call notes
• For industry discourse and unarticulated needs: Reddit communities, Slack groups, LinkedIn posts, industry newsletters

Prioritize recent sources. Reports more than two years old may describe a market that has changed substantially.

Step 3: Extract Systematically, Not Passively

Do not just read and highlight. For each source, capture in a structured notes document:

• The key claim or finding
• Source details (author, publication, year, URL)
• Your confidence in the source's rigor (peer-reviewed journal vs. vendor-published report vs. community post)
• Whether this finding confirms, contradicts, or is silent on your specific research question

Structure matters. You will reference these notes when designing your interview guide, and the structure will determine how usable those notes are.

Step 4: Identify the Three Categories of Information

After reviewing multiple sources, you will see findings fall into three categories:

Well-established: Multiple credible sources agree on this. No need to re-investigate in primary research. Treat as a known assumption at the start of your study.

Contested: Sources disagree, or the evidence is thin and inconclusive. Worth exploring in primary research to understand the disagreement through your specific users' lens.

Unknown / unexplored: Nobody seems to have studied this in the context that matters to you. This is your primary research opportunity — the questions where user interviews can surface genuinely original insight.

Your interview guide should focus primarily on contested and unknown topics. This is how secondary research directly improves the quality and originality of your primary research.

Step 5: Write a Secondary Research Summary

Before beginning primary research, write a 1–2 page synthesis document that includes:

• Key established facts relevant to your question
• Hypotheses that emerged from the secondary research
• Specific gaps that primary research will address
• Revised scope for primary research based on what you learned

Share this with stakeholders before primary research begins. It demonstrates rigor, surfaces misaligned assumptions early, and sets realistic expectations for what primary research will and will not answer.

When Secondary Research Is Not Enough

Secondary research has significant limitations that make primary research essential, not optional:

It covers averages, not your users: Industry reports describe markets. They do not describe your specific users in your specific product context. A report stating that "60% of enterprise buyers involve IT in the purchase decision" does not tell you whether your buyers do — or what specifically triggers IT involvement in your category.

It lags behind reality: Published reports typically reflect data collected 6–18 months before publication. Fast-moving markets — AI tools, consumer platforms, emerging categories — can change dramatically in that window.

It cannot answer behavioral questions at depth: Secondary data tells you what happened. Only primary research can tell you why, and in enough depth to act on it. "Users abandon checkout at the payment step" is visible in your analytics. Why they abandon requires a conversation.

It reflects what people publish, not what they experience: Organizations publish case studies of their successes, not their failures. Online reviews over-represent extreme experiences (delighted or furious). Job postings reflect aspiration, not current reality. Secondary data has systematic selection biases that primary research must correct.

It cannot surface unarticulated needs: By definition, secondary research only reveals what is already known. If you need genuinely novel insight — understanding a new user segment, discovering jobs-to-be-done that nobody has named yet, validating a hypothesis nobody has tested — only primary research delivers.

Secondary and Primary Research in Practice: A Product Discovery Example

Here is how a product team might combine secondary and primary research for a new feature decision:

Research question: Should we build a native analytics dashboard, or integrate with existing tools?

Secondary research phase (2–3 days):

• Review internal analytics: how many customers have connected third-party integrations?
• Read Gartner and Forrester reports on the analytics tool market in this category
• Review G2 and Capterra competitor reviews: what do users say about analytics in similar products?
• Search relevant Reddit communities: what do practitioners say about analytics workflows?
• Review competitor job postings: are they hiring data engineers? (signals investment direction)

Synthesis: Secondary research reveals that third-party integration adoption is low industry-wide, but G2 reviews consistently mention that built-in analytics lack the export/sharing capabilities practitioners need. The gap: nobody has studied specifically how teams share insights with non-technical stakeholders.

Primary research focus: Rather than asking broad questions about analytics needs, the interview guide focuses specifically on the insight-sharing and reporting workflow — a gap identified through secondary research. This produces original findings in a fraction of the interviews it would have taken without the prior context.

How Modern AI Research Tools Eliminate the Speed Gap

One historical argument for prioritizing secondary research over primary was speed: you could review five reports in a day, but scheduling and conducting five user interviews took a week.

That asymmetry has largely been eliminated by AI-moderated research platforms.

With Koji:

• Launch an interview study in under 30 minutes
• Interviews run asynchronously — participants complete them when it is convenient for them, 24/7
• AI-generated thematic analysis is available within hours of the last interview completing
• Structured questions across Koji's 6 question types (open-ended, scale, single choice, multiple choice, ranking, and yes/no) capture both qualitative depth and quantitative benchmarks in a single session

The result: primary research now takes roughly the same calendar time as thorough secondary research. Teams no longer face a meaningful trade-off between the two methods — they can run both in tight sequence.

A modern integrated research workflow:

1. Day 1: Define research question. Identify top 5–8 secondary sources.
2. Days 2–3: Review and synthesize secondary sources. Identify gaps.
3. Day 3: Configure a Koji study targeting the specific gaps. Write structured questions using Koji's 6 question types to capture both qualitative themes and quantitative benchmarks.
4. Days 4–7: Interviews run asynchronously. Participants complete sessions at their convenience.
5. Day 7: Review AI-generated thematic analysis, read standout transcripts for quotes.
6. Days 8–9: Synthesize secondary + primary findings into recommendations.

Total cycle time: approximately 9 days for a complete, defensible research project with both secondary context and primary user evidence.

Key Secondary Research Sources to Bookmark

For product and UX researchers, these sources consistently deliver high-signal secondary data:

Related Resources

• Structured Questions in AI Interviews — How to design primary research using Koji's 6 question types to fill the gaps secondary research reveals
• User Interview Guide — The complete guide to conducting primary user interviews
• Product Discovery Research Guide — How to integrate secondary and primary research across the full product discovery process
• Research Brief Template — How to document secondary research findings and define primary research scope
• How to Analyze Qualitative Data — Systematic analysis frameworks for making sense of primary research data
• Generative Research Guide — When and how to use primary generative research to surface unarticulated user needs