LibraryZenithRequest a breakdown
Research DocsStandardValidationFounder-ready

Documentation reference

User Research Plan

A user research plan prevents vague discovery. It defines research goals, assumptions, participants, methods, interview questions, analysis approach, timeline, and how findings will affect the roadmap.

Overview

What this document is

A user research plan prevents vague discovery. It defines research goals, assumptions, participants, methods, interview questions, analysis approach, timeline, and how findings will affect the roadmap.

User researchDiscoveryInterviewsValidationResearchOps

Fit signals

When to use it

  • The team has assumptions but not enough evidence.
  • A founder needs to understand users before committing to product scope.
  • The product has adoption, conversion, retention, or usability questions.
  • Design decisions need evidence instead of opinions.

Audience and ownership

Who uses it

Founders, product teams, designers, and agencies validating a problem, workflow, audience, or product concept.

FounderUX researcherProduct designerProduct manager

Before and after

Where it fits in the build chain

Idea Brief
BRD
PRD
Research
IA
Design System
Architecture
SOW
QA Plan
Launch

Gather before writing

Inputs required

  • Research question template
  • Participant screener
  • Interview guide
  • Synthesis and opportunity map

What each part should cover

Section-by-section guide

Goals

Explain what decision this section helps the team make and how success will be recognized.

Assumptions

Capture what could break the plan, what is still unknown, and who owns the next decision.

Participants

Describe the participants clearly enough that a founder, teammate, or AI agent can use it without needing hidden context.

Methods

Describe the methods clearly enough that a founder, teammate, or AI agent can use it without needing hidden context.

Questions

Describe the questions clearly enough that a founder, teammate, or AI agent can use it without needing hidden context.

Analysis

Describe the analysis clearly enough that a founder, teammate, or AI agent can use it without needing hidden context.

Practical workflow

How to create and use it

  1. 01Define research questions and product decisions the study must inform.
  2. 02Choose methods based on stage, risk, and available participants.
  3. 03Recruit target users and run interviews, tests, or surveys.
  4. 04Synthesize findings into product opportunities, risks, and PRD inputs.

Copy into your workspace

Starter template

  1. 01Define the decision this research must support.
  2. 02List assumptions, target participants, methods, and questions.
  3. 03Set recruiting criteria, timeline, and synthesis format.
  4. 04Define how findings will update the BRD, PRD, or roadmap.

Make the draft usable

Weak vs strong examples

Research question

Weak

Do users like the idea?

Strong

What causes operations teams to abandon spreadsheet-based onboarding, and what evidence would make them trust a shared client portal?

Participant criteria

Weak

Talk to business users.

Strong

Interview 8 operations leads at service businesses with 10-100 employees who currently manage client onboarding across email, spreadsheets, and shared drives.

How to know it is useful

Quality checklist

  1. 01Research questions map to product or business decisions.
  2. 02Participant criteria are specific enough to recruit the right users.
  3. 03The plan defines how findings will be captured and tagged.
  4. 04The output links insights to roadmap or PRD decisions.

Before you hand it off

Document readiness checklist

  • The user research plan has a named owner and approval path.
  • The business or product decision this document supports is explicit.
  • Inputs, assumptions, and open questions are separated from confirmed facts.
  • Scope boundaries and non-goals are clear enough to prevent silent expansion.
  • The document can be handed to a teammate, agency, or AI agent without hidden context.
  • Research questions map to product or business decisions.
  • Participant criteria are specific enough to recruit the right users.
  • The plan defines how findings will be captured and tagged.

Generate the first draft

AI prompt

Draft prompt

Create a user research plan for this product idea. Include research goals, assumptions, participant segments, recruiting criteria, methods, interview guide, tasks, timeline, analysis approach, insight tags, decision impact, and output format.

Avoid these

Common mistakes

  • Asking users what to build instead of studying behavior and pain.
  • Recruiting anyone available rather than the target segment.
  • No plan for analysis or decision-making after interviews.
  • Mixing validation, usability, and market research without focus.

Use this after the draft

Handoff assets

  • Research objectives
  • Participant criteria
  • Interview or test guide
  • Insight synthesis format

Suggested build path

What to create before and after

Before

PRD

Keep this connected so the build stays traceable.

Current

Research

Use this page to create the working draft.

After

IA

Keep this connected so the build stays traceable.

Zenith CTA

Need this shaped for your business?

Zenith can turn rough notes into a founder-ready user research plan.

Bring your idea, current docs, users, constraints, and open questions. We will help make the next decision clear.

Request a breakdown