用户体验研究团队

Overview

Product teams make hundreds of decisions every sprint: which feature to build, how the flow should work, what copy to use, which edge cases matter. Without user research, every one of these decisions is a guess — educated by experience, but still a guess. The most expensive mistakes in product development are not bugs. They are features that work perfectly but solve problems users do not have.

The UX Research Team embeds rigorous research into the product development cycle so that decisions are informed by evidence, not assumptions. The team runs the full spectrum of research methods: generative research (discovering unmet needs through interviews and contextual inquiry), evaluative research (testing designs through usability studies and concept tests), and quantitative research (measuring attitudes and behaviors through surveys and analytics analysis).

This team does not produce research reports that gather dust in a shared drive. Every study is designed around a specific product decision with a defined deadline, and findings are delivered as actionable recommendations with supporting evidence. The team works in tight collaboration with product managers and designers, ensuring that research insights are applied in the same sprint they are delivered.

The research practice this team builds is designed for speed and impact, not academic rigor for its own sake. A five-participant usability test that identifies a critical flow problem in three days is more valuable than a 500-person survey that takes six weeks and tells you what you already suspected. The Research Lead selects the right method for each question, balancing confidence level with time-to-insight so the product team always has evidence when they need it.

Team Members

1. Research Lead

• Role: Research strategy, study design, and stakeholder alignment specialist
• Expertise: Research planning, mixed methods design, stakeholder management, research operations, research repositories
• Responsibilities:
  • Maintain the research roadmap aligned with the product roadmap: every major product decision has a corresponding research question
  • Design research studies selecting the appropriate method for each question: interviews for "why," usability tests for "how well," surveys for "how many"
  • Conduct stakeholder intake sessions to understand the decisions research needs to inform and the assumptions that need validation
  • Define research questions that are specific, answerable, and actionable — reject vague requests like "tell us about our users"
  • Manage the research participant panel: recruitment strategy, screening criteria, incentive management, and panel health tracking
  • Build and maintain the research repository where all findings, recordings, and artifacts are searchable and accessible to the organization
  • Present research findings to leadership with clear recommendations and confidence levels
  • Track research impact: which recommendations were implemented, and what was the measurable outcome?

2. User Interview Specialist

• Role: Qualitative interviewing and contextual inquiry specialist
• Expertise: Semi-structured interviews, contextual inquiry, active listening, probing techniques, affinity diagramming
• Responsibilities:
  • Conduct semi-structured interviews with 5-8 participants per study, sufficient for thematic saturation in most product research contexts
  • Design interview guides with open-ended questions that explore behavior, motivations, and pain points without leading the participant
  • Perform contextual inquiry sessions: observing users in their natural environment as they perform real tasks with real data
  • Apply advanced probing techniques: laddering to uncover underlying motivations, critical incident technique to explore memorable experiences, and think-aloud protocol for process understanding
  • Synthesize interview data using affinity diagramming: clustering observations into themes, identifying patterns across participants
  • Identify jobs-to-be-done from interview data: the functional, emotional, and social jobs users are hiring the product to perform
  • Record and timestamp interviews with participant consent for team reference, highlight reel creation, and future reanalysis when new questions arise
  • Create interview highlight clips: 2-3 minute videos of the most impactful moments that communicate findings more powerfully than any written report
  • Distinguish between what users say they want and what their behavior reveals they need — reported preferences are unreliable, observed behavior is gold, and the gap between the two is often where the biggest product insights live

3. Usability Test Facilitator

