Hire an AI UX researcher

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A study plan with questions, method, who to recruit, how many people and a timeline
• A usability test script with tasks and what to watch for, if you ask for one
• Findings that each cite the notes behind them
• Personas and a path map built from your evidence, if you ask for them
• Fixes ranked by impact and effort, with a way to check each one worked

How it does the job well

• You plan and analyse. You cannot recruit, run sessions, watch recordings or read analytics tools. Say so if asked.
• Never present a percentage, a score or a target that is not in the user's notes. Use counts such as "3 of 5".
• Notes may hold names or contact details. Use participant labels in the report.
• A study with children, patients or other high-risk groups needs a qualified researcher and an ethics review. Say so and stop at a plan outline.
• Do not claim to remember between chats. Tell the user to save the report and paste it back next time.
• Start from the user's task and the content, then the layout. Decoration comes last.
• Design every state: empty, loading, error, long text and mobile.

Mistakes it avoids

• Designing only the happy path at desktop width.
• Copying a reference's logo, text or claims instead of learning from its structure.
• Handing over a picture without the sizes, tokens and behaviour a developer needs.

What a good result looks like

An example, not your task: Your checkout, sign-up or app keeps losing people and you do not know where they get stuck.

• Research question. Your worry restated as one question, with the decision it will change.
• Study plan. Method, who to recruit, how many, screening rules, session outline and consent steps.
• Evidence. What each person said or did, listed before any conclusion is drawn.
• Findings. Each finding with the people who showed it, a quote and how sure the agent is.
• Personas and path map. Goals, pain points and steps for each user type, built only from your notes.
• Recommendations. Fixes ranked by impact and effort, each with a way to check it worked.

How the work is checked

• Every screen has its states, breakpoints and interactions written down.
• Colour pairs and type sizes pass the stated contrast checks.
• The handoff names components, tokens and open questions.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way Clayton Christensen and Jill Konrath would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Fix the question. It turns your worry into a research question you can answer, and asks once for what is missing.
• Pick the method. It matches the question to interviews, a survey, a usability test or your analytics, and says why.
• Plan the study. It sets who to recruit, how many, how to screen them and how to get consent and protect privacy.
• Read the notes. It lists what people said and did, one per line, before it draws any conclusion.
• Find the patterns. It groups the evidence into themes and counts how many people showed each one.
• Rank the fixes. It turns each finding into a fix with impact, effort and a way to measure it.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id design-ux-researcher only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/design-ux-researcher/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• The product or page, and who uses it
• The one question you need answered, such as why people leave the checkout
• Notes from interviews or usability tests, pasted as text (optional if you are only planning)
• Any numbers you have, such as drop-off by step (optional)
• Your limits on time, people and budget (optional)

Helpful context (optional)

• Drop-off numbers by step, from your analytics.
• Session recordings or transcripts, pasted as text.

Tools and access

• Claude, ChatGPT or Gemini: Pasted notes are enough. Long note sets work best in an AI with a large reading window.

Functions and deliverables

• UX researcher agent: Plan a user research study or turn your interview and test notes into findings, personas and ranked fixes for your website or app.
  • A study plan with questions, method, who to recruit, how many people and a timeline
  • A usability test script with tasks and what to watch for, if you ask for one
  • Findings that each cite the notes behind them
  • Personas and a path map built from your evidence, if you ask for them
  • Fixes ranked by impact and effort, with a way to check each one worked
  Source: Michael Sitarzewski and Agency Agents contributors.
• Customer job interview planner: Plan a customer job interview: watch buyers, ask them on the way out, and talk to people who switched. You get questions and a log sheet.
  • A plan for a day of observation, with a log sheet
  • Quick questions for buyers on their way out
  • An interview plan for people who switched in the last year
  • What each answer should show, and the checks to run
• Interview and research planner: Share a decision, research question and who you can reach. Get a study plan and interview guide, not findings before research.
  • A sharper version of your research questions
  • A recruiting plan with numbers
  • An interview guide
  • Steps for turning notes into findings
  • A list of product decisions the findings should inform
  Source: RampStack.
• User persona and journey mapper: Share user notes and a product goal. Get user profiles, a journey map and test tasks.
  • Data based personas
  • A path map with pain points
  • A usability test plan
  • A summary of research themes
  Source: Alireza Rezvani.
• Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
  • A folder of eight plain files, from a start file for your AI to a claims list and a change log
  • A tag on every fact, and every claim marked approved, pending or banned
  • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
  • A short slice for your next step, if you name one
• Clayton Christensen: Explore why customers buy using Clayton Christensen’s recorded approach. Start with a real situation, the struggle and what the buyer used before.
  • Your problem worked on the way Clayton Christensen would: their questions, their method, their push-back
  • The answer or the work, in Clayton Christensen's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Jill Konrath: Write a short sales message for a busy buyer through Jill Konrath’s recorded approach. Show the business result and a clear reason to change.
  • Your problem worked on the way Jill Konrath would: their questions, their method, their push-back
  • The answer or the work, in Jill Konrath's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• Your checkout, sign-up or app keeps losing people and you do not know where they get stuck.
• You are about to redesign a page and want to test the idea with real users first.
• You have a folder of interview or usability test notes and no time to find the patterns.
• A teammate says "users hate this" and you need evidence before you change anything.

Limits to check before starting

• You want to find what to ask in early customer interviews for a business idea: use the Customer discovery interview planner.
• You want a quick research method pick and plan, with no UX focus: use the User research planner.
• You want to sort a pile of reviews, tickets or survey comments into themes: use the Product feedback analyst.
• You need a study with real legal or medical risk, such as patient testing: use a trained researcher and an ethics review.
• You want to test whether a result is statistically real: use the Statistician agent.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Add the pack to your AI as a skill. Or open a new chat and paste SKILL.md, then references/source-agent.md.
• Say whether you are planning research or analysing notes. Paste the product, the users and your one question.
• For analysis, paste your notes, one person per block. Say how many people you spoke to.
• Read the evidence list first. Remove or fix any quote or finding that does not match your notes.
• Run the plan or the test script with real people. You do the recruiting and the sessions, then come back with the notes.
• Pick the top fix, make the change and test again with a few new people.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/design-ux-researcher for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.