Templates / Project

Free UX Research Plan Template

A UX Research Plan covers the research stages, tasks, and handoff steps, from kickoff through synthesis and recommendations.

UX Research Plan template preview

7-day free trial. No credit card required.

Use this template

Language:

en

Category:

Last updated:

October 2026

Share template

Teams need clarity on what to build next, but research can drag on and still leave decisions fuzzy. The UX Research Plan gives the work a visible order, from kickoff through handoff, so interviews, evidence, and recommendations don’t drift into “we’ll get to it later”. The board uses teal-grey accents with proof-sheet magenta for the moments that call for action, under Fraunces headings and Inter body text.

Cards move in one direction, so stakeholders can see what’s happening now and what’s blocked, and the research team can keep momentum without skipping the evidence. The early cards cover access, context, and goals, then the board pushes into scripts, screeners, and session planning. The back half holds execution notes, synthesis into insight cards, prioritisation by effort and impact, and a handoff package that engineering can actually build from.

  • Onboarding and kickoff Adds the team, confirms access and permissions, and captures product context before sessions get scheduled.
  • Research design Holds the goals, success metrics, methods, and scripts, so the team agrees what evidence will count before talking to users.
  • Recruitment and scheduling Tracks the participant profile, screening, and session confirmations, and keeps recruitment moving without guesswork.
  • Synthesis and recommendations Turns sessions into insight cards, maps problems to journeys, and ranks recommendations by effort and impact before the handoff.

In Plutio, the template runs as a project board with 28 cards, which means the first edits are your own dates and the people assigned to each task. Once the work starts, the columns act like a checklist you can work through, leaving one place to track recruitment, sessions, and the recommendations that come out the other end.

We went from spending hours on every proposal to creating fully customized ones in under 5 minutes. That's not an exaggeration - we timed it.

Yazan & Mawaheb
Yazan & MawahebAgency Owners

What is on this board

6 columns carrying 28 cards. Adding it builds the whole thing as a project in your workspace, with every column and card in place.

ColumnWhat is in it

Onboarding and kickoff

Kickoff tasks cover roles, access, stakeholder alignment, and the product context you’re researching. Swap in your own stakeholders and permissions list before the first meeting.

  • Introduce the team and roles
  • Confirm booking payment received
  • Create project folder and access list
  • Request developer access and analytics permissions
  • Run kickoff meeting with stakeholders
  • Document product context and gather analytics

Research design

Design tasks define goals and success metrics, then move into scripts, screeners, and a usability test plan. Update methods, sample size, and incentives to match the question you’re trying to answer.

  • Define research goals and success metrics
  • Select methods and sample size
  • Draft interview script and screener
  • Create usability test plan and tasks
  • Prepare recruitment brief and incentives

Recruitment and scheduling

Recruitment tasks cover the target profile, screening, and session scheduling. Add whoever owns recruitment and plug in the cadence you can actually support.

  • Confirm target participant profile
  • Coordinate recruitment with client or recruiter
  • Screen candidates using screener
  • Schedule sessions and send confirmations

Research execution

Execution tasks cover moderated sessions, tagging and transcription, and quick notes right after each session. Assign the moderator and note-taker so evidence doesn’t get lost between calls.

  • Run moderated interview and usability sessions
  • Tag and transcribe key moments
  • Collect quick synthesis notes after each session

Synthesis and recommendations

Synthesis tasks turn findings into insight cards, map issues to journeys, and prioritise recommendations with effort and impact. Replace the draft report outline with the format your team expects to read.

  • Synthesize findings into insight cards
  • Map problems to user journeys
  • Prioritize recommendations with effort and impact
  • Draft final research report with recordings and evidence

Handoff and close

Closeout tasks cover a roadmap of fixes and experiments, low-fidelity wireframes for priority flows, and an engineering handoff package, then billing and archiving. Update the handoff owners and the final billing step to match how the work closes.

  • Create recommended roadmap of fixes and experiments
  • Produce low-fidelity wireframes for priority flows
  • Prepare handoff package for engineering
  • Present findings and next steps to stakeholders
  • Issue final invoice for remaining 50% of price
  • Close project and archive assets

What happens when you install it

  • A project is created with its board, 6 columns and 28 cards already there.
  • Nothing carries a due date, because a board holds the order the work runs in rather than a calendar. The dates go on once you know when the job starts.
  • Every card opens as a task with its own description, assignee, dates, subtasks and files, and columns are renamed, reordered or deleted like any other.

Who it is for

UX researchers, product designers, and ui/ux design teams running interviews and usability tests, then handing recommendations to engineering and stakeholders.

Questions about this project template

What should a UX research plan include?

A UX research plan usually covers kickoff and access, research goals and success metrics, the chosen methods, recruitment and scheduling, how sessions will run, and how findings turn into recommendations. This board follows that same flow, ending with handoff and close.

How many users do we need to talk to for UX research?

The number depends on the methods, the risks in the product area, and how consistent the patterns are as sessions run. This board includes tasks to pick methods and sample size up front, then adjust once early sessions show what’s repeating.

Do we have to recruit participants ourselves?

Recruitment can run through your team, the client, or a recruiter, as long as someone owns the screener and scheduling. The recruitment column includes tasks for confirming the target profile, screening candidates, and sending session confirmations.

What do you need from the dev team for UX research, and when?

Access tends to come first, like analytics permissions and whatever’s needed to understand constraints and instrumentation. The kickoff column includes tasks for requesting developer access and documenting product context before research design and sessions start.

How do you keep UX research from turning into endless tweaks?

A plan needs decision points, not just activities, so the work moves from goals to evidence to prioritised recommendations. The synthesis column includes prioritisation by effort and impact, which creates a stopping point for analysis and a clear handoff.

What’s the difference between usability research and product design work?

Usability research focuses on observing behaviour and collecting evidence, while product design turns decisions into flows and screens within constraints. This board keeps both connected by ending with recommendations, a roadmap of fixes and experiments, and low-fidelity wireframes for priority flows.

This workspace is on us. Every feature in the Suite switched on, free for 7 days, no card needed.