UX research study track
Runs a UX research study in gated steps - research questions, method choice, screener, session guide, notes template, synthesis and a decision-focused readout - pausing for approval.
Runs one UX research study from question to decision.
Only if [PRODUCT] is given:
Product: Only if [TIMELINE] is given:
Timeline and resources:
Seven steps: sharpen the research questions, choose the method, write the screener, write the session guide, prepare the notes template while sessions run, synthesise the notes, and write a readout aimed at the decision. Each step produces one document and stops for the team's edits or approval; later steps build on the approved versions.
Rules for every step: the study exists to inform a decision, so every question, task and finding traces back to it. Keep what people did apart from what they said and from what we interpret. Protect participants: informed consent, the right to stop, fair incentives, minimal personal data and anonymised quotes. Never invent participants, quotes, counts or results; steps that need real-world work wait for the team to paste notes. The team owns every decision.
Step 1: Research questions and the decision
If the decision this study informs, or who makes it, is missing, ask for both and stop. Other gaps become marked assumptions.
Write:
- Decision: what will be decided, by whom, by when, and the options.
- Research questions: three to five, specific and answerable with evidence, each labelled behaviour (what people do), attitude (why, what matters) or prevalence (how many).
- Known so far: from the input, with sources, and what it does not tell us.
- Out of scope.
- What would change our mind: for each option, the evidence that would favour it, set before any data.
Flag questions this study cannot answer in time, and propose a narrower one or a better source (analytics, a survey).
Stop for approval.
Step 2: Choose the method
- Match each approved question to a method: behaviour and usability → usability tests, contextual inquiry or diary studies; attitude → interviews; prevalence → surveys or analytics; navigation and labels → tree tests or card sorts. Say plainly when a requested method cannot answer a question (a usability test cannot show whether people would buy).
- Recommend one primary method, and a second only if a question needs it and time allows.
- Specify participants (behaviour-based, by segment), sample size with reasoning (about five to eight per segment for qualitative work; far more for surveys), session length and format, stimulus, incentive, roles, and a schedule with recruiting lead time, a pilot, sessions, synthesis and readout.
- Note consent, data storage and deletion, and any ethics review (children, patients, vulnerable groups).
Stop for approval.
Step 3: Screener and invitation
- Recruit spec: must-have behaviours with recency and frequency; exclusions (research, UX, marketing or press jobs; employees of the company or competitors; a similar study in the last six months; study-specific ones).
- Screener: 8 to 12 questions, knock-outs first, multiple choice with distractors and "None of these", the target hidden among other options, never a yes/no that reveals the answer. Give the logic per answer (accept, reject, quota), one articulation question with accept criteria, logistics and consent questions.
- Quota grid with about 20% over-recruit.
- Invitation (under 120 words, criteria not revealed) and confirmation message, with placeholders for incentive, time and links.
Ask only what decides eligibility; sensitive data only if needed, optional, with a reason.
Stop for approval.
Step 4: Session guide
Write the guide for the approved method, timed to the session length.
- Opening: neutral purpose, consent and recording, the right to stop, "we are testing the product, not you", and a think-aloud practice for usability tests.
- Interviews: context warm-up, then the last specific time the behaviour happened, probing trigger, steps, people, tools, workarounds and cost. Open, neutral questions about the past; no "would you use" or "how much would you pay".
- Usability tests: five to eight scenario tasks that avoid interface labels, each with start point, success criteria and time limit; neutral probes. Unmoderated: self-contained instructions and an attention check.
- Other methods: the equivalent instrument.
- Label every block or task with the research question it serves, and add moderator notes (do not help or defend the design) and a pilot checklist.
Stop for approval.
Step 5: Notes template and sessions
- A notes template per session: session id, date, segment, device (no names); for each block or task, what the participant did, verbatim quotes with timestamps, and the note-taker's interpretation in a separate labelled field; task outcome, time and problem severity; evidence per research question; surprises.
- A five-minute debrief routine after each session.
- A session tracker: id, segment, date, status, notes link placeholder.
Stop for approval. Then run the sessions. The team pastes all notes or transcripts to start step 6; do not continue without them.
Step 6: Synthesis
If no notes or transcripts were pasted, ask for them and stop.
- List sessions analysed (N) and any excluded, with the reason.
- Break notes into observations tagged with session id and type: behaviour, opinion or hypothetical.
- Cluster by underlying cause; name each finding as a statement, not a topic.
- Per finding: n of N with ids, one to three verbatim quotes, confidence, and for usability problems a severity (critical, serious, minor) separate from frequency.
- Answer each research question, or say "not answered by this study".
- Note contradictions, segment differences, surprises and what worked.
Use "n of N", not percentages; mask personal details.
Stop for approval.
Step 7: Decision-focused readout
One to two pages for the decision-maker, from the approved synthesis only:
- Recommendation: the option the evidence favours, confidence, and the findings that drive it, checked against the step 1 "what would change our mind" criteria. Say plainly when evidence is mixed.
- Answers to the research questions.
- Top findings, ranked by impact on the decision, with n of N, a quote and severity.
- Next actions with owner placeholders.
- Limits and still unknown, each gap with its cheapest next step.
- Appendix: method, segments, dates, link placeholders.
Put uncomfortable findings first. The decision-maker owns the decision.
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Workflow: ordered steps with a checkpoint between them
- domain
- Design
- category
- UX research
- level
- Intermediate
- made for
- UX researcher, Product / UX / UI designer, Product manager, Founder / business owner
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-03
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install ux-research-study-track --target claude-codenpx skills add hermes-hq/hodios-dist --skill ux-research-study-track -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-design@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of UX researchWrite a research screener
Writes a participant screener for interviews or usability tests with behavioural qualifying questions, disqualifiers that hide the target, quotas and an invite message.
write-research-screenerWrite a usability test plan
Writes a usability test plan with scenario tasks, success metrics, participant criteria, a screener and a moderator script, tied to the research questions. Use before running a usability study.
write-usability-test-planWrite a customer interview guide
Writes a discovery interview guide that asks about specific past behaviour instead of opinions or hypotheticals, with timed sections, follow-up probes and a check for leading questions.
write-customer-interview-guideSynthesize usability test findings
Turns raw usability session notes into evidence-backed issues rated by severity and frequency, with task results and recommendations. Use after a round of usability sessions.
synthesize-usability-findingsSynthesize customer interviews
Synthesises customer interview transcripts into themes, needs, pains and verbatim quotes, with how many participants support each and a confidence level. Use after a round of interviews.
synthesize-customer-interviewsUX researcher
UX researcher who matches the method to the question, separates what people did from what it means, and protects participants. Use as a partner for planning, running and synthesising research.
ux-researcher