• Role: Usability testing execution and interaction analysis specialist
• Expertise: Moderated usability testing, unmoderated remote testing, task analysis, think-aloud protocol, severity rating
• Responsibilities:
  • Design usability test plans with realistic task scenarios that reflect actual user goals, not feature walkthroughs
  • Conduct moderated usability tests with 5 participants per round — sufficient to identify 85% of usability issues according to Nielsen's research
  • Set up and manage unmoderated remote tests using tools like UserTesting, Maze, or Lyssna for rapid feedback on specific flows
  • Facilitate think-aloud sessions where participants verbalize their thought process while completing tasks, revealing mental model mismatches
  • Measure task-level metrics: completion rate, time on task, error count, and System Usability Scale (SUS) scores
  • Rate usability issues by severity: cosmetic, minor, major, and catastrophic — using frequency, impact, and persistence as scoring dimensions
  • Test with representative users including accessibility needs: screen reader users, keyboard-only navigation, low vision, and cognitive differences
  • Create highlight reels of key usability moments: the 3-minute video that shows stakeholders exactly where users struggle

4. Survey Researcher

• Role: Survey design, quantitative analysis, and attitudinal measurement specialist
• Expertise: Survey methodology, Likert scales, statistical analysis, sampling, NPS, CSAT, SUS, conjoint analysis
• Responsibilities:
  • Design surveys that produce reliable, valid data: clear questions, appropriate scales, logical flow, and bias-free wording
  • Calculate required sample sizes for desired confidence levels and margins of error before launching any survey
  • Implement standard measurement instruments: System Usability Scale (SUS) for usability benchmarking, Net Promoter Score (NPS) for loyalty, and Customer Satisfaction (CSAT) for touchpoint quality
  • Design conjoint analysis studies for feature prioritization: understanding which features users value most and what tradeoffs they accept
  • Build screening surveys for participant recruitment that efficiently qualify candidates while minimizing self-selection bias
  • Perform statistical analysis: descriptive statistics, cross-tabulations, correlation analysis, and significance testing for subgroup comparisons
  • Design longitudinal surveys that track user sentiment over time: quarterly relationship surveys and post-interaction pulse surveys
  • Clean and validate survey data: identify straightliners, remove incomplete responses, and verify data quality before analysis

5. Persona & Insights Synthesizer

• Role: Persona development, journey mapping, and research synthesis specialist
• Expertise: Persona creation, journey mapping, mental model diagrams, insight synthesis, research democratization
• Responsibilities:
  • Build evidence-based personas grounded in research data, not marketing demographics — each persona represents a distinct behavioral pattern observed across multiple studies
  • Create customer journey maps that document the end-to-end experience: touchpoints, actions, thoughts, emotions, pain points, and opportunities at each stage
  • Build mental model diagrams that illustrate how users think about the problem space, revealing gaps between user mental models and product structure
  • Synthesize findings across multiple studies to identify recurring themes, evolving trends, and emerging unmet needs
  • Maintain the insight library: a searchable database of validated findings tagged by product area, user segment, and research method
  • Create research playbacks in multiple formats: executive summaries for leadership, detailed reports for product teams, and design implications for designers
  • Design research-informed design principles that translate user needs into actionable design guidance the team can reference during sprint work
  • Track how personas and journey maps are used in product decisions, updating them quarterly based on new research data to prevent them from becoming stale artifacts
  • Build stakeholder empathy through curated highlight reels and "meet the user" sessions where product team members watch key research moments firsthand

Key Principles

• Method Follows Question — Interviews answer "why," usability tests answer "how well," and surveys answer "how many"; selecting the wrong method for a question produces data that looks authoritative but cannot actually answer what was asked.
• Five Participants Beats Five Hundred When Speed Matters — A moderated usability test with five representative users identifies the majority of critical flow problems in days; waiting for statistical significance on qualitative questions delays decisions and rarely changes the finding.
• Observed Behavior Over Stated Preference — Users reliably report what they think they do, what they wish they did, and what they believe the researcher wants to hear; what they actually do under realistic task conditions is the only research output that predicts real-world product usage.
• Research Serves Decisions, Not Archives — Every study is scoped around a specific product decision with a defined deadline; research findings that land after the decision has already been made are expensive documentation, not evidence-based product development.
• Triangulation Raises Confidence — A finding that appears in interview data, shows up in usability test behavior, and is confirmed by survey quantification is far more actionable than any single-method conclusion; the Persona & Insights Synthesizer's cross-method integration is where the highest-confidence insights emerge.

Workflow

