How to set up a continuous discovery cadence when your company only has one dedicated researcher

Being the only dedicated researcher at a company comes with a familiar tension. Leadership wants customer insights to inform product decisions across multiple teams. Product managers have questions. Designers want to validate concepts. And you are one person.

Project-based research—scoping a study, conducting it, delivering a report, then moving to the next request—can feel like the only realistic option when resources are limited. But this approach creates gaps. Between projects, teams make decisions without fresh customer input. Insights age quickly, and by the time a report is delivered, priorities may have already shifted.

Continuous discovery offers a different model. Instead of treating research as a series of discrete projects, it embeds ongoing customer contact into the regular rhythm of product development. The challenge is making this work when the entire research function is one person.

This article covers how to design a continuous discovery cadence that is sustainable for a solo researcher, how to involve product teams without burning out, and where to focus your limited time for maximum impact.

Why continuous discovery matters more when you're solo

When there is only one researcher, the bottleneck risk is severe. If every customer insight must pass through a single person's project queue, most product decisions will be made without research input. Teams will either wait—slowing down their work—or proceed without evidence.

A continuous cadence reduces this bottleneck in two ways. First, it produces a steady stream of lightweight insights that teams can draw on without waiting for a full study to complete. Second, it creates structures that enable non-researchers to participate in discovery, extending the reach of the research function beyond what one person could accomplish alone.

Continuous discovery also changes the nature of the insights you generate. Project-based research answers specific questions well but often misses the broader patterns that emerge only through sustained contact with customers over weeks and months. A regular cadence surfaces recurring themes, shifting needs, and emerging problems that a one-off study would not catch.

Assess your starting conditions

Before designing a cadence, take stock of what you are working with.

Map the teams you support

List every product team, squad, or initiative that expects research input. For each, note how frequently they currently receive customer insights, what kinds of decisions they are making, and how much appetite they have for participating in discovery themselves. This map reveals where the demand is highest and where you are most likely to find willing collaborators.

Understand your time budget

Be honest about how your time breaks down today. Most solo researchers spend significant hours on stakeholder management, recruitment logistics, and synthesizing and sharing findings—not just conducting research. If interviews take 60 minutes each but scheduling, note-taking, synthesis, and sharing add another two to three hours per interview, your realistic weekly capacity is lower than it might appear.

Identify existing customer touchpoints

Your company likely has customer conversations happening that are not labeled as research. Sales calls, customer success check-ins, support tickets, onboarding sessions, and NPS follow-ups all contain discovery-relevant information. Understanding what already exists helps you decide where to build new touchpoints and where to tap into existing ones.

Design your weekly cadence

A sustainable cadence for a solo researcher has three components: regular customer contact, dedicated synthesis time, and structured sharing.

Customer contact: two to three interviews per week

This is the core habit. Two to three interviews per week—each lasting 30 to 45 minutes—gives you enough signal to identify patterns without consuming all your available hours. These are not full usability studies or in-depth ethnographic sessions. They are short, focused conversations guided by the opportunity space your teams are currently exploring.

To keep interviews productive across multiple teams, maintain a rolling set of questions organized by theme. You might spend two weeks focused on onboarding pain points, then shift to questions about a workflow that a specific product team is redesigning. Alternately, you can structure each interview to cover a broad opening question ("What has been frustrating about your work this week?") followed by targeted follow-ups tied to active product initiatives.

The key constraint is consistency. Three interviews every week for three months produces far more useful insight than ten interviews crammed into a single sprint followed by six weeks of silence.

Synthesis: two focused sessions per week

Raw interview notes lose value quickly if they sit untouched. Block two 60-to-90-minute synthesis sessions per week—ideally within 24 hours of your interviews. During synthesis, you are doing three things:

1. Tagging and organizing observations. Identify discrete insights, quotes, and behavioral observations from each interview and categorize them by theme or opportunity area. Tools like Dovetail can speed this process significantly by letting you tag transcript passages and see patterns accumulate across interviews over time.

2. Updating your opportunity map. Maintain a living document—whether it is an opportunity solution tree, a simple spreadsheet, or a board in your project tool—that captures the customer needs, pain points, and desires you are hearing about. Each synthesis session should refine this map: strengthening themes with additional evidence, adding new ones, or retiring themes that are not holding up.

3. Flagging urgent signals. Sometimes an interview surfaces something that a product team needs to hear immediately—a workaround that reveals a critical usability problem, or a competitive threat that was not on the radar. Flag these for same-day sharing rather than waiting for the regular cadence.

Sharing: a weekly rhythm with lightweight artifacts

Insights that stay in the researcher's notebook do not influence decisions. Build a weekly sharing ritual that is low-effort for you and high-value for your stakeholders.

Weekly insight digest. A short written summary—no more than one page—sent to product and design leads every week. Include the top three to five observations from that week's interviews, relevant customer quotes, and a note on how these relate to active product initiatives. Keep the format consistent so people learn where to look.

