ux-researcher-designer

# UX Researcher & Designer

Generate user personas from research data, create journey maps, plan usability tests, and synthesize research findings into actionable design recommendations.

---

## Table of Contents

- [Trigger Terms](#trigger-terms)
- [Workflows](#workflows)
  - [Workflow 1: Generate User Persona](#workflow-1-generate-user-persona)
  - [Workflow 2: Create Journey Map](#workflow-2-create-journey-map)
  - [Workflow 3: Plan Usability Test](#workflow-3-plan-usability-test)
  - [Workflow 4: Synthesize Research](#workflow-4-synthesize-research)
- [Tool Reference](#tool-reference)
- [Quick Reference Tables](#quick-reference-tables)
- [Knowledge Base](#knowledge-base)

---

## Trigger Terms

Use this skill when you need to:

- "create user persona"
- "generate persona from data"
- "build customer journey map"
- "map user journey"
- "plan usability test"
- "design usability study"
- "analyze user research"
- "synthesize interview findings"
- "identify user pain points"
- "define user archetypes"
- "calculate research sample size"
- "create empathy map"
- "identify user needs"

---

## Workflows

### Workflow 1: Generate User Persona

**Situation:** You have user data (analytics, surveys, interviews) and need to create a research-backed persona.

**Steps:**

1. **Prepare user data**

   Required format (JSON):
   ```json
   [
     {
       "user_id": "user_1",
       "age": 32,
       "usage_frequency": "daily",
       "features_used": ["dashboard", "reports", "export"],
       "primary_device": "desktop",
       "usage_context": "work",
       "tech_proficiency": 7,
       "pain_points": ["slow loading", "confusing UI"]
     }
   ]
   ```

2. **Run persona generator**
   ```bash
   # Human-readable output
   python scripts/persona_generator.py

   # JSON output for integration
   python scripts/persona_generator.py json
   ```

3. **Review generated components**

   | Component | What to Check |
   |-----------|---------------|
   | Archetype | Does it match the data patterns? |
   | Demographics | Are they derived from actual data? |
   | Goals | Are they specific and actionable? |
   | Frustrations | Do they include frequency counts? |
   | Design implications | Can designers act on these? |

4. **Validate persona**

   - Show to 3-5 real users: "Does this sound like you?"
   - Cross-check with support tickets
   - Verify against analytics data

5. **Reference:** See `references/persona-methodology.md` for validity criteria

---

### Workflow 2: Create Journey Map

**Situation:** You need to visualize the end-to-end user experience for a specific goal.

**Steps:**

1. **Define scope**

   | Element | Description |
   |---------|-------------|
   | Persona | Which user type |
   | Goal | What they're trying to achieve |
   | Start | Trigger that begins journey |
   | End | Success criteria |
   | Timeframe | Hours/days/weeks |

2. **Gather journey data**

   Sources:
   - User interviews (ask "walk me through...")
   - Session recordings
   - Analytics (funnel, drop-offs)
   - Support tickets

3. **Map the stages**

   Typical B2B SaaS stages:
   ```
   Awareness → Evaluation → Onboarding → Adoption → Advocacy
   ```

4. **Fill in layers for each stage**

   ```
   Stage: [Name]
   ├── Actions: What does user do?
   ├── Touchpoints: Where do they interact?
   ├── Emotions: How do they feel? (1-5)
   ├── Pain Points: What frustrates them?
   └── Opportunities: Where can we improve?
   ```

5. **Identify opportunities**

   Priority Score = Frequency × Severity × Solvability

6. **Reference:** See `references/journey-mapping-guide.md` for templates

---

### Workflow 3: Plan Usability Test

**Situation:** You need to validate a design with real users.

**Steps:**

1. **Define research questions**

   Transform vague goals into testable questions:

   | Vague | Testable |
   |-------|----------|
   | "Is it easy to use?" | "Can users complete checkout in <3 min?" |
   | "Do users like it?" | "Will users choose Design A or B?" |
   | "Does it make sense?" | "Can users find settings without hints?" |

2. **Select method**

   | Method | Participants | Duration | Best For |
   |--------|--------------|----------|----------|
   | Moderated remote | 5-8 | 45-60 min | Deep insights |
   | Unmoderated remote | 10-20 | 15-20 min | Quick validation |
   | Guerrilla | 3-5 | 5-10 min | Rapid feedback |

3. **Design tasks**

   Good task format:
   ```
   SCENARIO: "Imagine you're planning a trip to Paris..."
   GOAL: "Book a hotel for 3 nights in your budget."
   SUCCESS: "You see the confirmation page."
   ```

   Task progression: Warm-up → Core → Secondary → Edge case → Free exploration

4. **Define success metrics**

   | Metric | Target |
   |--------|--------|
   | Completion rate | >80% |
   | Time on task | <2× expected |
   | Error rate | <15% |
   | Satisfaction | >4/5 |

5. **Prepare moderator guide**

   - Think-aloud instructions
   - Non-leading prompts
   - Post-task questions

6. **Reference:** See `references/usability-testing-frameworks.md` for full guide

---

### Workflow 4: Synthesize Research

**Situation:** You have raw research data (interviews, surveys, observations) and need actionable insights.

**Steps:**

1. **Code the data**

   Tag each data point:
   - `[GOAL]` - What they want to achieve
   - `[PAIN]` - What frustrates them
   - `[BEHAVIOR]` - What they actually do
   - `[CONTEXT]` - When/where they use product
   - `[QUOTE]` - Direct user words

2. **Cluster similar patterns**

   ```
   User A: Uses daily, advanced features, shortcuts
   User B: Uses daily, complex workflows, automation
   User C: Uses weekly, basic needs, occasional

   Cluster 1: A, B (Power Users)
   Cluster 2: C (Casual User)
   ```

3. **Calculate segment sizes**

   | Cluster | Users | % | Viability |
   |---------|-------|---|-----------|
   | Power Users | 18 | 36% | Primary persona |
   | Business Users | 15 | 30% | Primary persona |
   | Casual Users | 12 | 24% | Secondary persona |

4. **Extract key findings**

   For each theme:
   - Finding statement
   - Supporting evidence (quotes, data)
   - Frequency (X/Y participants)
   - Business impact
   - Recommendation

5. **Prioritize opportunities**

   | Factor | Score 1-5 |
   |--------|-----------|
   | Frequency | How often does this occur? |
   | Severity | How much does it hurt? |
   | Breadth | How many users affected? |
   | Solvability | Can we fix this? |

6. **Reference:** See `references/persona-methodology.md` for analysis framework

---

## Tool Reference

### persona_generator.py

Generates data-driven personas from user research data.

| Argument | Values | Default | Description |
|----------|--------|---------|-------------|
| format | (none), json | (none) | Output format |

**Sample Output:**

```
============================================================
PERSONA: Alex the Power User
============================================================

📝 A daily user who primarily uses the product for work purposes

Archetype: Power User
Quote: "I need tools that can keep up with my workflow"

👤 Demographics:
  • Age Range: 25-34
  • Location Type: Urban
  • Tech Proficiency: Advanced

🎯 Goals & Needs:
  • Complete tasks efficiently
  • Automate workflows
  • Access advanced features

😤 Frustrations:
  • Slow loading times (14/20 users)
  • No keyboard shortcuts
  • Limited API access

💡 Design Implications:
  → Optimize for speed and efficiency
  → Provide keyboard shortcuts and power features
  → Expose API and automation capabilities

📈 Data: Based on 45 users
    Confidence: High
```

**Archetypes Generated:**

| Archetype | Signals | Design Focus |
|-----------|---------|--------------|
| power_user | Daily use, 10+ features | Efficiency, customization |
| casual_user | Weekly use, 3-5 features | Simplicity, guidance |
| business_user | Work context, team use | Collaboration, reporting |
| mobile_first | Mobile primary | Touch, offline, speed |

**Output Components:**

| Component | Description |
|-----------|-------------|
| demographics | Age range, location, occupation, tech level |
| psychographics | Motivations, values, attitudes, lifestyle |
| behaviors | Usage patterns, feature preferences |
| needs_and_goals | Primary, secondary, functional, emotional |
| frustrations | Pain points with evidence |
| scenarios | Contextual usage stories |
| design_implications | Actionable recommendations |
| data_points | Sample size, confidence level |

---

## Quick Reference Tables

### Research Method Selection

| Question Type | Best Method | Sample Size |
|---------------|-------------|-------------|
| "What do users do?" | Analytics, observation | 100+ events |
| "Why do they do it?" | Interviews | 8-15 users |
| "How well can they do it?" | Usability test | 5-8 users |
| "What do they prefer?" | Survey, A/B test | 50+ users |
| "What do they feel?" | Diary study, interviews | 10-15 users |

### Persona Confidence Levels

| Sample Size | Confidence | Use Case |
|-------------|------------|----------|
| 5-10 users | Low | Exploratory |
| 11-30 users | Medium | Directional |
| 31+ users | High | Production |

### Usability Issue Severity

| Severity | Definition | Action |
|----------|------------|--------|
| 4 - Critical | Prevents task completion | Fix immediately |
| 3 - Major | Significant difficulty | Fix before release |
| 2 - Minor | Causes hesitation | Fix when possible |
| 1 - Cosmetic | Noticed but not problematic | Low priority |

### Interview Question Types

| Type | Example | Use For |
|------|---------|---------|
| Context | "Walk me through your typical day" | Understanding environment |
| Behavior | "Show me how you do X" | Observing actual actions |
| Goals | "What are you trying to achieve?" | Uncovering motivations |
| Pain | "What's the hardest part?" | Identifying frustrations |
| Reflection | "What would you change?" | Generating ideas |

---

## Knowledge Base

Detailed reference guides in `references/`:

| File | Content |
|------|---------|
| `persona-methodology.md` | Validity criteria, data collection, analysis framework |
| `journey-mapping-guide.md` | Mapping process, templates, opportunity identification |
| `example-personas.md` | 3 complete persona examples with data |
| `usability-testing-frameworks.md` | Test planning, task design, analysis |

---

## Validation Checklist

### Persona Quality
- [ ] Based on 20+ users (minimum)
- [ ] At least 2 data sources (quant + qual)
- [ ] Specific, actionable goals
- [ ] Frustrations include frequency counts
- [ ] Design implications are specific
- [ ] Confidence level stated

### Journey Map Quality
- [ ] Scope clearly defined (persona, goal, timeframe)
- [ ] Based on real user data, not assumptions
- [ ] All layers filled (actions, touchpoints, emotions)
- [ ] Pain points identified per stage
- [ ] Opportunities prioritized

### Usability Test Quality
- [ ] Research questions are testable
- [ ] Tasks are realistic scenarios, not instructions
- [ ] 5+ participants per design
- [ ] Success metrics defined
- [ ] Findings include severity ratings

### Research Synthesis Quality
- [ ] Data coded consistently
- [ ] Patterns based on 3+ data points
- [ ] Findings include evidence
- [ ] Recommendations are actionable
- [ ] Priorities justified

## Related Skills

- **UI Design System** (`product-team/ui-design-system/`) — Research findings inform design system decisions
- **Product Manager Toolkit** (`product-team/product-manager-toolkit/`) — Customer interview analysis complements persona research

{
  "format": "aiskill/v1",
  "skill": {
    "name": "ux-researcher-designer",
    "slug": "ux-researcher-designer",
    "version": "1.0.0",
    "description": "UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis. Use when conducting user research, creating personas, mapping user journeys, planning usability tests, or validating designs.",
    "category": "Business",
    "tags": [
      "product-business",
      "testing",
      "research",
      "design"
    ],
    "platforms": [
      "chatgpt",
      "claude-code",
      "cursor"
    ],
    "tested_environment": "Agent Skills convention (SKILL.md) — works with Claude Code, Cursor, ChatGPT/Codex and compatible agents",
    "license": "MIT"
  },
  "prompts": {
    "system": "# UX Researcher & Designer\r\n\r\nGenerate user personas from research data, create journey maps, plan usability tests, and synthesize research findings into actionable design recommendations.\r\n\r\n---\r\n\r\n## Table of Contents\r\n\r\n- [Trigger Terms](#trigger-terms)\r\n- [Workflows](#workflows)\r\n  - [Workflow 1: Generate User Persona](#workflow-1-generate-user-persona)\r\n  - [Workflow 2: Create Journey Map](#workflow-2-create-journey-map)\r\n  - [Workflow 3: Plan Usability Test](#workflow-3-plan-usability-test)\r\n  - [Workflow 4: Synthesize Research](#workflow-4-synthesize-research)\r\n- [Tool Reference](#tool-reference)\r\n- [Quick Reference Tables](#quick-reference-tables)\r\n- [Knowledge Base](#knowledge-base)\r\n\r\n---\r\n\r\n## Trigger Terms\r\n\r\nUse this skill when you need to:\r\n\r\n- \"create user persona\"\r\n- \"generate persona from data\"\r\n- \"build customer journey map\"\r\n- \"map user journey\"\r\n- \"plan usability test\"\r\n- \"design usability study\"\r\n- \"analyze user research\"\r\n- \"synthesize interview findings\"\r\n- \"identify user pain points\"\r\n- \"define user archetypes\"\r\n- \"calculate research sample size\"\r\n- \"create empathy map\"\r\n- \"identify user needs\"\r\n\r\n---\r\n\r\n## Workflows\r\n\r\n### Workflow 1: Generate User Persona\r\n\r\n**Situation:** You have user data (analytics, surveys, interviews) and need to create a research-backed persona.\r\n\r\n**Steps:**\r\n\r\n1. **Prepare user data**\r\n\r\n   Required format (JSON):\r\n   ```json\r\n   [\r\n     {\r\n       \"user_id\": \"user_1\",\r\n       \"age\": 32,\r\n       \"usage_frequency\": \"daily\",\r\n       \"features_used\": [\"dashboard\", \"reports\", \"export\"],\r\n       \"primary_device\": \"desktop\",\r\n       \"usage_context\": \"work\",\r\n       \"tech_proficiency\": 7,\r\n       \"pain_points\": [\"slow loading\", \"confusing UI\"]\r\n     }\r\n   ]\r\n   ```\r\n\r\n2. **Run persona generator**\r\n   ```bash\r\n   # Human-readable output\r\n   python scripts/persona_generator.py\r\n\r\n   # JSON output for integration\r\n   python scripts/persona_generator.py json\r\n   ```\r\n\r\n3. **Review generated components**\r\n\r\n   | Component | What to Check |\r\n   |-----------|---------------|\r\n   | Archetype | Does it match the data patterns? |\r\n   | Demographics | Are they derived from actual data? |\r\n   | Goals | Are they specific and actionable? |\r\n   | Frustrations | Do they include frequency counts? |\r\n   | Design implications | Can designers act on these? |\r\n\r\n4. **Validate persona**\r\n\r\n   - Show to 3-5 real users: \"Does this sound like you?\"\r\n   - Cross-check with support tickets\r\n   - Verify against analytics data\r\n\r\n5. **Reference:** See `references/persona-methodology.md` for validity criteria\r\n\r\n---\r\n\r\n### Workflow 2: Create Journey Map\r\n\r\n**Situation:** You need to visualize the end-to-end user experience for a specific goal.\r\n\r\n**Steps:**\r\n\r\n1. **Define scope**\r\n\r\n   | Element | Description |\r\n   |---------|-------------|\r\n   | Persona | Which user type |\r\n   | Goal | What they're trying to achieve |\r\n   | Start | Trigger that begins journey |\r\n   | End | Success criteria |\r\n   | Timeframe | Hours/days/weeks |\r\n\r\n2. **Gather journey data**\r\n\r\n   Sources:\r\n   - User interviews (ask \"walk me through...\")\r\n   - Session recordings\r\n   - Analytics (funnel, drop-offs)\r\n   - Support tickets\r\n\r\n3. **Map the stages**\r\n\r\n   Typical B2B SaaS stages:\r\n   ```\r\n   Awareness → Evaluation → Onboarding → Adoption → Advocacy\r\n   ```\r\n\r\n4. **Fill in layers for each stage**\r\n\r\n   ```\r\n   Stage: [Name]\r\n   ├── Actions: What does user do?\r\n   ├── Touchpoints: Where do they interact?\r\n   ├── Emotions: How do they feel? (1-5)\r\n   ├── Pain Points: What frustrates them?\r\n   └── Opportunities: Where can we improve?\r\n   ```\r\n\r\n5. **Identify opportunities**\r\n\r\n   Priority Score = Frequency × Severity × Solvability\r\n\r\n6. **Reference:** See `references/journey-mapping-guide.md` for templates\r\n\r\n---\r\n\r\n### Workflow 3: Plan Usability Test\r\n\r\n**Situation:** You need to validate a design with real users.\r\n\r\n**Steps:**\r\n\r\n1. **Define research questions**\r\n\r\n   Transform vague goals into testable questions:\r\n\r\n   | Vague | Testable |\r\n   |-------|----------|\r\n   | \"Is it easy to use?\" | \"Can users complete checkout in <3 min?\" |\r\n   | \"Do users like it?\" | \"Will users choose Design A or B?\" |\r\n   | \"Does it make sense?\" | \"Can users find settings without hints?\" |\r\n\r\n2. **Select method**\r\n\r\n   | Method | Participants | Duration | Best For |\r\n   |--------|--------------|----------|----------|\r\n   | Moderated remote | 5-8 | 45-60 min | Deep insights |\r\n   | Unmoderated remote | 10-20 | 15-20 min | Quick validation |\r\n   | Guerrilla | 3-5 | 5-10 min | Rapid feedback |\r\n\r\n3. **Design tasks**\r\n\r\n   Good task format:\r\n   ```\r\n   SCENARIO: \"Imagine you're planning a trip to Paris...\"\r\n   GOAL: \"Book a hotel for 3 nights in your budget.\"\r\n   SUCCESS: \"You see the confirmation page.\"\r\n   ```\r\n\r\n   Task progression: Warm-up → Core → Secondary → Edge case → Free exploration\r\n\r\n4. **Define success metrics**\r\n\r\n   | Metric | Target |\r\n   |--------|--------|\r\n   | Completion rate | >80% |\r\n   | Time on task | <2× expected |\r\n   | Error rate | <15% |\r\n   | Satisfaction | >4/5 |\r\n\r\n5. **Prepare moderator guide**\r\n\r\n   - Think-aloud instructions\r\n   - Non-leading prompts\r\n   - Post-task questions\r\n\r\n6. **Reference:** See `references/usability-testing-frameworks.md` for full guide\r\n\r\n---\r\n\r\n### Workflow 4: Synthesize Research\r\n\r\n**Situation:** You have raw research data (interviews, surveys, observations) and need actionable insights.\r\n\r\n**Steps:**\r\n\r\n1. **Code the data**\r\n\r\n   Tag each data point:\r\n   - `[GOAL]` - What they want to achieve\r\n   - `[PAIN]` - What frustrates them\r\n   - `[BEHAVIOR]` - What they actually do\r\n   - `[CONTEXT]` - When/where they use product\r\n   - `[QUOTE]` - Direct user words\r\n\r\n2. **Cluster similar patterns**\r\n\r\n   ```\r\n   User A: Uses daily, advanced features, shortcuts\r\n   User B: Uses daily, complex workflows, automation\r\n   User C: Uses weekly, basic needs, occasional\r\n\r\n   Cluster 1: A, B (Power Users)\r\n   Cluster 2: C (Casual User)\r\n   ```\r\n\r\n3. **Calculate segment sizes**\r\n\r\n   | Cluster | Users | % | Viability |\r\n   |---------|-------|---|-----------|\r\n   | Power Users | 18 | 36% | Primary persona |\r\n   | Business Users | 15 | 30% | Primary persona |\r\n   | Casual Users | 12 | 24% | Secondary persona |\r\n\r\n4. **Extract key findings**\r\n\r\n   For each theme:\r\n   - Finding statement\r\n   - Supporting evidence (quotes, data)\r\n   - Frequency (X/Y participants)\r\n   - Business impact\r\n   - Recommendation\r\n\r\n5. **Prioritize opportunities**\r\n\r\n   | Factor | Score 1-5 |\r\n   |--------|-----------|\r\n   | Frequency | How often does this occur? |\r\n   | Severity | How much does it hurt? |\r\n   | Breadth | How many users affected? |\r\n   | Solvability | Can we fix this? |\r\n\r\n6. **Reference:** See `references/persona-methodology.md` for analysis framework\r\n\r\n---\r\n\r\n## Tool Reference\r\n\r\n### persona_generator.py\r\n\r\nGenerates data-driven personas from user research data.\r\n\r\n| Argument | Values | Default | Description |\r\n|----------|--------|---------|-------------|\r\n| format | (none), json | (none) | Output format |\r\n\r\n**Sample Output:**\r\n\r\n```\r\n============================================================\r\nPERSONA: Alex the Power User\r\n============================================================\r\n\r\n📝 A daily user who primarily uses the product for work purposes\r\n\r\nArchetype: Power User\r\nQuote: \"I need tools that can keep up with my workflow\"\r\n\r\n👤 Demographics:\r\n  • Age Range: 25-34\r\n  • Location Type: Urban\r\n  • Tech Proficiency: Advanced\r\n\r\n🎯 Goals & Needs:\r\n  • Complete tasks efficiently\r\n  • Automate workflows\r\n  • Access advanced features\r\n\r\n😤 Frustrations:\r\n  • Slow loading times (14/20 users)\r\n  • No keyboard shortcuts\r\n  • Limited API access\r\n\r\n💡 Design Implications:\r\n  → Optimize for speed and efficiency\r\n  → Provide keyboard shortcuts and power features\r\n  → Expose API and automation capabilities\r\n\r\n📈 Data: Based on 45 users\r\n    Confidence: High\r\n```\r\n\r\n**Archetypes Generated:**\r\n\r\n| Archetype | Signals | Design Focus |\r\n|-----------|---------|--------------|\r\n| power_user | Daily use, 10+ features | Efficiency, customization |\r\n| casual_user | Weekly use, 3-5 features | Simplicity, guidance |\r\n| business_user | Work context, team use | Collaboration, reporting |\r\n| mobile_first | Mobile primary | Touch, offline, speed |\r\n\r\n**Output Components:**\r\n\r\n| Component | Description |\r\n|-----------|-------------|\r\n| demographics | Age range, location, occupation, tech level |\r\n| psychographics | Motivations, values, attitudes, lifestyle |\r\n| behaviors | Usage patterns, feature preferences |\r\n| needs_and_goals | Primary, secondary, functional, emotional |\r\n| frustrations | Pain points with evidence |\r\n| scenarios | Contextual usage stories |\r\n| design_implications | Actionable recommendations |\r\n| data_points | Sample size, confidence level |\r\n\r\n---\r\n\r\n## Quick Reference Tables\r\n\r\n### Research Method Selection\r\n\r\n| Question Type | Best Method | Sample Size |\r\n|---------------|-------------|-------------|\r\n| \"What do users do?\" | Analytics, observation | 100+ events |\r\n| \"Why do they do it?\" | Interviews | 8-15 users |\r\n| \"How well can they do it?\" | Usability test | 5-8 users |\r\n| \"What do they prefer?\" | Survey, A/B test | 50+ users |\r\n| \"What do they feel?\" | Diary study, interviews | 10-15 users |\r\n\r\n### Persona Confidence Levels\r\n\r\n| Sample Size | Confidence | Use Case |\r\n|-------------|------------|----------|\r\n| 5-10 users | Low | Exploratory |\r\n| 11-30 users | Medium | Directional |\r\n| 31+ users | High | Production |\r\n\r\n### Usability Issue Severity\r\n\r\n| Severity | Definition | Action |\r\n|----------|------------|--------|\r\n| 4 - Critical | Prevents task completion | Fix immediately |\r\n| 3 - Major | Significant difficulty | Fix before release |\r\n| 2 - Minor | Causes hesitation | Fix when possible |\r\n| 1 - Cosmetic | Noticed but not problematic | Low priority |\r\n\r\n### Interview Question Types\r\n\r\n| Type | Example | Use For |\r\n|------|---------|---------|\r\n| Context | \"Walk me through your typical day\" | Understanding environment |\r\n| Behavior | \"Show me how you do X\" | Observing actual actions |\r\n| Goals | \"What are you trying to achieve?\" | Uncovering motivations |\r\n| Pain | \"What's the hardest part?\" | Identifying frustrations |\r\n| Reflection | \"What would you change?\" | Generating ideas |\r\n\r\n---\r\n\r\n## Knowledge Base\r\n\r\nDetailed reference guides in `references/`:\r\n\r\n| File | Content |\r\n|------|---------|\r\n| `persona-methodology.md` | Validity criteria, data collection, analysis framework |\r\n| `journey-mapping-guide.md` | Mapping process, templates, opportunity identification |\r\n| `example-personas.md` | 3 complete persona examples with data |\r\n| `usability-testing-frameworks.md` | Test planning, task design, analysis |\r\n\r\n---\r\n\r\n## Validation Checklist\r\n\r\n### Persona Quality\r\n- [ ] Based on 20+ users (minimum)\r\n- [ ] At least 2 data sources (quant + qual)\r\n- [ ] Specific, actionable goals\r\n- [ ] Frustrations include frequency counts\r\n- [ ] Design implications are specific\r\n- [ ] Confidence level stated\r\n\r\n### Journey Map Quality\r\n- [ ] Scope clearly defined (persona, goal, timeframe)\r\n- [ ] Based on real user data, not assumptions\r\n- [ ] All layers filled (actions, touchpoints, emotions)\r\n- [ ] Pain points identified per stage\r\n- [ ] Opportunities prioritized\r\n\r\n### Usability Test Quality\r\n- [ ] Research questions are testable\r\n- [ ] Tasks are realistic scenarios, not instructions\r\n- [ ] 5+ participants per design\r\n- [ ] Success metrics defined\r\n- [ ] Findings include severity ratings\r\n\r\n### Research Synthesis Quality\r\n- [ ] Data coded consistently\r\n- [ ] Patterns based on 3+ data points\r\n- [ ] Findings include evidence\r\n- [ ] Recommendations are actionable\r\n- [ ] Priorities justified\r\n\r\n## Related Skills\r\n\r\n- **UI Design System** (`product-team/ui-design-system/`) — Research findings inform design system decisions\r\n- **Product Manager Toolkit** (`product-team/product-manager-toolkit/`) — Customer interview analysis complements persona research",
    "user_template": ""
  },
  "variables": [],
  "install": {
    "steps": [
      {
        "title": "Download & unzip",
        "detail": "Download the .zip package from SkillVault and unzip it. The ux-researcher-designer/ folder contains SKILL.md plus any companion scripts, references and assets."
      },
      {
        "title": "Copy into your agent skills directory",
        "detail": "Move the folder into your agent's skills directory — e.g. ~/.claude/skills/ (Claude Code), .codex/skills/, .cursor/skills/ or your project's .claude/skills/ folder — then restart or reload the session."
      },
      {
        "title": "Use it",
        "detail": "Describe the task in natural language; the agent loads the skill automatically when the request matches the skill description."
      }
    ]
  },
  "usage": {
    "steps": []
  },
  "metadata": {
    "author": "SkillVault",
    "source": "https://skillvault.top/skills/ux-researcher-designer",
    "exported_at": "2026-11-03T07:45:20.407Z"
  }
}

format: aiskill/v1
skill:
  name: ux-researcher-designer
  slug: ux-researcher-designer
  version: 1.0.0
  description: >-
    UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona
    generation, journey mapping, usability testing frameworks, and research synthesis. Use when
    conducting user research, creating personas, mapping user journeys, planning usability tests, or
    validating designs.
  category: Business
  tags:
    - product-business
    - testing
    - research
    - design
  platforms:
    - chatgpt
    - claude-code
    - cursor
  tested_environment: >-
    Agent Skills convention (SKILL.md) — works with Claude Code, Cursor, ChatGPT/Codex and
    compatible agents
  license: MIT
prompts:
  system: "# UX Researcher & Designer\r\n\r\nGenerate user personas from research data, create journey maps, plan usability tests, and synthesize research findings into actionable design recommendations.\r\n\r\n---\r\n\r\n## Table of Contents\r\n\r\n- [Trigger Terms](#trigger-terms)\r\n- [Workflows](#workflows)\r\n  - [Workflow 1: Generate User Persona](#workflow-1-generate-user-persona)\r\n  - [Workflow 2: Create Journey Map](#workflow-2-create-journey-map)\r\n  - [Workflow 3: Plan Usability Test](#workflow-3-plan-usability-test)\r\n  - [Workflow 4: Synthesize Research](#workflow-4-synthesize-research)\r\n- [Tool Reference](#tool-reference)\r\n- [Quick Reference Tables](#quick-reference-tables)\r\n- [Knowledge Base](#knowledge-base)\r\n\r\n---\r\n\r\n## Trigger Terms\r\n\r\nUse this skill when you need to:\r\n\r\n- \"create user persona\"\r\n- \"generate persona from data\"\r\n- \"build customer journey map\"\r\n- \"map user journey\"\r\n- \"plan usability test\"\r\n- \"design usability study\"\r\n- \"analyze user research\"\r\n- \"synthesize interview findings\"\r\n- \"identify user pain points\"\r\n- \"define user archetypes\"\r\n- \"calculate research sample size\"\r\n- \"create empathy map\"\r\n- \"identify user needs\"\r\n\r\n---\r\n\r\n## Workflows\r\n\r\n### Workflow 1: Generate User Persona\r\n\r\n**Situation:** You have user data (analytics, surveys, interviews) and need to create a research-backed persona.\r\n\r\n**Steps:**\r\n\r\n1. **Prepare user data**\r\n\r\n   Required format (JSON):\r\n   ```json\r\n   [\r\n     {\r\n       \"user_id\": \"user_1\",\r\n       \"age\": 32,\r\n       \"usage_frequency\": \"daily\",\r\n       \"features_used\": [\"dashboard\", \"reports\", \"export\"],\r\n       \"primary_device\": \"desktop\",\r\n       \"usage_context\": \"work\",\r\n       \"tech_proficiency\": 7,\r\n       \"pain_points\": [\"slow loading\", \"confusing UI\"]\r\n     }\r\n   ]\r\n   ```\r\n\r\n2. **Run persona generator**\r\n   ```bash\r\n   # Human-readable output\r\n   python scripts/persona_generator.py\r\n\r\n   # JSON output for integration\r\n   python scripts/persona_generator.py json\r\n   ```\r\n\r\n3. **Review generated components**\r\n\r\n   | Component | What to Check |\r\n   |-----------|---------------|\r\n   | Archetype | Does it match the data patterns? |\r\n   | Demographics | Are they derived from actual data? |\r\n   | Goals | Are they specific and actionable? |\r\n   | Frustrations | Do they include frequency counts? |\r\n   | Design implications | Can designers act on these? |\r\n\r\n4. **Validate persona**\r\n\r\n   - Show to 3-5 real users: \"Does this sound like you?\"\r\n   - Cross-check with support tickets\r\n   - Verify against analytics data\r\n\r\n5. **Reference:** See `references/persona-methodology.md` for validity criteria\r\n\r\n---\r\n\r\n### Workflow 2: Create Journey Map\r\n\r\n**Situation:** You need to visualize the end-to-end user experience for a specific goal.\r\n\r\n**Steps:**\r\n\r\n1. **Define scope**\r\n\r\n   | Element | Description |\r\n   |---------|-------------|\r\n   | Persona | Which user type |\r\n   | Goal | What they're trying to achieve |\r\n   | Start | Trigger that begins journey |\r\n   | End | Success criteria |\r\n   | Timeframe | Hours/days/weeks |\r\n\r\n2. **Gather journey data**\r\n\r\n   Sources:\r\n   - User interviews (ask \"walk me through...\")\r\n   - Session recordings\r\n   - Analytics (funnel, drop-offs)\r\n   - Support tickets\r\n\r\n3. **Map the stages**\r\n\r\n   Typical B2B SaaS stages:\r\n   ```\r\n   Awareness → Evaluation → Onboarding → Adoption → Advocacy\r\n   ```\r\n\r\n4. **Fill in layers for each stage**\r\n\r\n   ```\r\n   Stage: [Name]\r\n   ├── Actions: What does user do?\r\n   ├── Touchpoints: Where do they interact?\r\n   ├── Emotions: How do they feel? (1-5)\r\n   ├── Pain Points: What frustrates them?\r\n   └── Opportunities: Where can we improve?\r\n   ```\r\n\r\n5. **Identify opportunities**\r\n\r\n   Priority Score = Frequency × Severity × Solvability\r\n\r\n6. **Reference:** See `references/journey-mapping-guide.md` for templates\r\n\r\n---\r\n\r\n### Workflow 3: Plan Usability Test\r\n\r\n**Situation:** You need to validate a design with real users.\r\n\r\n**Steps:**\r\n\r\n1. **Define research questions**\r\n\r\n   Transform vague goals into testable questions:\r\n\r\n   | Vague | Testable |\r\n   |-------|----------|\r\n   | \"Is it easy to use?\" | \"Can users complete checkout in <3 min?\" |\r\n   | \"Do users like it?\" | \"Will users choose Design A or B?\" |\r\n   | \"Does it make sense?\" | \"Can users find settings without hints?\" |\r\n\r\n2. **Select method**\r\n\r\n   | Method | Participants | Duration | Best For |\r\n   |--------|--------------|----------|----------|\r\n   | Moderated remote | 5-8 | 45-60 min | Deep insights |\r\n   | Unmoderated remote | 10-20 | 15-20 min | Quick validation |\r\n   | Guerrilla | 3-5 | 5-10 min | Rapid feedback |\r\n\r\n3. **Design tasks**\r\n\r\n   Good task format:\r\n   ```\r\n   SCENARIO: \"Imagine you're planning a trip to Paris...\"\r\n   GOAL: \"Book a hotel for 3 nights in your budget.\"\r\n   SUCCESS: \"You see the confirmation page.\"\r\n   ```\r\n\r\n   Task progression: Warm-up → Core → Secondary → Edge case → Free exploration\r\n\r\n4. **Define success metrics**\r\n\r\n   | Metric | Target |\r\n   |--------|--------|\r\n   | Completion rate | >80% |\r\n   | Time on task | <2× expected |\r\n   | Error rate | <15% |\r\n   | Satisfaction | >4/5 |\r\n\r\n5. **Prepare moderator guide**\r\n\r\n   - Think-aloud instructions\r\n   - Non-leading prompts\r\n   - Post-task questions\r\n\r\n6. **Reference:** See `references/usability-testing-frameworks.md` for full guide\r\n\r\n---\r\n\r\n### Workflow 4: Synthesize Research\r\n\r\n**Situation:** You have raw research data (interviews, surveys, observations) and need actionable insights.\r\n\r\n**Steps:**\r\n\r\n1. **Code the data**\r\n\r\n   Tag each data point:\r\n   - `[GOAL]` - What they want to achieve\r\n   - `[PAIN]` - What frustrates them\r\n   - `[BEHAVIOR]` - What they actually do\r\n   - `[CONTEXT]` - When/where they use product\r\n   - `[QUOTE]` - Direct user words\r\n\r\n2. **Cluster similar patterns**\r\n\r\n   ```\r\n   User A: Uses daily, advanced features, shortcuts\r\n   User B: Uses daily, complex workflows, automation\r\n   User C: Uses weekly, basic needs, occasional\r\n\r\n   Cluster 1: A, B (Power Users)\r\n   Cluster 2: C (Casual User)\r\n   ```\r\n\r\n3. **Calculate segment sizes**\r\n\r\n   | Cluster | Users | % | Viability |\r\n   |---------|-------|---|-----------|\r\n   | Power Users | 18 | 36% | Primary persona |\r\n   | Business Users | 15 | 30% | Primary persona |\r\n   | Casual Users | 12 | 24% | Secondary persona |\r\n\r\n4. **Extract key findings**\r\n\r\n   For each theme:\r\n   - Finding statement\r\n   - Supporting evidence (quotes, data)\r\n   - Frequency (X/Y participants)\r\n   - Business impact\r\n   - Recommendation\r\n\r\n5. **Prioritize opportunities**\r\n\r\n   | Factor | Score 1-5 |\r\n   |--------|-----------|\r\n   | Frequency | How often does this occur? |\r\n   | Severity | How much does it hurt? |\r\n   | Breadth | How many users affected? |\r\n   | Solvability | Can we fix this? |\r\n\r\n6. **Reference:** See `references/persona-methodology.md` for analysis framework\r\n\r\n---\r\n\r\n## Tool Reference\r\n\r\n### persona_generator.py\r\n\r\nGenerates data-driven personas from user research data.\r\n\r\n| Argument | Values | Default | Description |\r\n|----------|--------|---------|-------------|\r\n| format | (none), json | (none) | Output format |\r\n\r\n**Sample Output:**\r\n\r\n```\r\n============================================================\r\nPERSONA: Alex the Power User\r\n============================================================\r\n\r\n📝 A daily user who primarily uses the product for work purposes\r\n\r\nArchetype: Power User\r\nQuote: \"I need tools that can keep up with my workflow\"\r\n\r\n👤 Demographics:\r\n  • Age Range: 25-34\r\n  • Location Type: Urban\r\n  • Tech Proficiency: Advanced\r\n\r\n🎯 Goals & Needs:\r\n  • Complete tasks efficiently\r\n  • Automate workflows\r\n  • Access advanced features\r\n\r\n😤 Frustrations:\r\n  • Slow loading times (14/20 users)\r\n  • No keyboard shortcuts\r\n  • Limited API access\r\n\r\n💡 Design Implications:\r\n  → Optimize for speed and efficiency\r\n  → Provide keyboard shortcuts and power features\r\n  → Expose API and automation capabilities\r\n\r\n📈 Data: Based on 45 users\r\n    Confidence: High\r\n```\r\n\r\n**Archetypes Generated:**\r\n\r\n| Archetype | Signals | Design Focus |\r\n|-----------|---------|--------------|\r\n| power_user | Daily use, 10+ features | Efficiency, customization |\r\n| casual_user | Weekly use, 3-5 features | Simplicity, guidance |\r\n| business_user | Work context, team use | Collaboration, reporting |\r\n| mobile_first | Mobile primary | Touch, offline, speed |\r\n\r\n**Output Components:**\r\n\r\n| Component | Description |\r\n|-----------|-------------|\r\n| demographics | Age range, location, occupation, tech level |\r\n| psychographics | Motivations, values, attitudes, lifestyle |\r\n| behaviors | Usage patterns, feature preferences |\r\n| needs_and_goals | Primary, secondary, functional, emotional |\r\n| frustrations | Pain points with evidence |\r\n| scenarios | Contextual usage stories |\r\n| design_implications | Actionable recommendations |\r\n| data_points | Sample size, confidence level |\r\n\r\n---\r\n\r\n## Quick Reference Tables\r\n\r\n### Research Method Selection\r\n\r\n| Question Type | Best Method | Sample Size |\r\n|---------------|-------------|-------------|\r\n| \"What do users do?\" | Analytics, observation | 100+ events |\r\n| \"Why do they do it?\" | Interviews | 8-15 users |\r\n| \"How well can they do it?\" | Usability test | 5-8 users |\r\n| \"What do they prefer?\" | Survey, A/B test | 50+ users |\r\n| \"What do they feel?\" | Diary study, interviews | 10-15 users |\r\n\r\n### Persona Confidence Levels\r\n\r\n| Sample Size | Confidence | Use Case |\r\n|-------------|------------|----------|\r\n| 5-10 users | Low | Exploratory |\r\n| 11-30 users | Medium | Directional |\r\n| 31+ users | High | Production |\r\n\r\n### Usability Issue Severity\r\n\r\n| Severity | Definition | Action |\r\n|----------|------------|--------|\r\n| 4 - Critical | Prevents task completion | Fix immediately |\r\n| 3 - Major | Significant difficulty | Fix before release |\r\n| 2 - Minor | Causes hesitation | Fix when possible |\r\n| 1 - Cosmetic | Noticed but not problematic | Low priority |\r\n\r\n### Interview Question Types\r\n\r\n| Type | Example | Use For |\r\n|------|---------|---------|\r\n| Context | \"Walk me through your typical day\" | Understanding environment |\r\n| Behavior | \"Show me how you do X\" | Observing actual actions |\r\n| Goals | \"What are you trying to achieve?\" | Uncovering motivations |\r\n| Pain | \"What's the hardest part?\" | Identifying frustrations |\r\n| Reflection | \"What would you change?\" | Generating ideas |\r\n\r\n---\r\n\r\n## Knowledge Base\r\n\r\nDetailed reference guides in `references/`:\r\n\r\n| File | Content |\r\n|------|---------|\r\n| `persona-methodology.md` | Validity criteria, data collection, analysis framework |\r\n| `journey-mapping-guide.md` | Mapping process, templates, opportunity identification |\r\n| `example-personas.md` | 3 complete persona examples with data |\r\n| `usability-testing-frameworks.md` | Test planning, task design, analysis |\r\n\r\n---\r\n\r\n## Validation Checklist\r\n\r\n### Persona Quality\r\n- [ ] Based on 20+ users (minimum)\r\n- [ ] At least 2 data sources (quant + qual)\r\n- [ ] Specific, actionable goals\r\n- [ ] Frustrations include frequency counts\r\n- [ ] Design implications are specific\r\n- [ ] Confidence level stated\r\n\r\n### Journey Map Quality\r\n- [ ] Scope clearly defined (persona, goal, timeframe)\r\n- [ ] Based on real user data, not assumptions\r\n- [ ] All layers filled (actions, touchpoints, emotions)\r\n- [ ] Pain points identified per stage\r\n- [ ] Opportunities prioritized\r\n\r\n### Usability Test Quality\r\n- [ ] Research questions are testable\r\n- [ ] Tasks are realistic scenarios, not instructions\r\n- [ ] 5+ participants per design\r\n- [ ] Success metrics defined\r\n- [ ] Findings include severity ratings\r\n\r\n### Research Synthesis Quality\r\n- [ ] Data coded consistently\r\n- [ ] Patterns based on 3+ data points\r\n- [ ] Findings include evidence\r\n- [ ] Recommendations are actionable\r\n- [ ] Priorities justified\r\n\r\n## Related Skills\r\n\r\n- **UI Design System** (`product-team/ui-design-system/`) — Research findings inform design system decisions\r\n- **Product Manager Toolkit** (`product-team/product-manager-toolkit/`) — Customer interview analysis complements persona research"
  user_template: ""
variables: []
install:
  steps:
    - title: Download & unzip
      detail: >-
        Download the .zip package from SkillVault and unzip it. The ux-researcher-designer/ folder
        contains SKILL.md plus any companion scripts, references and assets.
    - title: Copy into your agent skills directory
      detail: >-
        Move the folder into your agent's skills directory — e.g. ~/.claude/skills/ (Claude Code),
        .codex/skills/, .cursor/skills/ or your project's .claude/skills/ folder — then restart or
        reload the session.
    - title: Use it
      detail: >-
        Describe the task in natural language; the agent loads the skill automatically when the
        request matches the skill description.
usage:
  steps: []
metadata:
  author: SkillVault
  source: https://skillvault.top/skills/ux-researcher-designer
  exported_at: "2026-11-03T07:45:20.407Z"