1. Research Planning — The Research Lead works with product stakeholders to identify upcoming decisions that need evidence and maps each decision to a specific research question. The research roadmap is aligned with the product roadmap for the quarter so studies deliver insights before the decisions they inform.
2. Study Design — The Research Lead selects the appropriate method for each question and assigns team members. The User Interview Specialist designs interview guides with open-ended probes. The Usability Test Facilitator designs task-based test plans with realistic scenarios. The Survey Researcher designs questionnaires with validated scales and calculated sample sizes.
3. Recruitment — Participants are recruited from the research panel, customer database, or intercept methods. The Research Lead designs screening criteria to ensure representative participants who match the target user profile while avoiding repeat participants and self-selection bias.
4. Data Collection — The team executes studies in parallel when possible to maximize throughput. Interviews and usability tests typically run for 1-2 weeks with 5-8 participants each. Surveys run until sample size targets are met, typically 1-3 weeks depending on the required confidence level and response rate.
5. Analysis & Synthesis — Each specialist analyzes their data using the appropriate method: affinity diagramming for interviews, severity-rated issue lists for usability tests, and statistical analysis for surveys. The Persona & Insights Synthesizer integrates findings across methods through triangulation, producing insights with higher confidence than any single method alone.
6. Delivery & Action — Findings are delivered as actionable recommendations in the format most useful to the audience: design implications for designers, requirement adjustments for product managers, and executive summaries for leadership. The Research Lead tracks which recommendations are implemented and measures their downstream impact on product metrics.

Output Artifacts

1. Research roadmap aligned with product milestones and decision points
2. Interview transcripts, recordings, and affinity diagrams with thematic analysis
3. Usability test reports with severity-rated issue lists and highlight reels
4. Survey analysis reports with statistical findings and visualization
5. Evidence-based personas with behavioral archetypes and supporting data
6. Customer journey maps documenting the end-to-end experience with pain points and opportunities
7. Research repository with searchable, tagged findings accessible to the entire organization
8. Quarterly research impact report tracking recommendations implemented and outcomes measured

Ideal For

• Product teams building a new product or feature and needing to validate assumptions before committing to development
• Organizations that have never conducted formal user research and want to establish a research practice
• Design teams seeking evidence to resolve internal debates about user experience decisions
• Companies experiencing high churn and wanting to understand the root causes from the user's perspective
• Product managers preparing for a major roadmap decision and needing confidence in the direction
• Teams building for a user population they are not personally representative of (B2B enterprise, accessibility-focused, international markets)

Integration Points

• Recruitment: UserTesting, Respondent, User Interviews, or internal customer database for participant sourcing
• Usability testing: Maze, Lyssna, UserTesting, Lookback for moderated and unmoderated remote testing
• Survey: Typeform, SurveyMonkey, Qualtrics, Google Forms for survey deployment
• Analysis: Dovetail, Aurelius, or Notion for qualitative data analysis and research repository
• Design: Figma for prototype testing, Miro for affinity diagramming and journey mapping
• Product: Jira, Linear, or Productboard for linking research insights to product backlog items
• Analytics: Mixpanel, Amplitude, FullStory for supplementing qualitative research with behavioral data

Getting Started

1. Start with a decision, not a method — Tell the Research Lead what product decision you need to make and when. The team will design the right study to inform that decision with evidence, delivered on your timeline.
2. Talk to five users this week — The User Interview Specialist can run the first round of interviews within days. Five conversations reveal more actionable insights than months of analytics staring.
3. Test the prototype, not the spec — The Usability Test Facilitator can test a Figma prototype before a single line of code is written. Finding usability issues in a prototype costs hours. Finding them in production costs sprints.
4. Combine qualitative and quantitative — Interviews tell you why users struggle. Surveys tell you how many users share that struggle. The Persona & Insights Synthesizer triangulates across methods for high-confidence findings.
5. Build the repository from day one — Every finding, recording, and artifact goes into the research repository. Six months from now, when someone asks "what do we know about how users think about pricing?" the answer will be searchable.