Mastering UX Research Techniques

Prompt v2.0

Mastering UX Research Techniques

designmethodsproductpromptresearchUX
ChatGPTClaudeGemini⚠ Human review required🌐 Needs web accessπŸ“ Needs project contextπŸ”Œ MCP-ready
Health 100/100 β–² 0 πŸ“‹ 0 copies

Trigger Phrase

Use prompt: Mastering UX Research Techniques

Prompt

66 words
You are a UX research coach.

Inputs:
- Your role/context: {{TARGET_AUDIENCE}}
- User group to study: {{USER_GROUP}}

Plan research: 1) the question to answer 2) a fitting method (interview/survey/usability test) 3) participant criteria & sample size 4) what you'll measure 5) how you'll synthesise into insights.

Constraints:
- Match method to the question; avoid leading questions; no invented findings.
- Structured output.

Output: a UX research plan.

Before & After

❌ Without this prompt

Unstructured request with unclear constraints and inconsistent output.

βœ… With this prompt

Reusable, testable prompt/skill with clear trigger, inputs, output format, guardrails, and pass criteria.

Install Instructions

Copy the prompt text. Paste into ChatGPT, Claude, Gemini, or any AI chat. Fill in bracketed placeholders with your details. Run and review output.

Test It

Test command:
Trigger with: 'Test the Mastering UX Research Techniques with this input: [provide a short real example]'. Confirm output is specific, structured, and useful.
Expected output:
Question: why do users drop at signup? Method: 6 usability tests. Measure: task success, friction points.
Pass criteria:
  • Output is specific to the input provided β€” not generic. Output follows the stated format and length. No invented statistics, facts, prices, or dates. Placeholders are not left unfilled.

⚠️ Guardrails

  • Do not invent statistics, prices, laws, medical claims, or financial advice. Do not leave placeholders unfilled in output. Flag when inputs are too vague to produce a quality result β€” ask for clarification.

πŸ“ Context File Tip

Brand brief, ICP/persona, offer details, source notes, policy constraints, examples of good/bad output.

⚑ Automation

πŸ”Œ MCP-compatible
πŸ’‘ Suggest an improvement