reph

Templates · Design

UX research plan template

Research questions, method, participants and timeline

Start with this template →Sign in

Opens on reph with the template ready to start. No account needed; sign in to keep your document.

Use it when

A product decision depends on something you do not yet know about users, and you need agreement on questions, method and timeline before recruiting

Who it's for

ResearcherDesignerProduct manager

Filled example

The template filled in for a made-up company, so you can see what good looks like.

UX research plan: How clinics handle insurer claims

Author: Kofi Mensah · Date: 5 November 2026

Background

Carewell's Billing squad will decide in January whether to build in-app insurer claim submission or deepen our integration with ClaimBridge, the clearing service 38% of clinics already use. Claims are the second largest source of billing tickets. We do not know who in a clinic files claims, how often claims are rejected, or what happens after a rejection. This study informs the build versus integrate decision.

Research questions

  • Who files insurer claims in a clinic, and how much of their week does it take?
  • At which steps do claims get rejected, and how do clinics find out?
  • What would make a clinic switch away from the tool they use today?
  • Do clinics that use ClaimBridge experience fewer rejections than those that file by hand?

Method (and why)

Remote contextual interviews of 60 minutes, with participants sharing their screen while filing or reviewing a real recent claim (with patient details hidden). Interviews over a survey because we do not yet know the right options to offer; contextual over plain interviews because people misremember how many steps a claim takes. A short follow-up survey to all clinics in January will size what we find.

Participants

Participants
12
Segments
3
Weeks to readout
5
Criteria Target N Recruiting source
Files claims by hand, 1 to 3 practitioners 4 In-app banner to eligible clinics
Uses ClaimBridge 4 Customer success list
Clinic owner or manager who reviews rejections 4 Customer advisory board

Consent and data

  • Consent: written consent form sent with the invite; verbal confirmation at recording start.
  • Storage: recordings in the research drive, access limited to the research team and the Billing PM.
  • Retention: recordings deleted 90 days after readout; anonymised notes kept.

Discussion guide outline

  1. Warm-up: role and a normal week (5 min)
  2. Walkthrough of a recent claim, on screen (25 min)
  3. Rejections: the last one and what happened next (15 min)
  4. Tools and switching (10 min)
  5. Wrap-up (5 min)

Timeline

Phase Dates Owner
Recruiting 10 to 21 November Kofi
Sessions 24 November to 5 December Kofi, Maya
Synthesis 8 to 12 December Kofi
Readout 15 December Kofi

Deliverables

A synthesis doc in reph with findings tied to each research question, a 6 minute highlight reel, and a journey map of the claim lifecycle. Goes to the Billing squad and the VP of Product.

Stakeholders

Jonas Berg (Billing PM) owns the decision and observes at least four sessions. Priya Raman (engineering lead) observes two. Ana Lima (design lead) attends the readout.

The template

Show the blank template

UX research plan

Author: [your name] · Date: [date]

Background

What decision this research is meant to inform. A vague "understand users better" produces a report nobody acts on.

Research questions

What you need to know, phrased as questions you could fail to answer, not the interview script itself.

Method (and why)

Qualitative interviews, usability testing, a diary study or a survey, and why this method over the alternatives given your questions and timeline.

Participants

Who qualifies, how many, and how you'll find them.

Participants
0
Segments
0
Weeks to readout
0
Criteria Target N Recruiting source

Consent and data

How you'll get consent, where recordings live, who can see them, and when they're deleted.

  • Consent:
  • Storage:
  • Retention:

Discussion guide outline

The rough shape of a session: not the full script, just the sections and time budget.

  1. Warm-up (5 min)
  2. Core questions (30 min)
  3. Wrap-up (5 min)

Timeline

Recruiting, sessions, synthesis, readout, with dates.

Phase Dates Owner
Recruiting
Sessions
Synthesis
Readout

Deliverables

Report format (synthesis doc, highlight reel, affinity map) and who it goes to.

Stakeholders

Who needs to see this land, and who should observe sessions live.

Questions

How many participants do I need?
Five to eight per segment for interviews or usability tests, far more for a survey
How long does a study take?
Usually three to five weeks from plan to readout, with recruiting as the slowest step
Who should observe sessions?
The PM and an engineer from the team making the decision, live if possible

Fill it with your agent

Connect Claude to reph over MCP, then paste this. The draft arrives as suggestions you accept or reject section by section. How to connect Claude.

Find my reph doc "UX research plan" with search_docs, then read it with read_doc. Draft Background and Research questions from the PRD, open roadmap decisions and past research I link, each question able to fail. Propose a method and participant criteria that fit the timeline, and how consent and participant data are handled. File it with suggest_edit, one replace_section op per section (heading line kept) so each can be accepted alone. Ask each open question (recruiting and budget assumptions) with add_comment quoting that section's heading line, then call request_review with a one-line summary.

Related templates

Start with this template →Sign in