Conduct a User Research Study

Write the question that would change a product decision. That question chooses the method: interview, survey, or both.

• Product
  Problem Statement FrameworkCreate clear, actionable problem statements that align teams and drive focused solutions.

Define who has the experience you need, then write a screener that finds them. Book a couple of extras so the calendar still holds.

• Research
  User Research Recruitment PlanCreate participant criteria and recruitment materials for user research studies.
• Research
  Participant Screener Survey BuilderDraft a recruitment screener with intro copy, behavioral and qualifying items, explicit disqualifiers, routing notes, and recruiter guidance. Goes deeper than a high-level recruitment plan.
• Research
  Participant Consent & Session CommsPlain-language consent and logistics: recording, data use, how to stop, incentive, and calendar copy. Variants for interviews, usability tests, surveys, and diaries.

Build the guide around the last time they did the work. Behavioral questions give you answers you can quote. If the session has tasks or a prototype, use the Moderated Discussion Guide instead.

• Research
  User Interview GuideSimple generative interview outline: objectives, question sets, probes. Need a timed session with tasks or a concept? Use Moderated Discussion Guide Generator, Usability Test Script, or Concept Test Protocol instead.

Run the sessions. After each one, turn the transcript into a debrief so synthesis is clustering evidence, not reconstructing memory.

• Research
  Session Debrief From TranscriptTurn one interview or usability transcript into structured notes: task outcomes, timestamped quotes, surprises, and follow-ups. Not a full-study synthesis. Run after each session; affinity mapping comes later.

Cluster debriefs into themes with coverage counts. Then write insight statements. Do not skip to a mixed-source report from raw notes.

• Research
  Affinity Mapping AssistantSynthesize raw qual data (interviews, usability, diaries) using an affinity-style flow: clean, code, cluster into themes with evidence counts, outliers, severity-weighted ranking, and surprises.
• Research
  Research Insight Statement WriterTurn themes and observations into decision-ready insight statements (Observation, Pattern, Implication, Recommendation) plus a short exec "So What" summary. Use after synthesis or affinity output.

Open the readout with what should change and the evidence behind it. Method belongs in the appendix.

• Research
  Research Readout BuilderBuild a research readout deck structure: TL;DR, overview, one slide per finding with evidence and recommendations, prioritized actions, unknowns, appendix, plus speaker notes. More research-specific than generic shareouts.