Ux Research Plan
Create a UX research plan that connects a product decision to evidence.
Sample result
How it works
What Ux Research Plan does
Turns decisions into answerable research questions, separates known facts, assumptions, and unknowns, writes falsifiable hypotheses with pre-set decision thresholds, selects methods by question type, defines participant criteria with a screener and a sample-size logic, drafts the interview or session guide, plans consent and data handling, builds a backwards timeline, and specifies the synthesis approach and readout.
Use it when
Someone asks for a UX research plan, a discovery or generative research study, interview plan, research hypotheses, which research method to use, or how to recruit and what to ask users.
Use something else for
A usability test protocol with tasks and success criteria, analyzing an existing survey export, synthesizing feedback already collected, or controlled experiments.
Inputs and results
What goes in, what comes back
- You give
A short brief describing what you need
Add a specialist method to the work.
- You get
Research plan, hypothesis table, interview guide and synthesis plan
The method guides the work with your files and context.
- You check
The sources and open questions
Review the output against your brief.
Questions and answers
Questions about Ux Research Plan
Updated Oct 20, 2026.
What does Ux Research Plan do?
Create a UX research plan that connects a product decision to evidence. Turns decisions into answerable research questions, separates known facts, assumptions, and unknowns, writes falsifiable hypotheses with pre-set decision thresholds, selects methods by question type, defines participant criteria with a screener and a sample-size logic, drafts the interview or session guide, plans consent and data handling, builds a backwards timeline, and specifies the synthesis approach and readout. Use when someone asks for a UX research plan, a discovery or generative research study, interview plan, research hypotheses, which research method to use, or how to recruit and what to ask users. Do not use for a usability test protocol with tasks and success criteria (use usability-test-plan), analyzing an existing survey export (use analyze-survey-results), synthesizing feedback already collected (use synthesize-product-feedback), or controlled experiments (use ab-test-setup).
Who is Ux Research Plan for?
It is designed for UX researchers, product designers, product managers, founders doing customer discovery and agency research leads.
What do I need to use it?
Nothing extra is needed. Sign in to Relay to run it with your own files and context.
What does Ux Research Plan produce?
Research plan, hypothesis table, interview guide and synthesis plan. Results come back with their sources and any open questions for you to check before anything is used.
How much does Ux Research Plan cost?
It is free to use. Paid model usage, if any, is shown before a run.
Can an AI agent use it?
Yes. Agents can read its public definition through the Relay API and run it with a person’s authorization. See the For Agents page for how to connect.
Details
Trust, access and technical details
Trust and access
- Visibility
- Public: anyone can view
- Status
- Published and maintained
- Pricing
- Free
- cmvgtauhq00ce…
- Oct 20, 2026
- 0 signals
- Commit pinned
Security review is a static package assessment, not a guarantee of safety or a behavioral qualification.
Use it from code or an agent
Read the public definition, then check cost and inputs with a preflight before a run.
Open definitionPOST /api/v1/runs/preflight
How agents connect to Relay →Tags and source
- Repo
- rose-digital/relay
- License
- MIT
Connections
Where Ux Research Plan fits
Similar skills5
codebase-design
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.FreeSkill · MarketingColor Font Pairing
Select a color palette and type pairing that fits a brand, audience, and product, and prove it works. Defines palette roles (neutral ramp, brand, accent, semantic states, surfaces), checks every intended foreground and background pair against WCAG contrast thresholds, plans dark mode and color-blind-safe signaling, chooses font roles and pairings by shared structure and clear contrast, verifies script coverage, numerals, weights, licensing, and performance, and sets a type scale. Use when someone asks for a color palette, a font pairing, typography or brand color choices for a site or app, whether two fonts go together, or whether a palette is accessible. Do not use for exploring whole visual styles (use explore-visual-directions), building a moodboard (use creative-moodboard), auditing existing screens (use design-audit), or governing a shared component library (use component-library-governance).FreeSkill · MarketingComponent Library Governance
Define how a design-system component library is owned, extended, reviewed, versioned, and retired. Sets the ownership model and decision rights, an intake and triage path for requests, component status levels with entry and exit criteria, a definition of done covering design, accessibility, code, and documentation, a scored review rubric, versioning and deprecation rules, exception handling, and health metrics with formulas. Use when someone asks for design system governance, contribution rules, component status levels, a review checklist for new components, how to deprecate a component, or why teams keep forking or detaching components. Do not use for auditing screens for inconsistency (use design-audit), choosing colors and fonts (use color-font-pairing), testing built components for accessibility (use accessibility-qa), or app-surface patterns like tables (use steel-design).FreeSkill · MarketingDesign Audit
Audit an existing UI against its own job and produce an evidence-backed, ranked findings report. Scopes the audit to named tasks and screens, runs a task walk, then checks visual hierarchy, layout and spacing, accessibility against WCAG 2.2 criteria, information density, cross-screen consistency, and conversion or workflow fit; separates defects from judgment calls; scores each finding by severity, reach, confidence, and effort. Use when someone asks for a design audit, UI review, UX heuristic review, an accessibility and consistency check of screens, or why an interface feels cluttered, confusing, or underperforms. Do not use for redesign directions (use explore-visual-directions), a funnel numbers diagnosis (use diagnose-conversion-funnel), a full site restructure (use map-site-for-redesign), or an accessibility test pass on built software (use accessibility-qa).FreeSkill · Marketinggrill-me
A relentless interview to sharpen a plan or design.FreeCommunityHave a task this would help with?
Describe it. Relay plans the work, picks the right playbook and shows the cost before anything runs.