Plan user interviews or usability tests
A research plan with goals, participants, discussion guide, and tasks.
The prompt
Role: Act as a UX researcher planning a study.
Context: Decision the research must inform: [DECISION]. Research questions: [RESEARCH_QUESTIONS]. Study type (interviews / usability test / both) and setting: [STUDY_TYPE]. Target participants and where to find them: [PARTICIPANTS]. Prototype / product state: [ARTEFACT]. Timeline and number of sessions: [LOGISTICS]. Known biases to avoid: [BIAS_RISKS].
Task: Produce: sharpened research questions; a screener to recruit the right participants (with disqualifiers); a discussion guide (warm-up, background, core questions with non-leading phrasing and probes, wrap-up); for a usability test, 3-5 realistic task scenarios with success criteria and what to observe; a consent/recording note; and the analysis approach (how sessions will be coded and synthesised).
Format: Sections: Research questions | Screener | Discussion guide | Task scenarios (if applicable) | Consent note | Analysis approach.
Verification: Flag any question or task that is leading, double-barrelled, or primes the participant; check the screener actually excludes the wrong people.
Validation: Dry-run the guide against a likely participant: does it fit the session length and elicit the decision-relevant information? Trim or resequence.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Product & UX Design prompts
What to fill in
- DECISION
- RESEARCH_QUESTIONS
- STUDY_TYPE
- PARTICIPANTS
- ARTEFACT
- LOGISTICS
- BIAS_RISKS
How this prompt is built
This prompt follows the RCTFVV structure (Role, Context, Task, Format, Verification, Validation). RCTFVV extends RCTF with two checking steps. Verification asks the model to review its own draft against your requirements; Validation asks it to flag assumptions and gaps you should confirm.
Related prompts
- Make the business case for a UX improvementBuilds a short, numbers-aware pitch that links a design fix to revenue, cost, or risk so leadership prioritizes it.
- Prioritize a product roadmap or backlogScores and orders features with a transparent model (RICE, value vs. effort) and builds a roadmap.
- Map an opportunity solution treeConnects an outcome to customer opportunities, solutions, and experiments.
- Set product vision, strategy, and OKRsVision, strategy, and outcome-based OKRs for a product or team.