How to write a research plan (with a template)
A research plan turns a vague request into a study you can actually run. Here are the seven sections every plan needs, plus a template you can fill in today.
A research plan is a short document that defines why a study is happening, what it needs to answer, how you will collect evidence, who you will talk to, and when the results are due. It exists to align everyone before a single interview is booked or a survey goes live. Write it well and the study runs itself. Skip it and you end up with a pile of transcripts that never point to a decision.
This guide walks through what a research plan is, why it matters, and the seven sections that belong in every one. At the end there is a fillable outline you can copy into a doc and complete in about thirty minutes. It works for UX researchers running usability studies and for product managers scoping their first round of customer interviews.
What a research plan is and why it matters
A research plan is not a survey script or an interview guide. Those are downstream artifacts. The plan sits above them and answers a more basic question: what decision is this research supposed to inform, and how will we know when we have enough to make it?
Without a plan, three failure modes show up again and again. The study drifts, because nobody agreed on the objective, so every conversation wanders somewhere new. Stakeholders disagree with the findings, because they never signed off on the questions and now dispute the scope. And the timeline slips, usually during recruiting, because sourcing the right participants was treated as an afterthought instead of a planned step.
A good plan closes all three gaps up front. The Nielsen Norman Group recommends writing a research plan for exactly this reason: it forces the team to agree on purpose and method before money and calendar time are spent. The document does not need to be long. One to three pages is normal. What matters is that it is specific enough that someone else could pick it up and run the study without a meeting.
If you are still deciding which method fits your question, it helps to review the landscape first. Our complete walkthrough of product research methods covers when to reach for interviews, surveys, usability tests, or diary studies, and the complete guide to user research frames how those methods ladder up to product decisions.
The seven sections of a research plan
Every effective research plan covers the same seven areas. You can rename or reorder them to fit your team, but if one is missing, that is usually where the study breaks down later.
| Plan section | What to include |
|---|---|
| Objective | The decision this study informs, the audience, and the outcome you want. One or two sentences. |
| Research questions | Three to five specific questions the study must answer. Not survey wording, but the things you need to learn. |
| Method | The research method and why it fits, plus format, session length, and number of sessions. |
| Participants and recruiting | Screening criteria, sample size, incentive, sourcing channel, and screener questions. |
| Timeline | Key dates from kickoff to readout, with recruiting called out as its own milestone. |
| Deliverables | What the team gets at the end: a report, a highlight reel, a metrics summary, or a decision memo. |
| Stakeholders | Who owns the study, who reviews it, and who acts on the findings. |
Below, each section in detail.
1. Objective
The objective is the spine of the plan. Everything else hangs off it. A strong objective names three things: the decision the team faces, the audience it concerns, and the outcome you want from the study.
Weak: “Learn more about how people use the dashboard.”
Strong: “Decide whether first-time admins can complete self-serve onboarding without support, so we can remove the guided setup call before the Q4 launch.”
The difference is a finish line. The strong version tells you when you are done and what a useful answer looks like. If your objective could describe any study your team might ever run, it is too broad. Tie it to a decision with a date attached. Our guide on turning product research into better product decisions goes deeper on writing objectives that connect research to a real choice rather than general curiosity.
2. Research questions
Research questions are the specific things you need to learn to serve the objective. Aim for three to five. Fewer and the study may be too shallow to be worth running. More and you are probably trying to answer several objectives at once, which is a sign to split into separate studies.
Keep research questions distinct from interview questions. Research questions are what you need to know. Interview questions are what you actually ask a participant. For example, a research question might be “Where do first-time admins get stuck during setup?” while the matching interview prompt is “Walk me through the last time you set up a new workspace, step by step.” If you need help translating research questions into good prompts, our list of 50 user interview questions that uncover real insights is a practical starting point.
3. Method
The method section states how you will gather evidence and why that approach fits the question. Match the method to what you need to learn. Behavioral questions about whether people can complete a task call for usability testing. Questions about motivation and context call for interviews. Questions about how common something is across a population call for a survey.
Be concrete. Name the method, the session format, how long each session runs, and how many sessions you will run. “Six moderated remote usability sessions, forty-five minutes each, using a clickable prototype” is a method someone can execute. “Some user testing” is not. If your study crosses methods, say how they connect, for example a survey to size a problem followed by interviews to understand it. For B2B products specifically, the B2B user research playbook covers method choices that account for gatekeepers, buying committees, and hard-to-reach professional audiences. For market-facing studies, the market research methodology guide walks through quantitative and qualitative trade-offs.
4. Participants and recruiting
This is the section where plans most often fall apart, so it deserves the most detail. Recruiting is almost always the longest and least predictable part of a study. Teams routinely scope a two-week study and then spend three weeks trying to find qualified people. A plan that treats recruiting as one line at the bottom is a plan that will slip.
Define five things:
- Screening criteria. The exact profile that qualifies someone. Role, seniority, company size, tools they use, behaviors they exhibit. Be specific enough to exclude the wrong people.
- Sample size. How many participants, and why. Qualitative studies often need five to eight per segment. Surveys need a target that supports the analysis you plan.
- Incentive. What you will pay, and how it is delivered. Under-paying is a common reason recruiting stalls, especially for senior or specialized audiences.
- Sourcing channel. Where participants come from. Your own users, a panel, or outreach. This choice drives your timeline more than any other.
- Screener questions. The two or three questions that confirm someone matches the criteria before you book them.
The sourcing choice is where timelines live or die. Recruiting from your own user list is cheap but slow and biased toward engaged customers. Cold outreach is precise but painfully slow for niche B2B roles. A verified panel removes most of the uncertainty because the qualified people are already there and identity-checked.
This is where CleverX fits. CleverX is a B2B research platform with more than 8 million verified professionals, plus B2C reach, across 150 or more countries. You define screening criteria, and qualified, identity-verified participants are delivered in roughly two to five days on a pay-as-you-go basis, so you are not locked into a subscription for a single study. Because the panel is verified, you skip the biggest source of delay and the biggest source of bad data, which is people who misrepresent their role to qualify for the incentive.
For a deeper look at getting this section right, see our guides on participant recruitment and finding quality participants and, for professional audiences specifically, how to recruit B2B research participants.
5. Timeline
The timeline maps the study from kickoff to readout. List the milestones with dates: plan approved, recruiting starts, first session, last session, analysis, and final readout. Call out recruiting as its own explicit milestone rather than folding it into fieldwork, because that is the step most likely to run long.
A realistic timeline for a small qualitative study might look like one week to recruit, one week of sessions, and one week to analyze and report. When you use a verified panel with a two-to-five-day delivery window, the recruiting block shrinks and the whole study compresses. When you rely on ad hoc sourcing, pad the recruiting estimate generously, because it will almost always take longer than you expect.
6. Deliverables
Deliverables state what the team actually receives at the end. Be explicit, because “a report” means different things to different people. Options include a written findings report, a slide summary, a highlight reel of clips, a metrics dashboard for a survey, or a one-page decision memo tied back to the objective.
The best deliverable maps directly to the decision in your objective. If the objective was to decide whether to remove the guided setup call, the deliverable should end with a clear recommendation on that exact question, supported by evidence. Deciding the format in advance also shapes how you take notes and what you capture during sessions. If interviews are your method, our guide on analyzing user interview data shows how to get from raw transcripts to something a stakeholder will act on.
7. Stakeholders
The last section names people. Who owns and runs the study, who reviews the plan before it starts, and who will use the findings to make the decision. Naming the decision-maker matters most. Research that has no clear consumer tends to be ignored, no matter how good it is.
Get the reviewers to sign off on the objective and research questions before recruiting begins. That single step prevents the most demoralizing outcome in research, which is finishing a study only to hear a stakeholder say they would have asked something completely different.
A fillable research plan template
Copy the outline below into a document and fill in the brackets. If you can complete all seven sections in one sitting, the study is scoped well enough to run.
RESEARCH PLAN: [Study name]
Author: [Name] Date: [Date]
1. OBJECTIVE
We are running this study to inform [the decision], concerning [the audience],
so that we can [the outcome] by [date].
2. RESEARCH QUESTIONS
- [Question 1]
- [Question 2]
- [Question 3]
(Add up to two more. Stop at five.)
3. METHOD
We will use [method] because [reason it fits the questions].
Format: [remote/in-person, moderated/unmoderated]
Sessions: [number] x [length]
4. PARTICIPANTS AND RECRUITING
Profile: [role, seniority, company size, tools, behaviors]
Sample size: [number] because [rationale]
Incentive: [amount and delivery]
Sourcing: [own users / verified panel / outreach]
Screener questions:
- [Q1]
- [Q2]
5. TIMELINE
Plan approved: [date]
Recruiting starts: [date]
First session: [date]
Last session: [date]
Readout: [date]
6. DELIVERABLES
The team will receive [format], ending in a recommendation on [the decision].
7. STAKEHOLDERS
Owner: [name]
Reviewers: [names]
Decision-maker: [name]
Common mistakes to avoid
A few patterns show up in weak plans over and over. The objective describes a topic instead of a decision, so the study has no finish line. The research questions are really interview questions, which locks the study into wording before anyone has thought about what they need to learn. Recruiting gets one vague line, and then the whole timeline slips waiting for participants. And no decision-maker is named, so the findings land with no one obligated to act on them.
All four are cheap to fix at the planning stage and expensive to fix later. A plan that survives a quick read from a skeptical stakeholder is worth far more than a polished report on a study nobody asked for.
Put your recruiting plan on solid ground
The single highest-leverage part of a research plan is the recruiting section, because it drives both your timeline and the quality of your evidence. If you scope everything else perfectly but cannot reach the right people, the study stalls. A verified panel is the most reliable way to de-risk that step. You can recruit verified participants on CleverX, define your exact screening criteria, and get qualified professionals in roughly two to five days without a subscription commitment.
Write the plan first, get sign-off on the objective and questions, then recruit against criteria you already agreed on. That order is what turns a research request into a study that actually changes a decision.
Frequently asked questions
What is a research plan?
A research plan is a short document that defines why a study is happening, what it needs to answer, how you will gather evidence, who you will talk to, and when results are due. It aligns stakeholders before any interviews or surveys begin, so the work stays focused on a decision instead of drifting into general curiosity.
How long should a research plan be?
Most research plans are one to three pages. The goal is clarity, not length. If a plan runs longer than three pages, it usually means the scope is too broad and should be split into separate studies. A tight objective and three to five research questions keep the document readable in a few minutes.
What is the difference between a research plan and a research proposal?
A research plan is an internal operating document that guides how a team runs a specific study. A research proposal is usually a persuasive pitch written to secure approval, budget, or funding before work starts. In practice many teams fold the two together, but the plan is the version you actually execute against.
Who should write the research plan?
The person running the study usually writes it, whether that is a UX researcher, product manager, or founder. The plan should be reviewed by the stakeholders who will act on the findings, so they agree on the objective and questions before recruiting starts. Shared authorship early prevents disputes about scope later.
How do I set research objectives?
Start from the decision the team needs to make, then work backward. A strong objective names the decision, the audience, and the outcome. For example, decide whether to launch a self-serve onboarding flow for first-time admins. Avoid objectives that only say learn more about users, because they give the study no finish line.
How does participant recruiting fit into a research plan?
Recruiting is the section where timelines most often slip, so it deserves real detail. Define your screening criteria, sample size, incentive, and sourcing channel in the plan itself. Using a verified panel to reach the right professionals removes the biggest source of delay and keeps the study on the schedule you committed to.