UX Research

Triggers

• ux research
• user research
• usability testing
• user interviews
• user persona
• user journey
• journey mapping
• a/b testing
• user behavior
• user insights
• research study
• survey design
• participant recruitment
• task analysis
• heuristic evaluation
• user satisfaction
• user needs
• competitive analysis
• research methodology

Instructions

Research Planning

Before conducting any research:

1. Define clear research questions and objectives
2. Select appropriate methodology (qualitative, quantitative, mixed methods)
3. Determine sample size with statistical justification
4. Design participant recruitment and screening criteria
5. Create study materials (scripts, surveys, prototypes)
6. Plan data collection, consent, and privacy procedures
7. Establish analysis plan for synthesizing findings

Research Methodologies

Qualitative Methods

• User Interviews: Semi-structured, 45-60 minutes, with think-aloud protocol
• Contextual Inquiry: Observing users in their natural environment
• Focus Groups: Moderated group discussions for exploratory research
• Card Sorting: Open or closed sorting for information architecture
• Diary Studies: Longitudinal self-reported usage and experience data

Quantitative Methods

• Surveys: Validated scales (SUS, NPS, CSAT) with proper sampling
• A/B Testing: Controlled experiments with statistical significance testing
• Analytics Analysis: Behavioral data patterns from usage metrics
• Benchmarking: Task completion rates, time on task, error rates

Usability Testing

• Session Structure: Introduction (5 min), baseline questions (10 min), task scenarios (35 min), post-test interview (10 min)
• Data Collection: Task completion rate, time on task, error count, satisfaction rating
• Think-Aloud Protocol: Participants verbalize thoughts during task performance
• Observer Roles: Moderator, note-taker, observer with defined responsibilities

User Persona Development

Build personas from empirical data:

• Demographics and context (age, location, occupation, tech proficiency)
• Behavioral patterns (usage frequency, task priorities, decision factors)
• Goals and needs (primary/secondary objectives, success criteria)
• Pain points and motivations
• Context of use (environment, time constraints, social context)
• Direct quotes from research supporting each attribute

Journey Mapping

Map complete user journeys with:

• Touchpoints: Key interaction points with the product/service
• Actions: What the user does at each stage
• Thoughts: Internal dialogue and decision-making
• Emotions: Emotional state throughout the journey (satisfaction/frustration curve)
• Pain Points: Friction areas and problems
• Opportunities: Improvement areas at each stage

Research Ethics

• Obtain informed consent before all research activities
• Protect participant privacy and data security
• Ensure inclusive recruitment across diverse demographics
• Present findings objectively without confirmation bias
• Store and handle research data securely

EloPhanto Tool Integration

• Use web_search to conduct competitive research and find benchmark data
• Use browser_navigate to perform heuristic evaluations of live products
• Use knowledge_write to build research repositories and persona libraries

Analysis and Synthesis

1. Thematic Analysis: Code qualitative data, identify themes and patterns
2. Statistical Analysis: Calculate significance, confidence intervals, effect sizes
3. Affinity Mapping: Cluster insights into actionable categories
4. Triangulation: Validate findings across multiple data sources
5. Prioritized Recommendations: Impact vs. effort matrix for design changes

Deliverables

Research Study Plan Template

# User Research Study Plan

## Research Objectives
**Primary Questions**: [What we need to learn]
**Success Metrics**: [How we measure research success]
**Business Impact**: [How findings influence product decisions]

## Methodology
**Research Type**: [Qualitative, Quantitative, Mixed Methods]
**Methods Selected**: [Interviews, Surveys, Usability Testing, Analytics]
**Rationale**: [Why these methods answer our questions]

## Participant Criteria
**Primary Users**: [Target audience characteristics]
**Sample Size**: [Number with statistical justification]
**Recruitment**: [How and where to find participants]
**Screening**: [Qualification criteria and bias prevention]

## Study Protocol
**Timeline**: [Schedule and milestones]
**Materials**: [Scripts, surveys, prototypes, tools]
**Data Collection**: [Recording, consent, privacy procedures]
**Analysis Plan**: [How findings will be processed]

User Persona Template

# User Persona: [Name]

## Demographics & Context
Age, Location, Occupation, Tech Proficiency, Device Preferences

## Behavioral Patterns
Usage Frequency, Task Priorities, Decision Factors, Pain Points, Motivations

## Goals & Needs
Primary Goals, Secondary Goals, Success Criteria, Information Needs

## Context of Use
Environment, Time Constraints, Distractions, Social Context

## Quotes & Insights
> "[Direct quote from research]"
**Research Evidence**: Based on [X] interviews, [Y] survey responses

Research Findings Template

# [Project Name] User Research Findings

## Research Overview
**Objectives**: [What we sought to learn]
**Methods**: [Approaches used]
**Participants**: [Sample size and demographics]

## Key Findings
1. [Primary Finding]: [Description and impact]
2. [Secondary Finding]: [Description and impact]
3. [Supporting Finding]: [Description and impact]

## Recommendations
### High Priority (Immediate)
- [Recommendation]: Impact, Effort, Success Metric

### Medium Priority (Next Quarter)
- [Recommendation]: Impact, Effort, Success Metric

## Success Metrics
- Task completion rate: Target [X]% improvement
- Time on task: Target [Y]% reduction
- Error rate: Target [Z]% decrease
- User satisfaction: Target [A]+ rating

Success Metrics

• Research recommendations are implemented by design and product teams (80%+ adoption)
• User satisfaction scores improve measurably after implementing research insights
• Product decisions are consistently informed by user research data
• Research findings prevent costly design mistakes and development rework
• User needs are clearly understood and validated across the organization

Verify

• The change was rendered in a browser/simulator and a screenshot or DOM snapshot was captured, not just code-reviewed
• Layout was checked at the breakpoints the ux-research guide calls out (mobile + desktop minimum); evidence of each is attached
• Color, typography, and spacing values used come from the project's design tokens / theme, not hard-coded ad-hoc values
• Keyboard navigation and focus order were exercised on every interactive element introduced
• Reduced-motion / dark-mode (when supported) variants were verified, not assumed to inherit
• No console errors or hydration warnings were emitted during the verification render