Research Plan Template (free)

Structure your user research study from start to finish so you capture the right insights, recruit the right participants, and walk away with clear, actionable findings.

Template components

Research Goals & Questions
Write the primary objective of your study and the specific questions you need answered to make a product decision.
Example: Goal: Understand why new users abandon the onboarding flow before completing their first project. Key questions: What steps feel confusing or unnecessary? What do users expect to happen that doesn't? What would make them more confident to continue?
Methodology & Study Design
Describe the research method you will use, the format of the sessions, and how you will capture data.
Example: Method: Moderated usability testing via Zoom. Format: 45-minute sessions with think-aloud protocol. Data capture: Session recordings, observer notes, and a post-task SUS questionnaire. Sessions will be conducted over two weeks with a minimum of 5 participants per segment.
Participant Criteria & Recruitment
Define who qualifies for the study, how many participants you need, and how you will recruit and screen them.
Example: Target: SaaS product managers at companies with 50–500 employees who signed up in the last 90 days but have not created a project. Sample size: 10 participants (5 from SMB segment, 5 from mid-market). Recruitment: In-app intercept survey + UserTesting panel. Screener will exclude anyone in a technical role or with prior product research experience.
Success Criteria & Deliverables
State how you will know the research was successful and what outputs you will deliver to stakeholders when it is complete.
Example: Success criteria: Identify at least 3 distinct friction points supported by observations from 60% or more of participants. Deliverables: Affinity map of themes, top 5 findings with supporting quotes, prioritized list of design recommendations, and a 10-slide readout deck for the product team — due within one week of final session.

Full Copyable Template

How to use it

  1. Define your research goal first
    Before filling in any other section, write one clear sentence that describes the decision this research will help your team make.
  2. Choose your method based on your question type
    Use generative methods like interviews when you need to discover problems, and evaluative methods like usability tests when you need to assess a specific solution.
  3. Recruit before you finalize your discussion guide
    Start the screener and outreach process early so participant scheduling does not delay your study timeline while you finalize your questions.
  4. Share the plan with stakeholders before fielding
    Get sign-off on goals and success criteria upfront so that findings land with credibility and recommendations move directly into the product roadmap.

What it looks like filled in

Unclear value at the setup step
"I didn't know what a 'workspace' was supposed to be — I thought I was setting up my profile, not the whole company account."
→ Rewrite the workspace setup screen headline to explain who this configuration affects and why it matters before users proceed.
Premature feature exposure overwhelming new users
"There were like eight things I could do and I just wanted to create one thing and see if it worked — I didn't know where to start."
→ Design a focused first-run experience that surfaces only the single next action needed to reach the first value moment, hiding advanced features until session two.
Missing progress feedback causes drop-off anxiety
"I saved it and nothing happened — no confirmation, nothing. I wasn't sure if it actually worked or if I had to do something else."
→ Add inline save confirmation and a visible progress indicator throughout onboarding so users always know their current step and what comes next.

Why teams skip the template

  • Manually reviewing hours of session recordings
    Watching and re-watching recordings to find recurring themes takes days of researcher time and is highly dependent on who is doing the reviewing.
  • Synthesizing notes into themes by hand
    Sorting sticky notes or spreadsheet rows into affinity clusters is time-consuming and introduces bias based on which quotes you happened to notice or remember.
  • Writing up findings without missing critical patterns
    When analysis is done manually across 10 or more sessions, low-frequency but high-impact signals are routinely overlooked because they do not cluster visually the way dominant themes do.

Analyze your user research plans and study designs automatically — no template needed

👉 TRY IT NOW FREE