Bi-weekly or monthly insight reviews. A 30-minute meeting where you walk stakeholders through the patterns building up over multiple weeks. This is where the cumulative power of continuous discovery becomes visible. Individual interviews may seem incremental; the patterns across 10 or 20 interviews are often compelling.

Clip and quote sharing. Short video or audio clips from interviews—two minutes or less—are far more persuasive than written summaries for many stakeholders. If you are recording interviews with participant consent, pulling key moments and sharing them in Slack or your team's communication tool takes minutes and has outsized impact.

Scale your reach by enabling others

A solo researcher who tries to personally handle all discovery for every team will burn out. The more sustainable path is to treat your role as part practitioner, part coach.

Identify research partners on each team

Look for product managers or designers who are curious about customers and willing to invest time. These are your research partners. You do not need every PM to become a skilled interviewer—one or two willing collaborators can dramatically extend your capacity.

Provide lightweight toolkits

Create simple, reusable resources that make it easy for non-researchers to run basic discovery conversations:

• A one-page interview guide template with example opening questions and prompts for going deeper
• A do's and don'ts sheet covering common mistakes like leading questions, confirmation bias, and talking more than listening
• A tagging guide so observations from PM-led interviews use the same categories you are tracking in your central repository

Offer office hours, not gatekeeping

Instead of requiring that all research requests go through a formal intake process, hold weekly office hours where anyone can bring a question, discuss an upcoming interview, or ask for feedback on a prototype test plan. This positions you as an enabler rather than a gatekeeper and makes it more likely that teams will involve you early rather than skipping research entirely.

Centralize everything in one place

When multiple people are contributing observations, having a single source of truth for customer insights is essential. If interview notes, survey results, and tagged observations are scattered across individual notebooks, Google Docs, and Slack threads, patterns are invisible and effort is duplicated. A dedicated research repository—Dovetail is designed for exactly this purpose—gives everyone a place to contribute and search existing insights before starting new research from scratch.

Manage the tension between continuous and project-based work

Going fully continuous does not mean you never do project-based research. Some questions—like evaluating a complex new workflow, running a diary study, or conducting a competitive usability benchmark—require dedicated time and structured methodology.

The practical approach is to allocate your time roughly as follows:

• 60–70% continuous discovery: Weekly interviews, synthesis, and sharing
• 30–40% project-based research: Deeper studies aligned with major product initiatives

Protect your continuous cadence fiercely. It is tempting to pause weekly interviews when a big project study ramps up, but every pause makes it harder to restart. If a project study requires your full attention for a week, reduce your interview count rather than dropping to zero.

Common pitfalls and how to avoid them

Trying to cover every team equally

You cannot serve six product teams with the same depth when you are one person. Prioritize based on where customer evidence will have the highest impact on upcoming decisions. Rotate your focus across teams over monthly or quarterly cycles so no team is permanently neglected, but accept that coverage will be uneven at any given moment.

Over-investing in deliverables

Polished research reports take hours to produce and are often skimmed. In a continuous cadence, speed and frequency matter more than production quality. A tagged transcript with highlighted quotes that ships today is more useful than a beautifully designed deck that ships in two weeks.

Not saying no

Every stakeholder will have questions they want answered. Without a clear prioritization framework, you will spend your time on whoever asks loudest. Maintain a visible research backlog, prioritized against product strategy, and review it with leadership regularly. This makes trade-offs transparent and gives you a defensible reason when you need to decline or defer a request.

Neglecting your own development

Solo researchers often have no peer to learn from, no one to review their discussion guides, and no sounding board for tricky analytical decisions. Seek out external communities, attend conferences, and if possible, negotiate budget for professional development. Your effectiveness as the sole research voice in the company depends on your continued growth.

What a typical week looks like

To make this concrete, here is a sample weekly schedule for a solo researcher running a continuous discovery cadence:

Monday: Synthesis session from the previous week's final interview. Update opportunity map. Send weekly insight digest to stakeholders.

Tuesday: Customer interview (morning). Debrief notes and initial tagging (afternoon). Office hours for product teams (30 minutes).

Wednesday: Customer interview (morning). Synthesis session (afternoon). Share relevant clips or quotes in team channels.

Thursday: Customer interview or project-based research session. Recruitment and scheduling for the following week.

Friday: Stakeholder check-ins. Backlog review and prioritization. Preparation of interview guides for the following week.

This structure keeps every day anchored to a clear purpose while leaving room for the ad hoc requests and conversations that inevitably arise.

Building the case for growing the team

A well-run continuous discovery cadence produces something valuable beyond customer insights: evidence that research matters. When product teams are regularly receiving and acting on customer evidence, the organizational case for hiring a second researcher becomes much easier to make.

Track and share metrics that demonstrate impact. These might include the number of product decisions informed by research each quarter, how often teams reference customer evidence in planning documents, or specific examples where an insight changed a product direction. Over time, this evidence builds the argument that research capacity is a constraint worth investing in.

Starting with a sustainable, consistent practice—rather than trying to do everything at once—is both the most realistic path for a solo researcher and the strongest foundation for eventually building a team.