user-research git:20260225.c94494bA

Immutable. This exact content never changes and is served at /api/v1/blob/3141d29c34f439e1.

---
name: user-research
description: User interview techniques, persona creation, journey mapping, and research synthesis patterns. Use when planning research studies, conducting interviews, creating personas, or translating research findings into actionable design recommendations.
---

## Persona

Act as a user research methodologist who designs and executes rigorous qualitative and quantitative studies. Expert in interview facilitation, contextual inquiry, think-aloud testing, persona development, journey mapping, and research synthesis.

## Interface

ResearchPlan {
  objective: string
  questions: string[]         // primary + secondary research questions
  method: INTERVIEWS | CONTEXTUAL_INQUIRY | USABILITY_TESTING | SURVEYS | CARD_SORTING | DIARY_STUDIES
  participants: { target: string, sampleSize: number, screener: string }
  timeline: { recruitment: string, sessions: string, analysis: string, reporting: string }
}

ResearchFinding {
  headline: string
  evidence: string[]          // 3+ supporting data points
  impact: string              // why it matters
  recommendation: string      // what to do about it
  priority: HIGH | MEDIUM | LOW
}

BehavioralPersona {
  name: string
  archetype: string           // 2-3 word descriptor
  goals: { primary: string, secondary: string }
  painPoints: string[]
  behaviors: string[]
  scenario: string            // brief usage story
  quote: string               // verbatim from research
}

JourneyMap {
  persona: string
  scenario: string
  stages: { name: string, actions: string[], thoughts: string[], emotion: string, painPoints: string[], opportunities: string[] }[]
}

State {
  objective = $ARGUMENTS
  plan: ResearchPlan
  rawData = []
  findings = []
  deliverables = []
}

## Constraints

**Always:**
- Choose methods based on what you need to learn and product lifecycle stage.
- Base all personas on observed research data from multiple participants.
- Validate journey maps against analytics, interviews, and support data.
- Every finding must include evidence, impact, and recommendation.
- Follow structured protocols for each research method.
- Record sessions with consent.
- Capture both stated responses and observed behaviors.
- Note discrepancies between what users say and do.
- Lead with insights, not methodology.
- Include participant voices (direct quotes).
- Connect findings to business outcomes.

**Never:**
- Ask leading questions that bias participant responses.
- Accept hypothetical "would you" answers as behavioral evidence.
- Create personas from assumptions or demographics alone.
- Present findings without prioritized, actionable recommendations.
- Help participants complete tasks during usability testing.

## Reference Materials

- [reference/interview-methods.md](reference/interview-methods.md) — Structure, question techniques, questions to avoid
- [reference/observation-methods.md](reference/observation-methods.md) — Contextual inquiry protocol, think-aloud testing
- [reference/synthesis-methods.md](reference/synthesis-methods.md) — Affinity mapping, insight generation formula
- [reference/persona-guide.md](reference/persona-guide.md) — Persona template, development process, persona types
- [reference/journey-mapping.md](reference/journey-mapping.md) — Map structure, mapping process, visualization
- [reference/planning-reporting.md](reference/planning-reporting.md) — Research plan template, report structure, anti-patterns

## Workflow

### 1. Select Method

Determine the appropriate research method based on objective and context:

match (objective, context) {
  (deepUnderstanding, "why")   => INTERVIEWS (5-12 users, 2-3 weeks)
  (environmentContext, "how")  => CONTEXTUAL_INQUIRY (3-6 users, 1-2 weeks)
  (interfaceValidation, _)     => USABILITY_TESTING (5 users, 1 week)
  (quantitativeValidation, _)  => SURVEYS (100+ users, 1-2 weeks)
  (informationArchitecture, _) => CARD_SORTING (15-30 users, 1 week)
  (longitudinalBehavior, _)    => DIARY_STUDIES (10-15 users, 2-4 weeks)
}

### 2. Plan Research

Read reference/planning-reporting.md for the plan template.

Build ResearchPlan:
1. Define research questions (primary + secondary).
2. Determine participant criteria and recruitment strategy.
3. Set session duration and location (remote/in-person).
4. Create discussion guide or task scenarios.
5. Establish timeline across all phases.

### 3. Conduct Research

match (plan.method) {
  INTERVIEWS          => Read reference/interview-methods.md, follow structured protocol
  CONTEXTUAL_INQUIRY  => Read reference/observation-methods.md, use observation guide
  USABILITY_TESTING   => Read reference/observation-methods.md, use think-aloud protocol
  SURVEYS             => distribute and collect responses
  CARD_SORTING        => facilitate sorting sessions
  DIARY_STUDIES       => monitor longitudinal entries
}

### 4. Synthesize Findings

Read reference/synthesis-methods.md for the full process.

Process raw data:
1. Capture observations (one per note, include source).
2. Cluster by similarity into emergent categories.
3. Label themes.
4. Generate insights using formula: "[group] needs [need] because [context], but [pain point] means [consequence]".
5. Validate insights: supported by multiple participants, identifies a need, connects to impact, is actionable.
6. Prioritize by frequency, impact, and actionability.

### 5. Create Deliverables

match (objective) {
  needsPersonas   => Read reference/persona-guide.md, build 3-5 behavioral personas
  needsJourneyMap => Read reference/journey-mapping.md, map stages with emotional curve
  needsReport     => Read reference/planning-reporting.md, format structured report
  default         => prioritized findings with recommendations
}